This chapter covers the three primary types of network diagrams essential for CompTIA Network+ N10-009: physical, logical, and wiring diagrams. Understanding these diagrams is critical for network documentation, troubleshooting, and design — topics that appear in approximately 10-15% of exam questions under Domain 3.0 (Network Operations), specifically Objective 3.1. Mastering these diagram types will help you interpret existing documentation, create accurate representations of networks, and identify misconfigurations during exams and in real-world scenarios.
Jump to a section
Think of network diagrams as the architectural blueprints for a building. A physical diagram is like the floor plan showing exactly where each wall, door, and electrical outlet is located, including the types of materials used. A logical diagram is like the electrical schematic that shows how circuits connect, which switches control which lights, and the flow of power, without caring about the physical path of the wires. A wiring diagram is like the detailed wiring plan an electrician uses, showing every cable run, junction box, and termination point. Just as a contractor uses the floor plan to know where to build walls and the electrician uses the schematic to wire circuits, network engineers use physical diagrams to know device locations and cable runs, logical diagrams to understand traffic flow and addressing, and wiring diagrams to troubleshoot cabling. Without these diagrams, you'd be guessing where cables go or how devices communicate — leading to costly mistakes and downtime.
1. What Are Network Diagrams and Why Do They Exist?
Network diagrams are visual representations of network infrastructure that document how devices are connected, how data flows, and how cabling is physically installed. They exist to provide a common reference for network engineers, technicians, and stakeholders to plan, deploy, troubleshoot, and maintain networks. Without diagrams, organizations rely on tribal knowledge, leading to costly errors during changes, prolonged outages, and security gaps. The N10-009 exam expects you to distinguish between physical, logical, and wiring diagrams and know when to use each.
2. Physical Network Diagrams
A physical network diagram shows the physical layout of network devices and cabling. It includes:
Device locations (e.g., rack number, room, floor)
Device models and serial numbers
Cable types (e.g., Cat5e, Cat6, fiber single-mode/multi-mode)
Cable paths and lengths
Power sources and UPS connections
Physical ports and interfaces used
How it works: The diagram is a top-down or rack-elevation view. Each device is represented as an icon or rectangle, with lines representing cables. Labels indicate cable labels, port numbers, and sometimes speed. Physical diagrams are used for:
Rack and stack planning
Cable management
Hardware inventory
On-site troubleshooting (e.g., finding a specific patch panel)
Key components: - Rack elevation diagrams: Show the front view of equipment racks with device positions (U positions). - Floor plans: Show the building layout with network closets, cable pathways, and device placements. - Cable schedules: Tables listing cable IDs, source, destination, type, length, and test results.
Example scenario: A data center with 10 racks. The physical diagram shows that Server A in Rack 3, U12 connects to Switch B in Rack 5, U20 via a 10-meter Cat6a patch cable.
3. Logical Network Diagrams
A logical network diagram shows how devices communicate, focusing on addressing, routing, and protocols. It does not include physical details like cable types or locations. Instead, it includes:
IP subnets and VLANs
Routing protocols (e.g., OSPF, BGP)
Network segments and broadcast domains
Firewall rules and ACLs
Traffic flows and data paths
Logical topologies (e.g., star, mesh, hybrid)
How it works: The diagram abstracts away physical connections. For example, a logical diagram might show a single line between a router and a firewall, even if physically there are multiple cables and switches in between. Logical diagrams are used for:
Network design and architecture
Traffic analysis and optimization
Security planning (e.g., identifying zones)
Troubleshooting routing and switching issues
Key components: - IP addressing scheme: Subnet IDs, gateway addresses, DHCP scopes. - VLAN assignments: Which VLANs exist, their purpose (e.g., VLAN 10 – Management, VLAN 20 – Guest Wi-Fi). - Routing table summaries: Route prefixes and next-hop addresses. - Security zones: DMZ, internal, external, with firewall rules.
Example scenario: A logical diagram shows that the 10.1.1.0/24 subnet is VLAN 10 on Switch A, and all traffic to the internet goes through Router B via a default route. This helps when adding a new subnet — you know where to configure routing.
4. Wiring Diagrams
A wiring diagram (also called a cabling diagram or patch panel diagram) focuses on the physical cabling infrastructure. It shows:
Patch panel ports and their destinations
Wall jacks and their patch panel connections
Cable runs between rooms, floors, or buildings
Punch-down blocks and termination points
Cable labels and colors
How it works: Wiring diagrams are typically created during installation and updated when changes occur. They are essential for:
Identifying which patch panel port connects to which wall jack
Troubleshooting connectivity issues (e.g., tracing a dead port)
Planning new cable runs
Managing cable inventory
Key components: - Patch panel layout: Port numbers, labels, and cable IDs. - Cable routing: Horizontal and vertical cable managers, conduit paths. - Demarcation points: Where the service provider's network ends and the customer's begins. - Testing results: Certification test results (e.g., pass/fail, length, attenuation).
Example scenario: A user reports no connectivity at desk 3A. The wiring diagram shows that wall jack 3A is patched to patch panel port 12 in the IDF closet, which connects to Switch Port 12. You can quickly verify the cable and port.
5. How Diagrams Interact with Related Technologies
Network Documentation: Diagrams are part of the broader documentation set, which includes configuration files, inventories, and change logs. They must be kept in sync with the actual network.
Change Management: Before making changes, engineers review diagrams to understand impact. After changes, diagrams are updated.
Troubleshooting: Diagrams help isolate problems. For example, a logical diagram reveals that traffic should go through a firewall, but a physical diagram shows the cable connecting the firewall is damaged.
Network Monitoring: Diagrams can be integrated with monitoring tools to show real-time status (e.g., link up/down, utilization).
6. Creating and Maintaining Diagrams
Tools: Visio, Lucidchart, draw.io, AutoCAD (for physical layouts). Best practices:
Use standard icons (Cisco, generic network symbols)
Include a legend for symbols and colors
Use consistent naming conventions (e.g., device hostnames, cable labels)
Keep diagrams in a centralized repository with version control
Update diagrams after every change
Include metadata: date created, author, revision history
7. Exam Relevance for N10-009
Objective 3.1: "Given a scenario, use the appropriate network diagram types to document a network." The exam tests your ability to:
Identify whether a diagram is physical, logical, or wiring based on its content.
Choose the correct diagram type for a given task (e.g., planning IP addressing → logical; tracing a cable fault → physical or wiring).
Interpret diagrams to answer questions about connectivity or configuration.
Recognize common diagram symbols and their meanings.
Common traps: - Confusing logical and physical diagrams — remember: physical shows cables and locations; logical shows addressing and protocols. - Thinking wiring diagrams are the same as physical — wiring diagrams focus on cabling details, while physical diagrams include device placement and overall layout. - Overlooking the importance of labels and documentation — the exam may present a diagram missing key information and ask what is needed.
8. Verification and Configuration Commands
While diagrams are not configured via CLI, the following commands help gather information to create or validate diagrams:
show running-config (Cisco) — get interface configurations, VLANs, IP addresses.
show ip interface brief — list interfaces and their status.
show cdp neighbors (Cisco) — discover directly connected devices and their interfaces.
show lldp neighbors — similar to CDP but vendor-neutral.
traceroute — understand logical paths.
ping — test connectivity.
arp -a — see IP to MAC mappings.
netstat -r — view routing table.
For cabling:
- show interface — check link status and speed.
- Cable testers (e.g., Fluke) — verify wiring continuity, length, and faults.
9. Standards and Best Practices
TIA/EIA-606-A: Standard for labeling and documentation.
ANSI/TIA-568: Cabling standards (Cat5e, Cat6, etc.).
Use BICSI or TIA symbols for consistency.
Maintain as-built diagrams: diagrams updated to reflect the actual installation after completion.
10. Summary of Key Differences
| Aspect | Physical Diagram | Logical Diagram | Wiring Diagram | |--------|------------------|----------------|----------------| | Focus | Device locations, cables | IP addressing, protocols | Cable terminations, patch panels | | Use case | Rack layout, cable management | Network design, troubleshooting | Troubleshooting physical connectivity | | Includes | Rack numbers, cable types | Subnets, VLANs, routing | Port numbers, cable IDs | | Abstraction | Low (shows physical reality) | High (abstracts physical) | Very high (only cabling) |
11. Advanced Considerations
Hybrid diagrams: Some diagrams combine physical and logical elements (e.g., a rack elevation with VLAN labels). The exam may test if you can identify the primary purpose.
Virtualization: Diagrams for virtual networks (e.g., VMware vSwitch, virtual routers) are logical but may include host physical details.
Cloud networking: Diagrams may show VPCs, subnets, and virtual gateways — these are logical but often include physical regions/availability zones.
12. Common Diagram Symbols (Exam Familiarity)
Router: Circle with arrows
Switch: Rectangle with arrows
Firewall: Brick wall symbol
Server: Tower or rack icon
Wireless access point: Antenna symbol
Cloud: Cloud shape (internet or WAN)
Patch panel: Rectangle with multiple ports
Cable: Solid line (physical) or dashed line (logical)
13. Conclusion
Understanding the differences between physical, logical, and wiring diagrams is essential for the N10-009 exam and real-world network management. Physical diagrams show the "where," logical diagrams show the "how," and wiring diagrams show the "what connects to what." Each serves a distinct purpose, and using the wrong type can lead to confusion and errors. Always ensure diagrams are accurate, up-to-date, and properly labeled.
Identify the diagram purpose
Before creating or interpreting a diagram, determine its intended use. For example, if you need to plan IP subnet allocation, you need a logical diagram. If you need to locate a specific cable run, you need a physical or wiring diagram. The N10-009 exam often presents a scenario and asks which diagram type is most appropriate. Always match the diagram to the task: physical for hardware placement, logical for addressing/routing, wiring for cabling details.
Gather network information
Collect data from network devices using commands like 'show running-config', 'show ip interface brief', 'show cdp neighbors', and 'show vlan'. For physical information, inspect racks, label cables, and use cable testers. This step is crucial because diagrams are only as good as the data they represent. Incomplete or outdated information leads to inaccurate diagrams. Document device models, serial numbers, firmware versions, and physical locations.
Choose the appropriate diagram type
Based on the purpose and gathered data, select the diagram type. For a new network design, start with a logical diagram to plan addressing and routing, then create a physical diagram for installation. For troubleshooting a connectivity issue, use a physical or wiring diagram to trace cables. For security audits, use logical diagrams to review firewall rules and segmentation. The exam tests your ability to choose the right type for a given scenario.
Create the diagram using standard symbols
Use consistent symbols (e.g., Cisco icons or generic network symbols) and include a legend. For physical diagrams, show rack elevations with device U positions. For logical diagrams, group devices by subnet or VLAN. For wiring diagrams, map patch panel ports to wall jacks. Label all elements clearly with hostnames, IP addresses, cable IDs, and port numbers. Use color coding if helpful (e.g., red for critical links).
Validate and update the diagram
After creation, verify the diagram against the actual network. Walk through the physical environment to confirm cable runs and device locations. For logical diagrams, test connectivity and routing paths using ping and traceroute. Ensure the diagram matches the live network. Update the diagram after any change (e.g., adding a new switch, changing VLAN assignment). Version control and date stamps are essential. The exam may present a diagram with errors and ask you to identify them.
Scenario 1: Data Center Migration
A company is migrating from an old data center to a new one. The network team uses physical diagrams to plan the rack layout in the new facility. They have rack elevation diagrams showing each server's U position, cable lengths, and power requirements. Without these diagrams, they would have to measure every cable and guess equipment placement, leading to delays and cable clutter. During migration, they use logical diagrams to reconfigure VLANs and routing to match the new IP scheme. They also use wiring diagrams to ensure patch panels are terminated correctly. A mislabeled cable in the wiring diagram caused a critical server to be disconnected for hours — highlighting the need for accurate documentation.
Scenario 2: Troubleshooting a Slow Network
A branch office reports slow network performance. The engineer first reviews the logical diagram to understand the traffic path: users connect to a switch, which connects to a router, then to a WAN link. The logical diagram shows QoS settings and bandwidth allocations. Next, the engineer uses the physical diagram to identify the switch model and its uplink port. Finally, a wiring diagram reveals that the uplink cable is a Cat5e run of 95 meters (near the 100m limit) and is experiencing high attenuation. Replacing it with a Cat6a cable resolves the issue. Without the wiring diagram, the engineer might have focused on configuration rather than the physical layer.
Scenario 3: Network Security Audit
During a security audit, the auditor requests logical diagrams to verify network segmentation. The diagrams show VLANs for guest Wi-Fi, internal users, and servers, with firewall rules between them. The auditor uses the logical diagram to check if there are any unauthorized paths between sensitive and untrusted zones. The physical diagram is used to confirm that the firewall is physically inline. A discrepancy is found: the logical diagram shows a firewall between the DMZ and internal network, but the physical diagram shows a direct cable from the DMZ switch to the core switch. This misconfiguration is fixed, preventing a potential breach. Accurate diagrams are critical for compliance (e.g., PCI DSS, HIPAA).
What N10-009 Tests
Objective 3.1: "Given a scenario, use the appropriate network diagram types to document a network." The exam expects you to:
Distinguish between physical, logical, and wiring diagrams based on their content.
Select the correct diagram type for a specific task (e.g., planning IP addressing → logical; locating a cable fault → physical/wiring).
Interpret diagrams to answer questions about device connections, IP addressing, or cabling.
Identify missing information or errors in a given diagram.
Common Wrong Answers and Why Candidates Choose Them
Confusing logical and physical diagrams: Candidates see IP addresses on a diagram and think it's physical, but IP addresses are logical. Physical diagrams show cables and locations, not IPs.
Thinking wiring diagrams are the same as physical: Wiring diagrams focus on termination points (patch panels, wall jacks), while physical diagrams include device placement and overall topology. The exam may show a diagram with only patch panel ports and ask what type it is.
Overlooking the need for labels: A diagram without labels (e.g., no hostnames, no port numbers) is incomplete. Candidates may assume it's acceptable, but the exam tests that diagrams must include key identifiers.
Choosing the wrong diagram for troubleshooting: For a problem with DHCP, a logical diagram is needed (to see VLANs, DHCP server location). But candidates might choose a physical diagram because they think the issue is cabling.
Specific Numbers, Values, and Terms
Cable lengths: Cat5e/Cat6 maximum 100 meters (328 feet) for twisted pair.
Standards: TIA/EIA-606A for labeling, ANSI/TIA-568 for cabling.
Symbols: Recognize standard network icons (router, switch, firewall, cloud).
Diagram types: Physical, logical, wiring (also called cabling diagram or patch panel diagram).
Rack units: 1U = 1.75 inches.
Edge Cases
Virtual networks: A diagram of a virtual switch (e.g., VMware vSwitch) is a logical diagram, even though it runs on a physical host. The exam may try to trick you by placing virtual devices in a physical context.
Hybrid diagrams: Some diagrams mix physical and logical elements. The exam expects you to identify the primary purpose. For example, a diagram showing rack elevations with VLAN labels is primarily physical, but includes logical info.
Cloud diagrams: Diagrams of cloud networks (AWS VPC, Azure VNet) are logical, but they may include physical regions. Know that cloud diagrams are typically logical.
How to Eliminate Wrong Answers
If the scenario involves cabling, patch panels, or physical locations, eliminate logical diagrams.
If the scenario involves IP addresses, subnets, VLANs, or routing, eliminate physical and wiring diagrams.
If the scenario involves tracing a specific cable from a wall jack to a patch panel, choose a wiring diagram.
If the diagram shows only ports and cable IDs without device icons, it's a wiring diagram.
If the diagram shows device positions in a rack, it's a physical diagram (rack elevation).
Physical diagrams document hardware locations, cabling, and physical topology; logical diagrams document IP addressing, VLANs, and routing; wiring diagrams document cable terminations and patch panel connections.
The N10-009 exam tests your ability to select the correct diagram type for a given scenario (e.g., planning IP addressing → logical; tracing a cable fault → physical or wiring).
All diagrams must include clear labels (hostnames, port numbers, cable IDs) and a legend for symbols.
Common exam traps include confusing logical and physical diagrams, and thinking wiring diagrams are the same as physical diagrams.
Cable length limit for twisted pair is 100 meters (328 feet) — this may appear in diagram-based questions.
Diagrams must be kept up-to-date; outdated diagrams can cause misconfigurations and outages.
Standard diagram symbols (router, switch, firewall, cloud) are used — recognize them for the exam.
These come up on the exam all the time. Here's how to tell them apart.
Physical Diagram
Shows device locations, rack units, and cable paths.
Includes cable types (e.g., Cat6, fiber) and lengths.
Used for hardware installation and inventory.
Does not show IP addresses or VLANs.
Often uses rack elevation views or floor plans.
Logical Diagram
Shows IP subnets, VLANs, and routing protocols.
Includes traffic flows and security zones.
Used for network design and troubleshooting logical issues.
Does not show physical cable details.
Often uses high-level topology diagrams with clouds.
Mistake
Physical diagrams show IP addresses and VLANs.
Correct
Physical diagrams focus on hardware locations and cabling, not IP addressing. IP addresses and VLANs belong on logical diagrams.
Mistake
Logical diagrams are only for routing protocols.
Correct
Logical diagrams include all Layer 3 and 2 logical constructs: IP subnets, VLANs, ACLs, NAT, and traffic flows. They are not limited to routing.
Mistake
Wiring diagrams are the same as physical diagrams.
Correct
Wiring diagrams are a subset of physical documentation that detail cable terminations, patch panel ports, and wall jacks. Physical diagrams include device placement, rack layouts, and overall topology.
Mistake
Diagrams are only needed during initial installation.
Correct
Diagrams must be maintained as living documents throughout the network lifecycle. Outdated diagrams are worse than no diagrams because they mislead engineers.
Mistake
A diagram with device icons is always a physical diagram.
Correct
Logical diagrams also use device icons (e.g., router, firewall) but omit physical details like cable types and locations. The presence of icons alone doesn't determine the type; the content does.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
A physical diagram shows the actual hardware layout: device locations, rack positions, cable types, and physical connections. A logical diagram shows how data flows: IP subnets, VLANs, routing protocols, and security zones. The physical diagram answers 'where is it?' and the logical diagram answers 'how does it communicate?'.
A wiring diagram should include patch panel port numbers, wall jack locations, cable IDs, cable types, termination points (e.g., punch-down blocks), and sometimes test results. It is used to trace physical cabling from end to end.
Use a logical diagram when planning IP addressing, VLAN segmentation, routing protocols, firewall rules, or traffic flows. Use a physical diagram when planning hardware installation, cable management, or troubleshooting physical connectivity.
You don't need to create diagrams on the exam, but you must interpret them. Focus on recognizing diagram types, identifying missing information, and selecting the correct diagram for a scenario. Know standard symbols and common labels.
A rack elevation diagram is a type of physical diagram that shows the front view of equipment racks, with devices placed in specific U positions. It includes device heights, model numbers, and often port numbering. It is used for rack planning and hardware inventory.
Yes, some hybrid diagrams combine elements of both, but they are typically categorized by their primary purpose. The exam expects you to identify the main type. For example, a rack diagram with VLAN labels is still primarily physical.
Common tools include Microsoft Visio, Lucidchart, draw.io (free), AutoCAD (for detailed physical layouts), and network management software that auto-generates diagrams (e.g., SolarWinds, PRTG).
You've just covered Network Diagram Types: Physical, Logical, Wiring — now see how well it sticks with free N10-009 practice questions. Full explanations included, no account needed.
Done with this chapter?