CompTIA Network+ N10-008: Network Topologies and Network Types Explained

Topology matters because it shows you how a network behaves when everything’s working and, just as importantly, how it tends to fall apart when something breaks. For CompTIA Network+, this isn’t just vocabulary you cram the night before and hope for the best. Honestly, you’ve got to slow down and read the scenario all the way through. What I usually tell folks is pretty straightforward: first figure out what kind of network you’re looking at, then ask yourself how far a failure would spread, and finally picture how traffic’s supposed to move through it. Once you’ve got that straight, it’s a lot easier to look at a design and say, ‘Yep, this is the one that actually fits the job.’ This article targets Network+ N10-008 objectives; if you are studying for N10-009, the concepts still apply, but you should verify the current objective wording.

The fastest way to keep this topic straight is to separate four ideas:

Topology = how devices and links are arranged.
Network type = scope or purpose of the network.
Physical topology = actual cables, radios, and ports.
Logical topology = how traffic flows and how networks are segmented.

A useful way to picture this is a physical star layout in which endpoints connect to a central switch, while logical segmentation divides users into VLAN 10 and VLAN 20, with a Layer 3 routing boundary controlling communication between them.

1. Topology vs. network type vs. physical vs. logical

A single environment can include several of these at once. A branch office may have a star LAN physically, VLANs logically, and a WAN connection back to headquarters. That is normal.

Physical topology answers “what is connected to what?” A modern office usually looks like a star because endpoints connect to a central switch.

Logical topology answers “who can talk to whom, and over what path?” A switch stack can physically bring everybody onto the same fabric, but VLANs can still split that fabric into separate logical broadcast domains. Inter-VLAN communication then requires a Layer 3 interface such as a router, router-on-a-stick, or a multilayer switch SVI.

In modern Ethernet, most LANs are physically switched star. Logical segmentation is commonly done with VLANs, trunks, and inter-VLAN routing.

2. Broadcast domains, collision domains, and failure domains

This is one of the most testable parts of the objective.

Broadcast domain: the group of devices that receive a Layer 2 broadcast, such as ARP or DHCP Discover. Switches only flood those broadcasts within the same VLAN, which is exactly why VLAN boundaries matter so much. A router, multilayer switch, or other Layer 3 interface stops that broadcast from crossing into another subnet.

Collision domain: the area where frame collisions can occur. With modern full-duplex switched Ethernet, each switch port is its own collision domain, so collisions are effectively eliminated. Collision problems mainly belong to hubs, half-duplex links, and older shared-media Ethernet.

Failure domain: the part of the network affected when a device or link fails. In a star, one bad access cable usually affects one user, but one failed central switch can affect everyone connected to it.

Quick exam trap: a hub is not the same as a switch. A hub just repeats traffic out every port, so everybody shares one big collision domain. A switch forwards based on MAC addresses and gives each port its own collision domain.

3. Common physical topologies

Star: endpoints connect to a central device, usually a switch. This is the dominant design you’ll see in modern LANs. It’s pretty easy to manage and pretty easy to expand, but that central device can become a single point of failure if you don’t build in redundancy. Common improvements include stacked switches, dual uplinks, link aggregation with LACP, and first-hop redundancy at Layer 3.

Bus: devices share one backbone medium. It is mostly legacy. A break in the backbone can affect all nodes.

Ring: each device connects in a loop. Classic examples include Token Ring and FDDI. Provider environments may also use protected rings in resilient optical transport designs. Important distinction: not every modern ring implies token passing.

Mesh: devices have multiple interconnections. Full mesh connects every node to every other node; partial mesh connects only selected nodes directly. Mesh does improve resiliency, definitely. That said, just because you’ve got alternate links doesn’t mean traffic will automatically choose the right one all by itself. It depends on routing behavior, SD-WAN policy, or whatever control logic is really steering the traffic. Multiple links alone do not guarantee intelligent failover.

Point-to-point: one dedicated link between two devices. Common for uplinks, leased lines, and wireless bridges.

Point-to-multipoint: one central point serves multiple remotes. This is common in provider wireless and can describe AP-to-client access at a high level, but remember that Wi-Fi is a shared RF medium, not a simple wired fan-out model.

Hybrid: a mix of topologies. Most real networks are hybrid.

Spine-and-leaf: a modern data center fabric. In that design, servers connect to leaf switches, and each leaf switch uplinks to every spine switch. Modern implementations commonly use a Layer 3 underlay with ECMP for predictable pathing. It is optimized for east-west traffic, though performance still depends on oversubscription and design choices.

4. Logical behavior in real networks

Logical topology is where traffic behavior matters more than cable shape.

Broadcast traffic behavior: broadcasts are flooded within a broadcast domain or VLAN. That is why large flat VLANs can become noisy.

Switched Ethernet: switches learn MAC addresses and forward unicast traffic only where needed. Unknown unicast traffic may be flooded temporarily until MAC learning completes. Multicast may also be controlled by features such as IGMP snooping rather than being flooded everywhere.

VLAN segmentation: VLANs create separate logical Layer 2 networks over the same physical switching infrastructure. Access ports carry one VLAN for end devices. Trunk ports carry multiple VLANs between switches using 802.1Q tagging. In enterprise design, one VLAN often maps to one IP subnet, though that is a design convention rather than a protocol requirement.

Inter-VLAN routing: if VLAN 10 and VLAN 20 need to communicate, you need a Layer 3 boundary. That can be a router-on-a-stick or a multilayer switch with SVIs.

Common VLAN problems: wrong access VLAN, missing allowed VLAN on a trunk, native VLAN mismatch, or no Layer 3 gateway for the subnet. Those mistakes can isolate one floor or department very quickly.

Loop prevention: if you add redundant Layer 2 links without control, you can create switching loops and broadcast storms. STP/RSTP prevents this by blocking redundant paths until they are needed.

Mini example: A user in VLAN 10 sends ARP for the default gateway. That ARP stays inside VLAN 10 because it’s a broadcast. The multilayer switch SVI for VLAN 10 replies, then routes traffic to VLAN 20 if policy allows it.

5. Common network types

PAN: personal area network. Very short range around one person, such as Bluetooth earbuds or a smartwatch.

LAN: local area network. That’s the local wired network you’d use in one room, one floor, one building, or one site. Usually Ethernet-based and organization-managed.

WLAN: wireless LAN. Same local scope as a LAN, but client access is via Wi‑Fi. In infrastructure mode, clients associate to an AP and communicate through it. Wi‑Fi is contention-based and half-duplex at the RF layer, unlike typical wired switched Ethernet.

CAN: campus area network. Multiple nearby buildings under one organization, usually with fiber uplinks and centralized IT.

MAN: metropolitan area network. That’s the local wireless access network built around Wi‑Fi. CAN stands for campus area network. In real enterprise documentation, the term is less common than LAN or WAN, but it remains an exam category.

WAN: wide area network. Long-distance connectivity across cities, regions, or countries using carrier or internet transport.

SAN: storage area network. A storage networking architecture for block-level storage access, often logically or physically isolated from user traffic. Common implementations include Fibre Channel, iSCSI, and sometimes FCoE. iSCSI runs over IP/Ethernet, so SAN traffic may be isolated by dedicated Ethernet, VLANs, QoS, or separate fabrics rather than always by separate cabling.

SAN vs. NAS: SAN provides block storage over a storage network; NAS provides file access over a normal IP network. For Network+, know the distinction at a high level.

6. WAN, wireless, storage, and cloud: the high-value modern pieces

WAN access methods: MPLS, broadband, leased lines, satellite, and LTE/5G backup are all common WAN transports. Each has tradeoffs in cost, latency, bandwidth consistency, and SLA quality.

SD-WAN: SD-WAN is not the circuit. It’s the overlay and control architecture that sits on top of one or more transport links. It commonly uses centralized orchestration, application-aware path selection, and often encrypted overlays across broadband, MPLS, or cellular links.

Underlay vs. overlay: the underlay is the real transport network. The overlay is the logical network built on top of it, such as VPN or SD-WAN tunnels.

WLAN implementation basics: SSIDs can map to VLANs, so Staff Wi‑Fi and Guest Wi‑Fi can use different logical networks on the same AP infrastructure. Common controls include WPA2/WPA3, and in enterprises often 802.1X. The usual wireless headaches are channel overlap, poor AP placement, RF interference, and coverage gaps. Roaming depends on client behavior and design quality, not magic.

SAN basics: Storage traffic is sensitive to latency, loss, and path instability. Redundancy often includes dual fabrics or dual paths with multipathing. Security controls include zoning and LUN masking.

Cloud virtual networking: Customer-visible cloud networking is logical or virtualized, while the provider still operates a physical underlay. At exam level, know virtual networks, subnets, route tables, security groups, peering, and hybrid connectivity like site-to-site VPN.

7. Security and performance implications

Security: Topology affects trust boundaries. VLANs, ACLs, firewalls, guest isolation, management VLANs, VPNs, WPA2 or WPA3-Enterprise, and SAN zoning all help cut down lateral movement. But VLANs by themselves are not a complete security solution. Misconfiguration and even VLAN hopping risks mean you still need proper Layer 3 controls and policy enforcement.

Performance: In a star or campus network, uplinks can become bottlenecks. In WLANs, airtime contention matters a lot more than the big number on the spec sheet. In WANs, latency and jitter can hurt voice and cloud apps pretty badly. In data centers, oversubscription and ECMP design matter a lot too. In large VLANs, too much broadcast traffic can waste bandwidth and CPU.

8. Troubleshooting playbook by topology/type

Star LAN: check endpoint link light, NIC status, cable, switchport state, VLAN assignment, and default gateway. If many users fail at once, check the access switch, uplink, or power.

Hybrid/campus: if one building or floor is isolated, check fiber uplinks, trunk status, STP state, and distribution-layer interfaces. A failed campus uplink often creates a clean building-level failure domain.

Mesh/WAN: verify interface status, routing adjacency, tunnel state, path policy, and latency/loss on each circuit. Watch for asymmetric routing and backup links masking a degraded primary path.

WLAN: verify SSID, authentication, DHCP, signal strength, channel utilization, and AP placement. If users connect but perform poorly, think interference, contention, or bad roaming.

SAN: verify storage paths, multipathing status, interface errors, latency, zoning, and whether storage traffic is competing with user traffic on shared Ethernet.

Loop symptoms: sudden broadcast storm, MAC table instability, high CPU on switches, and widespread intermittent failure often point to a Layer 2 loop, especially after someone adds an unmanaged switch.

9. Common confusions to avoid

VLAN vs. subnet: a VLAN is a Layer 2 segment; a subnet is a Layer 3 IP network. They commonly map one-to-one, but they are not the same thing.

CAN vs. MAN: campus is multiple nearby buildings under one organization; metro is city-scale connectivity, often provider-based.

SAN vs. LAN: SAN is for storage networking, often block storage access; LAN is for general user and application traffic.

SD-WAN vs. WAN circuit: SD-WAN is the overlay/control method; broadband, MPLS, and LTE are transports.

WLAN vs. topology: WLAN is a network type and access method, not a physical topology category like star or mesh.

10. Exam prep: what N10-008 expects and how to recognize it

Know these cold: star, bus, ring, mesh, point-to-point, point-to-multipoint, hybrid; physical vs. logical topology; PAN, LAN, WLAN, CAN, MAN, WAN, SAN; VLANs and broadcast domains at a recognition level; modern terms such as SD-WAN and spine-and-leaf at a high level.

Recognition cues:

One central switch with many clients = star.
Multiple nearby buildings under one organization = CAN.
City-wide provider connectivity = MAN.
Branches over carrier or internet links = WAN.
Storage traffic and block access = SAN.
Scalable data center east-west traffic = spine-and-leaf.

Mini scenarios:

1. A company has three buildings on one hospital campus connected by fiber to a central core. A building loses connectivity after its uplink gets cut. What network type is this? Answer: CAN. The scope is multiple nearby buildings under one organization.

2. Users on Floor 2 cannot reach printers on Floor 3 after a switch replacement. Both floors connect through a trunk. What’s the most likely issue? The answer is usually some kind of VLAN or trunk misconfiguration. Think missing allowed VLAN, wrong access VLAN, or a native VLAN mismatch.

3. A branch has broadband as the primary link and LTE backup managed by an SD-WAN appliance. The broadband circuit fails, and traffic shifts over automatically. What changed? Answer: the underlay path changed; SD-WAN overlay policy selected the backup transport.

Memory aids: PAN personal, LAN local, CAN campus, MAN metro, WAN wide, SAN storage. Star = spokes to center. Mesh = many paths.

11. Rapid review summary

Topology describes arrangement; network type describes scope or purpose. Physical topology is the actual real-world layout, while logical topology is all about traffic flow and segmentation. Modern Ethernet LANs are usually switched stars. VLANs create logical separation, and if you need communication between VLANs, you’ll need Layer 3 routing. Broadcast domains are bounded by VLANs and Layer 3 interfaces. In full-duplex Ethernet, collision domains are basically one per switch port. Hubs are shared-media legacy devices, not switches.

Bus and ring are mainly legacy for enterprise LANs, though ring ideas still appear in provider resiliency designs. Mesh does improve redundancy, but it also adds cost and complexity. Spine-and-leaf is a modern data center design with predictable leaf-to-spine connectivity and, commonly, ECMP over a Layer 3 underlay. WLANs are local, but they’re still shared and effectively half-duplex at the RF layer. WANs connect distant sites over provider or internet transport. SANs support storage networking and may use Fibre Channel or iSCSI with logical or physical isolation.

If you can identify the traffic pattern, the segmentation boundary, and the failure domain, you can usually identify the topology or network type correctly on the exam and in real troubleshooting.