1.2.2. Documentation as a First-Class Deliverable
💡 First Principle: Documentation isn't bureaucratic overhead—it's operational infrastructure. Undocumented systems are liabilities because the knowledge of how they work exists only in someone's head, and people leave, forget, and make mistakes.
Documentation failures cause real problems: the admin who configured a server five years ago has left, the configuration was never documented, and now nobody knows why a critical firewall rule exists or whether it's safe to remove. This is called undocumented technical debt, and it's extremely common.
Server+ tests documentation across multiple domains. The key document types:
| Document Type | Purpose | Example Content |
|---|---|---|
| Architecture diagrams | Show logical relationships between systems | Network topology, service dependencies |
| Infrastructure diagrams | Show physical layout | Rack diagrams, cable maps, floor plans |
| Workflow diagrams | Show processes | Backup procedures, escalation paths |
| Recovery processes | Specific DR/restore steps | Step-by-step restore instructions |
| Baselines | Normal performance snapshots | CPU/memory/disk/network metrics at known-good state |
| Change management records | Log of all changes | What changed, when, who approved, how to roll back |
| Server configurations | Current state of server settings | OS version, installed roles, IP config |
| Company policies and procedures | Governance | BIA, SLA commitments, acceptable use |
Change management deserves special attention. Every change to a production system should be documented before it's made—what's changing, why, who approved it, and how to roll back if it fails. Systems without change management suffer from configuration drift: the actual state of the system diverges from what anyone believes it to be, and troubleshooting becomes archaeology.
⚠️ Exam Trap: Documentation must be stored securely—especially documentation that contains IP addresses, credentials, network diagrams, or system configurations. A network diagram in the wrong hands is a roadmap for attackers.
Reflection Question: What is the risk of storing sensitive server documentation (IP assignments, network diagrams) in an unsecured shared folder?
