Networking Concepts
Name the layer, and the topic falls into place
Networking Concepts is the foundation domain, and at 23% it is one of the two heaviest sections of N10-009 (Network Troubleshooting edges it at 24%). Almost everything in it hangs on one tool: the OSI (Open Systems Interconnection) seven-layer model. The model splits one end-to-end conversation into seven stacked layers, from Physical signaling at the bottom (Layer 1) up to the Application at the top (Layer 7), and Network+ uses those layer numbers as its shared vocabulary. A switch is a Layer 2 device because it forwards by MAC address; a router is Layer 3 because it forwards by IP; a port number lives in the Layer 4 transport header. The single most useful habit for this whole domain is to ask of any device, protocol, or address, "which layer does this act on?", because the layer pins the function. The classic trap the model helps you dodge is mixing up boundaries that look alike: a switch breaks collision domains but a router (or a VLAN) breaks the broadcast domain, and confusing the two is a recurring exam miss.
The domain unfolds in nine steps, from the model down to the addressing
Read this page as a map, then follow the nine subtopics in order. OSI Model lays the seven-layer reference and the TCP/IP four-layer model that actually runs the internet, so reach for it first. Networking Appliances names each box by the layer it reads (switch, router, firewall, IDS/IPS, load balancer, proxy, NAS, SAN). Cloud Concepts rebuilds that same network in software inside a virtual private cloud (VPC) and adds the NIST service and deployment models. Ports and Protocols pins each service to a port and a transport, choosing TCP for guaranteed delivery and UDP for speed. Traffic Types sorts every frame into unicast, multicast, anycast, or broadcast. The next three subtopics drop to Layer 1: Transmission Media is the physical path (copper, fiber, wireless) chosen by distance, speed, and interference; Transceivers and Connectors is the swappable optic and the media-specific plug that must match on both ends; Network Topologies is the shape of the network and the redundancy-versus-cost tradeoff behind it. IPv4 Addressing and Subnetting closes the domain with the 32-bit address, the mask that splits network from host, and the magic-number method for subnetting. Each subtopic carries the deep tables, the numbers, and the traps; this overview just shows how they fit together.
Match the choice to the requirement the stem hands you
Across these subtopics the exam rewards the same instinct: it states a priority in the stem (distance, speed, immunity to interference, cost, redundancy, reliability) and expects you to pick the option that fits that priority, not the most powerful one. Copper is cheap and easy but stops at 100 meters; fiber spans far and ignores electromagnetic interference (EMI) but costs more, so a long or noisy run points to fiber. TCP guarantees delivery while UDP is lighter and faster, so a streaming or DNS-lookup scenario leans UDP and a file transfer leans TCP. A full mesh has no single point of failure but its link count grows as n(n-1)/2, while a star is cheap but concentrates the fault at the hub, so the stem's tolerance for failure picks the topology. When two answers both technically work, the correct one is the one that matches the named constraint, and each subtopic shows where the genuine exceptions live.
The nine building blocks of Networking Concepts (and where each is covered)
| Building block | OSI layer(s) it lives at | What it decides | Drill into |
|---|---|---|---|
| The reference model | All seven (Layers 1-7) | How every device, protocol, and PDU maps to a layer | OSI Model |
| Network devices | Layers 2-7 | Which box forwards, filters, or stores, named by the layer it reads | Networking Appliances |
| Cloud networks | Layers 2-7 (virtualized) | Who owns each layer of a network rented inside a provider | Cloud Concepts |
| Services and transports | Layer 4 (with Layer 3 addressing) | Which port and transport (TCP or UDP) identify a service | Ports and Protocols |
| Delivery patterns | Layers 2-3 | Whether a frame reaches one host, a group, the nearest, or all | Traffic Types |
| The physical path | Layer 1 | Reach, speed, and EMI immunity of copper, fiber, or wireless | Transmission Media |
| Optics and plugs | Layer 1 | The swappable transceiver and the connector that must match end to end | Transceivers and Connectors |
| Network shape | Layers 1-3 | The redundancy-versus-cost tradeoff and physical-versus-logical layout | Network Topologies |
| Addresses and subnets | Layer 3 | How the mask splits network from host and how many hosts fit | IPv4 Addressing and Subnetting |