This chapter covers network topology documentation, a critical skill for CompTIA A+ technicians that appears in roughly 5-8% of the 220-1102 exam questions under Objective 4.1 (Operational Procedures). You will learn the difference between physical and logical topologies, how to read and create accurate diagrams, and the documentation types that support network management. Mastering this material ensures you can troubleshoot efficiently, communicate network structure to colleagues, and avoid common exam traps about topology types and their characteristics.
Jump to a section
Network topology documentation is like a city's transit map and engineering blueprints combined. The logical topology is the subway map — it shows how stations (devices) connect via lines (virtual paths), ignoring the actual street layout. The physical topology is the detailed civil engineering plan showing exact cable trenches, junction boxes, and building entry points. Just as a subway map helps passengers plan routes without knowing every street, a logical topology diagram helps technicians understand traffic flow. The physical diagram is essential for maintenance crews — they need to know exactly where a fiber cable is buried to avoid cutting it during construction. A network without documentation is like a city without maps: when a connection fails, you have no idea which cables run where, which devices depend on which switches, or where to even start troubleshooting. The documentation must be kept current — a map from 1995 showing a streetcar line that no longer exists is worse than useless, just as a network diagram showing a decommissioned server can mislead technicians into hours of wasted effort.
What Is Network Topology Documentation?
Network topology documentation is the practice of creating and maintaining records that describe how a network is physically and logically structured. It includes diagrams, spreadsheets, configuration files, and inventory lists that capture the arrangement of devices, cabling, IP addressing, and data flow paths. For the CompTIA A+ 220-1102 exam, you must understand the distinction between physical and logical topologies, the common topology types (star, bus, ring, mesh, hybrid), and the documentation artifacts that support network operations.
Why It Matters
Accurate topology documentation enables rapid troubleshooting, change management, and capacity planning. When a user reports a connectivity issue, a technician can consult the physical topology diagram to locate the nearest switch and cable path, and the logical topology to verify VLAN assignments and routing. Without documentation, troubleshooting becomes guesswork. The exam tests your ability to identify the correct documentation type for a given scenario and to recognize the characteristics of each topology.
Physical vs. Logical Topology
Physical Topology: The actual layout of cables, devices, and interconnections. It shows where each device is located, how cables run (e.g., through ceilings, under floors), and the physical ports used. Examples include a rack diagram showing patch panel connections or a floor plan with cable routes.
Logical Topology: How data flows through the network regardless of physical placement. It shows IP subnets, VLANs, routing protocols, and traffic paths. For example, a logical diagram might show that all workstations in department A are on VLAN 10, even if they are physically scattered across multiple floors.
Common Topology Types
Star Topology: All devices connect to a central hub or switch. This is the most common topology in modern Ethernet networks. The central device acts as a concentration point. Failure of the central device isolates all connected nodes, but a failure of a single cable affects only that node. Star topology is easy to troubleshoot because each device has a dedicated cable.
Bus Topology: All devices share a single communication line (the bus). Data travels in both directions; terminators at each end absorb signals to prevent reflection. Bus topology is obsolete in modern networks but appears on the exam. A break in the bus brings down the entire segment. Coaxial cable was the typical medium.
Ring Topology: Each device connects to two neighbors, forming a closed loop. Data travels in one direction (or both in dual-ring designs like FDDI). A single break can disrupt the entire ring unless the network uses a redundant ring or self-healing mechanism (e.g., Token Ring with MSAUs). Modern ring topologies appear in SONET/SDH and some fiber networks.
Mesh Topology: Every device connects to every other device. Full mesh provides maximum redundancy but is impractical for large networks due to cabling costs. Partial mesh is more common — only critical devices have redundant links. Mesh is used in WAN backbones and data center fabrics.
Hybrid Topology: A combination of two or more topologies. For example, a corporate network might use star topologies within each department (local switches) and a mesh or ring topology between core switches. The exam expects you to recognize that most real networks are hybrids.
Documentation Types
Network Diagrams: Visual representations of topology. They can be created with tools like Microsoft Visio, draw.io, or even pen and paper. Diagrams should include device labels, IP addresses, interface names, cable types, and link speeds. A good diagram uses consistent symbols (e.g., a switch icon, a server icon) and includes a legend.
Wiring Diagrams: Detailed physical cabling information, including patch panel port mappings, cable labels, and termination points. These are essential for moves, adds, and changes (MACs).
Site Survey Reports: Documents that capture wireless signal strength, interference sources, and access point placement. For wired networks, site surveys include cable path lengths and conduit usage.
Asset Management/Inventory: A list of all network devices with serial numbers, model numbers, firmware versions, and locations. This supports warranty tracking and patch management.
Configuration Backups: Copies of device configurations (switch, router, firewall). These allow quick restoration after a failure. The exam emphasizes the importance of backing up configurations separately from topology diagrams.
IP Address Management (IPAM): A structured record of IP address assignments, subnets, and DHCP scopes. Tools like spreadsheets or dedicated IPAM software prevent address conflicts.
Creating Effective Documentation
When creating topology documentation, follow these best practices:
Use standardized symbols (e.g., Cisco icons or generic network symbols).
Include a legend explaining symbols and abbreviations.
Label all cables at both ends with unique identifiers.
Record device names, IP addresses, and firmware versions.
Update documentation whenever changes are made — use a change control process.
Store documentation in a secure, accessible location (e.g., shared drive, wiki).
Use different layers: physical floor plan, logical VLAN diagram, and WAN connectivity map.
Interpreting Topology Diagrams
The exam may present a diagram and ask you to identify the topology type, locate a failure point, or determine which device is affected. For example, a star topology diagram shows a central switch with lines to each computer. If the exam shows a break in one line, only that computer loses connectivity. If the break is at the switch, all connected devices are affected. Understanding these cause-and-effect relationships is critical.
Common Tools
Microsoft Visio: Industry standard for professional diagrams.
Lucidchart: Cloud-based alternative with collaboration features.
draw.io (diagrams.net): Free, open-source tool.
Ethernet cable testers: Used to verify physical connections and label cables.
Network mapping software: Tools like Nmap, SolarWinds, or Spiceworks can automatically discover devices and generate topology maps.
Interaction with Other Technologies
Topology documentation supports: - Troubleshooting: Knowing the physical path helps isolate faults. - Change Management: Before adding a new switch, review the physical topology to ensure power and cabling are available. - Security: Physical topology diagrams help identify vulnerable points (e.g., exposed network drops). - Disaster Recovery: Documentation guides restoration of connectivity after a disaster.
Exam-Relevant Numbers and Values
Maximum segment length for 1000BASE-T (Cat5e/Cat6): 100 meters.
Maximum number of nodes on a 10BASE2 (ThinNet) bus segment: 30.
Maximum distance for a single-mode fiber link (1000BASE-LX): 5 km (long-haul) or 10 km (depending on optics).
Termination resistance for coaxial bus: 50 ohms.
Common star topology uses: Ethernet switches with UTP cabling.
Verification and Configuration Commands
While topology documentation is not configured per se, you can verify physical connectivity with:
- ipconfig (Windows) / ifconfig (Linux) — shows IP address and subnet.
- ping — tests logical connectivity.
- tracert / traceroute — shows the logical path between devices.
- show interfaces (on managed switches) — shows link status and traffic counters.
- show vlan — displays VLAN assignments (logical topology).
For example, to verify the physical topology matches documentation, you could use:
C:\>ipconfig
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : example.local
IPv4 Address. . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1Then trace the cable from the PC's NIC to the patch panel, verify the patch panel port number matches the documentation, and check the switch port status:
Switch# show interfaces status | include Gi0/1
Gi0/1 connected 1 a-full a-1000 10/100/1000BaseTXCommon Pitfalls
Confusing physical and logical topologies: A network may be physically a star (all cables to a central switch) but logically a bus (if using a hub or if the switch is configured as a single collision domain — though switches eliminate this).
Assuming all star networks use switches: Hubs also create a star physical topology but behave as a logical bus (shared bandwidth).
Ignoring cable labels: Without labels, tracing a cable during troubleshooting is time-consuming.
Outdated documentation: The most common real-world problem. Always update diagrams after changes.
Exam Trap Patterns
The exam may describe a scenario where a single cable cut disables only one workstation (star) vs. disabling the entire network (bus).
A question might ask which topology is most fault-tolerant: mesh (redundant paths) or star (single point of failure at central device).
Be careful with hybrid topologies: The exam might describe a network that uses star wiring but has a logical ring (e.g., FDDI).
Pay attention to the medium: Coaxial cable is associated with bus topology; UTP/STP with star; fiber can be star, ring, or mesh.
Summary of Key Points
Physical topology = actual cable layout; logical topology = data flow.
Star is most common; bus is obsolete but tested.
Documentation includes diagrams, wiring records, IPAM, and configuration backups.
Always label cables and keep documentation current.
Use ipconfig, ping, tracert, and switch commands to verify topology.
This foundational knowledge will help you answer topology-related questions on the 220-1102 exam and perform network troubleshooting in real-world environments.
Identify Network Requirements
Before creating documentation, determine the scope: which devices, segments, and locations to include. Interview stakeholders (network admins, facilities) to understand the current state and any planned changes. Gather existing diagrams, asset lists, and IP address records. This step sets the foundation — missing a critical device leads to incomplete documentation. For the exam, understand that documentation should cover all managed devices, including switches, routers, firewalls, access points, and servers.
Survey Physical Infrastructure
Physically inspect the site to verify cable runs, device locations, and patch panel connections. Use a cable tester to confirm continuity and label cables at both ends. Record the exact model and serial number of each device. Take photos of racks and wiring closets. This step ensures the physical topology diagram reflects reality. The exam emphasizes the importance of labeling — unlabeled cables are a common source of errors.
Document Logical Topology
Using information from device configurations (e.g., VLANs, IP subnets, routing tables), create a logical diagram. Show how data flows between subnets, which VLANs exist, and how traffic is routed. Include default gateways, DNS servers, and DHCP scopes. Logical topology is often more important for troubleshooting than physical. The exam tests your ability to interpret logical diagrams — for example, identifying which devices are on the same VLAN.
Create and Validate Diagrams
Use diagramming software to draw both physical and logical topologies. Include a legend, device labels, IP addresses, and link speeds. Validate the diagrams by comparing them to actual device configurations and physical observations. Have a second person review for accuracy. The exam may present a diagram with errors (e.g., mismatched IP addresses) — you must spot the discrepancy.
Maintain and Update Documentation
Implement a change management process that requires documentation updates whenever a device is added, removed, or reconfigured. Store diagrams in a version-controlled repository. Schedule periodic audits to verify accuracy. Outdated documentation is worse than none — it leads to incorrect troubleshooting. The exam stresses that documentation must be kept current, and that backups of configurations should be part of the documentation set.
Enterprise Deployment Scenarios
Scenario 1: Data Center Migration A financial services firm is moving its primary data center to a new facility. The network team relies on physical topology diagrams that show every cable path from servers to top-of-rack switches, aggregation switches, and core routers. They also have logical diagrams indicating VLANs for production, DMZ, and management. During the migration, they use these diagrams to pre-cable the new racks and verify connectivity with a cable tester. Without accurate documentation, they risk misconnecting critical financial trading systems, causing hours of downtime.
Scenario 2: Office Expansion A growing tech company is adding a new wing to its headquarters. The facilities team needs to know where existing network cables run to avoid cutting them during construction. They consult the physical topology documentation, which includes a floor plan overlay showing cable conduits and access points. The network team uses the logical topology to plan VLANs for the new departments. They update the documentation as new cables are pulled and switches installed. Common pitfalls include failing to label new cables immediately — leading to a 'spaghetti' of unidentifiable wires.
Scenario 3: Security Incident Response A hospital experiences a ransomware attack that encrypts files on several servers. The security team needs to isolate the affected segment quickly. They refer to the logical topology diagram to identify which VLANs are compromised and which switches connect them. The physical diagram shows the exact location of the edge switch where the attacker likely gained access (a public kiosk). They disconnect the switch port and block the VLAN at the core. Accurate documentation reduces containment time from hours to minutes. Misconfigured documentation (e.g., wrong VLAN assignments) could lead to partial isolation, allowing the attack to spread.
Performance Considerations Large enterprise networks may have thousands of devices. Manual diagramming becomes impractical; automated tools like SolarWinds Network Topology Mapper or Cisco DNA Center can discover devices and generate maps. However, these tools may miss unmanaged switches or devices not responding to SNMP. A hybrid approach — automated discovery plus manual validation — is best. Documentation should be stored in a central repository accessible to all IT staff, with backups offsite.
Common Misconfigurations - Labeling cables with inconsistent naming (e.g., 'Server1' vs. 'SRV-01'). - Failing to update diagrams after a VLAN change. - Not including backup links or redundant paths in diagrams. - Using proprietary symbols without a legend.
What Goes Wrong When documentation is inaccurate, technicians waste time tracing cables, misconfigure devices, or cause outages. For example, a technician might unplug a cable thinking it's a test line, only to discover it connects to a production database server. Proper documentation prevents these costly errors.
Exam Focus for 220-1102 Objective 4.1
What the Exam Tests The CompTIA A+ 220-1102 exam covers network topology documentation under Objective 4.1: 'Given a scenario, implement basic change-management best practices.' Questions may ask you to identify the appropriate documentation type for a given task (e.g., 'Which document shows the physical location of network drops?'), compare topology types, or interpret a diagram to determine the impact of a failure. Expect 2-4 questions on this topic.
Common Wrong Answers and Why 1. Confusing physical and logical topologies: A question might describe a network that uses a star physical topology but a logical bus (hub). Candidates often assume star means switched, but hubs create a shared medium. The correct answer is that the physical topology is star, logical is bus. 2. Choosing 'ring' for Ethernet networks: Many candidates think Ethernet uses ring topology because of Token Ring's legacy. Modern Ethernet is star. Ring appears in fiber networks (FDDI) or WAN rings. 3. Believing mesh is used in LANs: Full mesh is impractical; most networks use partial mesh or star. The exam may ask which topology provides the most redundancy — full mesh is correct, but candidates might choose star because it's common. 4. Underestimating documentation importance: A scenario question might ask what to do before adding a new switch. The correct answer is 'consult the physical topology diagram to verify cabling and power.' Wrong answers include 'just plug it in' or 'update the diagram after installation' — the order matters.
Specific Numbers and Terms - Maximum segment length for 1000BASE-T: 100 meters. - Maximum nodes on 10BASE2: 30. - Termination resistance for coaxial: 50 ohms. - Common topology types: star, bus, ring, mesh, hybrid. - Documentation types: network diagram, wiring diagram, site survey, asset inventory, IPAM, configuration backup.
Edge Cases - A network that uses a switch but is configured with a single VLAN and no STP may behave like a logical bus (broadcast domain). However, the exam typically considers switches as creating logical star. - Wireless networks have a physical topology (access points placed in specific locations) but a logical topology that is often a star (clients connect to AP). The exam may ask about documenting wireless coverage maps. - Cloud resources: Documentation should include virtual networks and connections to on-premises. The exam may mention hybrid networks.
How to Eliminate Wrong Answers - If a question asks about the impact of a cable cut, identify the topology: star = single user affected; bus = entire segment down; ring = entire ring down (unless redundant). - For documentation questions, match the scenario to the document: physical location -> wiring diagram; IP address scheme -> IPAM; device inventory -> asset list. - When comparing topologies, remember that mesh has the highest redundancy but highest cost; star is cost-effective but has a single point of failure.
Master these points to confidently answer topology documentation questions on the 220-1102 exam.
Physical topology describes actual cabling; logical topology describes data flow.
Star topology is most common in modern Ethernet networks using switches.
Bus topology uses a single shared medium and is now obsolete but tested.
Ring topology can be unidirectional or bidirectional; FDDI uses dual ring.
Mesh topology provides maximum redundancy but is costly; partial mesh is practical.
Documentation includes network diagrams, wiring records, IPAM, and configuration backups.
Always label cables at both ends and update documentation after any change.
These come up on the exam all the time. Here's how to tell them apart.
Physical Topology
Shows actual cable paths and device locations.
Used for troubleshooting physical connectivity issues.
Includes floor plans, rack layouts, and cable labels.
Requires physical inspection to verify.
Changes when cables are moved or hardware relocated.
Logical Topology
Shows data flow regardless of physical placement.
Used for troubleshooting IP connectivity and routing.
Includes VLANs, subnets, routing protocols.
Derived from device configurations and network maps.
Changes when VLANs or routing policies are modified.
Mistake
Physical and logical topologies are always the same.
Correct
They can differ. For example, a network with a central switch (physical star) may have multiple VLANs creating separate logical broadcast domains. The logical topology describes data flow, not cable layout.
Mistake
A star topology always uses a switch.
Correct
A hub also creates a physical star but operates as a logical bus. The exam tests this distinction — a hub-based network is physically star but logically bus.
Mistake
Ring topology is obsolete and never used.
Correct
While Token Ring is obsolete, ring topologies are still used in fiber-optic networks (SONET/SDH) and some industrial networks. The exam may reference FDDI as a dual-ring example.
Mistake
Mesh topology is commonly used in office LANs.
Correct
Full mesh is impractical due to cabling costs. Partial mesh is used in WAN backbones and data centers, but typical office LANs use star or extended star.
Mistake
Network documentation is only needed for large networks.
Correct
Even small networks benefit from documentation. Without it, troubleshooting takes longer, and changes risk misconfiguration. The exam emphasizes documentation as a best practice for any network.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Physical topology is the actual layout of cables and devices — where they are and how they are physically connected. Logical topology is how data flows through the network, independent of physical arrangement. For example, all computers may connect to a central switch (physical star), but if they are on different VLANs, the logical topology is multiple separate broadcast domains. The exam expects you to distinguish between the two in scenarios.
Full mesh topology provides the highest fault tolerance because every device has a direct connection to every other device — a single link failure does not affect connectivity. However, full mesh is impractical for large networks due to cost. Partial mesh offers a balance: critical devices have redundant links. On the exam, if a question asks for the most redundant topology, the answer is mesh.
You should consult the physical topology diagram to identify available cabling paths, power sources, and rack space. Also review the logical topology to plan VLAN assignments and IP addressing. After installation, update both diagrams and label all new cables. The exam stresses the importance of consulting documentation before making changes.
Cable labeling allows technicians to quickly identify which cable connects to which device. Without labels, tracing a cable during troubleshooting is time-consuming and error-prone. Labels should be unique and consistent (e.g., 'SW1-P1' for switch 1, port 1). The exam includes cable labeling as a best practice in operational procedures.
Documentation should be updated whenever a change is made — whether it's adding a device, moving a cable, changing a VLAN, or updating firmware. Use a change management process to ensure updates are not forgotten. The exam emphasizes that outdated documentation is a common source of errors.
A hybrid topology combines two or more different topologies. For example, a corporate network might use star topologies within each department and a mesh or ring topology between core switches. Most real-world networks are hybrids. The exam expects you to recognize that hybrid topologies are common and to identify the constituent topologies in a given scenario.
Yes. If a network uses a hub instead of a switch, the physical wiring is star (all devices connect to a central hub), but the hub repeats all data to every port, creating a single collision domain — which is a logical bus topology. The exam tests this distinction: hubs create a logical bus; switches create a logical star.
You've just covered Network Topology Documentation — now see how well it sticks with free 220-1102 practice questions. Full explanations included, no account needed.
Done with this chapter?