DCNSA Level III
Network Set-up cheat sheet
Every chapter's key points, formulas and definitions on one page, for the last week before the exam. Each heading links to the chapter that explains it.
Network server concepts
- Windows Server suits organisations already standardised on Microsoft technology, Unix is known for stability in demanding, high-uptime environments, and Linux is open source with no per-server licensing cost.
- Servers are compared on features (what is built in), functionality (how well the platform performs the roles actually needed) and suitability (how well it fits existing skills, infrastructure and budget).
- The best platform on paper is the wrong choice if nobody on staff can administer it, so suitability usually decides the platform.
- The core server roles are Active Directory, proxy server, web server, file server, DHCP and DNS; Active Directory is the role most other roles and the whole domain structure depend on.
- Hardware is sized to each role: a file server needs generous, reliable storage, DNS and DHCP need very little storage but very high availability, and a web server scales with expected traffic.
Key terms
- Microsoft Windows Server
- The dominant choice in organisations already standardised on Microsoft technology, with tight integration with Active Directory and Windows clients (Network Operating Systems, Windows Server Roles and Features), a graphical management interface, and a large pool of administrators already familiar with it.
- Unix server
- A long-established family of server operating systems, known for stability and a strong track record in demanding, high-uptime environments, prevalent in enterprise and legacy environments where systems have run continuously for years.
- Linux server
- An open-source, highly configurable option, dominant for web servers and cloud infrastructure, with no per-server licensing cost, though it demands more command-line comfort from its administrators than Windows Server typically does.
- Features
- The built-in capabilities each platform offers out of the box, which roles are available and how mature their implementation is.
- Functionality
- How well a platform performs the specific roles the organisation actually needs, not simply how many features it lists on paper.
- Suitability
- How well a platform fits the organisation's existing skills, infrastructure and budget, not just its technical capability in isolation, since the best platform on paper is the wrong choice if nobody on staff can administer it.
- Active Directory
- Centralised directory service for users, computers and policy (Network Operating Systems, under configuring the operating system), the role most other roles and the whole domain structure depend on.
- Proxy server
- Sits between clients and the wider internet, forwarding requests, and often filtering or caching them, both improving performance (cached content served locally) and enforcing policy (blocking disallowed sites).
- Web server
- Hosts websites and web applications, serving content to client browsers, an intranet portal or a customer-facing site.
- File server
- Provides centralised, shared file storage with access control, the role most directly delivering everyday resource sharing.
- DHCP
- Automatically assigns IP addresses and network configuration to devices, developed in full computational depth in the chapter on configuring server roles.
- DNS
- Translates human-readable names into IP addresses, without which every other service would need to be reached by a memorised address.
The rest of the sheet covers
- Configuring server roles and features
- Administering server roles and features
- Exam technique and revision
- Glossary