Physical, Logical, Rack, Cable, Wireless Diagrams, and IPAM
Key Takeaways
- Domain 3 (Network Operations) is roughly 19% of the N10-009 exam, and objective 3.1 explicitly lists physical, logical, rack, and wiring diagrams plus IPAM as documentation Network+ candidates must distinguish.
- Physical diagrams answer 'where is it and what connects to what'; logical diagrams answer 'how does traffic, VLANs, subnets, routing, and security zones relate' — the exam tests which one solves a given task.
- Rack (elevation) and cable/wiring documentation cut Mean Time To Repair by mapping rack unit position, patch panel ports, switchports, media type, and labels so technicians never guess.
- Wireless diagrams (heat maps) tie Access Point placement, channel plan, transmit power, SSIDs, and coverage cells to a floor plan to manage roaming, capacity, and interference.
- IP Address Management (IPAM) tracks subnets, DHCP scopes, exclusions, reservations, static assignments, DNS relationships, ownership, and utilization to prevent address conflicts and stale records.
Documentation in N10-009 Domain 3
Network operations (Domain 3) accounts for roughly 19% of the CompTIA Network+ N10-009 exam, and objective 3.1 lists the documentation types you must tell apart. On the exam you will not draw a diagram; you will be handed a scenario and asked which artifact answers the question fastest. The exam is a maximum of 90 questions in 90 minutes with a passing score of 720 on a 100-900 scale, so you cannot afford to waste time guessing which document to open. Accurate documentation is a shared source of truth that lets teams troubleshoot, plan safe changes, onboard staff, and prove how the environment should behave.
Diagram Types and Their Jobs
| Documentation | What it shows | When the exam wants it |
|---|---|---|
| Physical diagram | Buildings, IDFs/MDFs, racks, devices, cabling runs, circuits, media paths | Locate equipment and physical failure domains |
| Logical diagram | Subnets, VLANs, routing, firewalls, WAN edges, cloud links, dependencies | Explain traffic flow and segmentation |
| Rack diagram (elevation) | RU position, device name, power feeds, patch panels, environmental notes | Install, replace, or audit a specific device |
| Wiring/cable diagram | Patch panel ports, switchports, fiber pairs, copper drops, labels, media | Avoid mistakes during moves, adds, changes |
| Wireless diagram (heat map) | AP placement, coverage cells, SSIDs, channels, power, controller links | Tune coverage, capacity, roaming, interference |
| IPAM records | Networks, assignments, DHCP scopes, reservations, DNS names, owners | Prevent conflicts and plan capacity |
Physical and logical diagrams are complementary. A physical diagram shows that a branch switch connects to a carrier handoff in a telecom room. The logical diagram shows the same switch carrying a user VLAN, a voice VLAN, a management VLAN, and a routed WAN link to the data center. Network+ frequently contrasts these two: if the question mentions racks, rooms, ports, or cable runs, choose physical; if it mentions VLANs, subnets, routing, or zones, choose logical.
Physical and Rack Detail
Useful physical records include make/model, serial number, asset tag, rack unit location, power supply connection, UPS or PDU mapping, circuit IDs, media type, transceiver type, and provider escalation contact. A rack elevation should be specific enough that a remote hands-on technician identifies the correct device without counting from the top. If a switch has dual power supplies, the record should name separate power feeds; if a firewall depends on a specific ISP handoff, the circuit ID and provider escalation number belong in the record before any outage.
Cable and Wiring Records
| Cable field | Example |
|---|---|
| Label | IDF2-PP03-24 to SW2-Gi1/0/24 |
| Media | Cat 6A copper |
| Endpoint | Office 2B-117 wall jack B |
| Service | User access VLAN 20 |
| Status | Active |
Fiber documentation should distinguish strand, connector type, polarity, and transceiver. Copper records should include the category rating (for example Cat 6A) and whether the run supports the expected speed and Power over Ethernet load. A standardized label scheme (location-panel-port to device-port) is what lets a wiring diagram be trusted during a midnight move.
Wireless Heat Maps
Wireless diagrams are tied to a floor plan and include AP location, mounting height, antenna type, SSID mapping, channel, transmit power, expected coverage, survey results, and known interference sources (microwaves, Bluetooth, neighboring networks). A good record also names controller or cloud-management ownership and whether each AP serves users, guests, scanners, or outdoor coverage. This is what you consult when a conference room sees channel overlap or sticky-client roaming.
IPAM and Naming
IP Address Management is far more than a spreadsheet of used addresses. It should track subnet purpose, VLAN ID, location, DHCP scope, excluded ranges, reservations, default gateway, DNS zones, device owner, and last-verified date.
| IPAM item | Why it matters |
|---|---|
| Subnet ownership | Identifies who approves new assignments |
| DHCP scope | Shows dynamic ranges, leases, options, exclusions |
| Static assignment | Prevents reuse of infrastructure addresses |
| DNS relationship | Connects names to addresses during triage |
| Utilization | Flags when a /24 needs redesign or expansion |
Practical Scenario
A technician replaces a switch in an IDF and several phones fail to register. Good documentation lets the technician verify the voice VLAN, the uplink trunk, the patch panel mapping, the PoE budget, and the switchport template. Without it, the technician guesses at VLANs or moves cables until something works, creating new faults.
Common Exam Traps
| Trap | Better exam reasoning |
|---|---|
| "A logical diagram is enough for hands-on work." | Physical, rack, and cable records locate and change hardware safely. |
| "IPAM only tracks static addresses." | IPAM tracks DHCP scopes, reservations, subnets, DNS, and ownership. |
| "A heat map is just an AP inventory." | It also captures coverage, channels, power, SSIDs, and interference. |
| "Documentation is finished after install." | It must be updated after every change and validated periodically. |
Quick Drill
- Find the switchport behind wall jack 3A-18: wiring/cable documentation.
- Explain VLAN-to-cloud-firewall traffic flow: logical diagram.
- Locate a router in rack unit 22: rack elevation diagram.
- Check whether a /24 is nearly full: IPAM utilization.
- Identify channel overlap in a conference area: wireless heat map.
A technician needs to identify which switchport connects to a specific wall jack before moving a user to a new VLAN. Which documentation is most directly useful?
Which record is the authoritative source for whether a /24 subnet is nearly exhausted and which addresses are reserved versus dynamically leased?
Which diagram best shows VLANs, routing relationships, firewalls, and traffic paths without focusing on rack location?