CompTIA Network+ N10-009 Study Guide

Course: Networking Fundamentals and Physical Networks Source basis: Coursera course videos and readings reviewed on 2026-06-19 Technical audit: All local questions and guide text reviewed on 2026-09-08 against N10-009 and the public primary references below; the original course materials were not re-accessed.

Purpose: Exam-focused study notes for the course modules. This is an original study guide, not a transcript.

How To Use This Guide

1. Read one module at a time.
2. Memorize the "must know" lists first.
3. Use the checklists to identify weak spots.
4. Take the practice question set after reviewing all modules.
5. Review explanations for missed questions, then return to the related section.

High-Yield Memory Anchors

• OSI layers: Physical, Data Link, Network, Transport, Session, Presentation, Application.
• Layer 1 moves bits. Layer 2 uses MAC addresses and frames. Layer 3 uses IP addresses and packets. Layer 4 uses ports and segments/datagrams.
• MAC addresses are 48-bit physical addresses commonly written as 12 hexadecimal characters.
• IPv4 addresses are 32-bit logical addresses commonly written in dotted decimal.
• Ethernet frames are the Layer 2 data unit used on Ethernet LANs.
• A switch forwards frames based on MAC addresses. A hub repeats bits to all ports.
• Star topology is the most common physical LAN topology today.
• UTP is common for Ethernet. Fiber is preferred for long distance, high bandwidth, and EMI resistance.
• T568A and T568B are wiring standards. Use the same standard on both ends for a straight-through cable.
• Full duplex avoids collisions. Half duplex requires collision handling.
• Structured cabling organizes horizontal cabling, patch panels, wall outlets, equipment rooms, and work areas.
• Cable troubleshooting starts with link lights, physical inspection, known-good cables, and the right tester.

Module 1: Network Models

Big Picture

Network models help explain how data moves through a network. They divide a complex communication process into layers, which makes design, troubleshooting, and security easier. The course emphasizes the OSI seven-layer model as a way to reason from the physical cable or radio signal up to the user-facing application.

OSI Model

The OSI model has seven layers:

1. Physical
2. Data Link
3. Network
4. Transport
5. Session
6. Presentation
7. Application

Layer 1: Physical

The Physical layer defines how bits move from one device to another. It includes cabling, connectors, radio frequencies, signaling, voltages, pinouts, and the physical properties of a link.

Know these examples:

• Copper cabling
• Fiber optic cabling
• Wireless radio frequencies
• Connectors such as RJ-45
• Signaling and physical media standards
• Link lights and physical connectivity

Layer 1 problems usually look like no link, damaged cable, bad connector, wrong cable type, excessive distance, broken fiber, EMI, or failed hardware port.

Layer 2: Data Link

The Data Link layer handles local network delivery. Ethernet operates here. Devices use MAC addresses to determine whether a frame is meant for them.

Important Layer 2 concepts:

• Ethernet frames
• Source and destination MAC addresses
• Switch forwarding
• Local delivery on a LAN
• Frame check sequence
• Broadcast and unicast traffic

Layer 2 handles delivery on the local link. An Ethernet receiver normally accepts frames addressed to its MAC, broadcasts, and subscribed multicast destinations. Promiscuous mode changes filtering for authorized capture; destination filtering is separate from checking frame integrity.

Layer 3: Network

The Network layer uses logical addressing. IP is the core Layer 3 protocol for Network+.

Important Layer 3 concepts:

• IPv4 and IPv6 addressing
• Source and destination IP addresses
• Routing between networks
• Packets
• Logical addressing

MAC addresses are useful on the local LAN, but IP addressing is needed for communication across routed networks such as the internet.

Layer 4: Transport

The Transport layer provides application multiplexing through ports. TCP segments a byte stream and reconstructs it in order. UDP preserves datagram boundaries and does not automatically segment a large application message into reliable smaller messages; the application must choose suitable message sizes. IP fragmentation is a separate network-layer function.

Know these Layer 4 ideas:

• TCP and UDP
• Port numbers
• Segmentation and reassembly
• Sessions between applications
• Reliability when using TCP
• Lower overhead when using UDP

The course highlights that Ethernet has a practical payload limit, so large files must be chopped into smaller chunks before transmission.

Layers 5-7: Upper Layers

The upper layers deal with conversations, formatting, encryption, and user-facing network services.

• Session: Establishes, manages, and ends communication sessions.
• Presentation: Handles data formatting, compression, and encryption/decryption.
• Application: Provides network services to user applications, such as web, email, file transfer, and name resolution services.

For Network+, you should know the layers, what each one does, and how to map common protocols/devices/problems to the right layer.

Encapsulation and Decapsulation

When data is sent, each layer adds its own information. This is encapsulation. When data is received, each layer removes and processes its own information. This is decapsulation.

Common data units:

• Bits at Layer 1
• Frames at Layer 2
• Packets at Layer 3
• Segments or datagrams at Layer 4
• Data at upper layers

Ethernet Frame Basics

An Ethernet frame carries data across a local Ethernet network.

Key frame fields to understand:

• Preamble: Signals that a frame is arriving.
• Destination MAC address: Identifies the intended receiver on the local link.
• Source MAC address: Identifies the sender on the local link.
• Type/length field: Identifies the payload type or length.
• Payload: The carried data, often an IP packet.
• Frame check sequence: Helps detect transmission errors.

The frame check sequence does not fix errors by itself. It lets the receiving device detect that a frame was damaged.

MAC Addresses

A MAC address is a 48-bit hardware address used at Layer 2. It is commonly written as six pairs of hexadecimal digits.

Important facts:

• 48 bits total.
• A factory address may be assigned to the interface, but software can use a locally administered or randomized address.
• Used for local LAN delivery.
• Switches learn source MAC addresses and build MAC address tables.
• In common universally administered EUI-48 assignments, the first 24 bits are an organizational identifier (OUI), followed by an organization-assigned suffix.
• A locally administered address is not reliable evidence of the hardware vendor or an immutable device identity.

See RFC 9542 for EUI-48, organizational identifiers, and locally administered address distinctions.

Do not confuse MAC and IP addresses. MAC addresses are local physical/link-layer identifiers. IP addresses are logical network-layer identifiers used across routed networks.

Broadcast vs Unicast

Unicast traffic is one-to-one. A frame is sent to one destination MAC address.

Broadcast traffic is one-to-all within the local broadcast domain. Ethernet broadcast uses destination MAC address FF:FF:FF:FF:FF:FF.

Exam points:

• Switches forward broadcasts out all ports in the same VLAN except the incoming port.
• Routers do not normally forward Layer 2 broadcasts.
• Too much broadcast traffic can hurt performance.
• ARP is a common broadcast-driven process in IPv4 networks.

IP Addressing Introduction

IPv4 addresses are 32-bit logical addresses. They are written in dotted decimal, such as 192.168.1.10.

IP addresses identify:

• The network portion.
• The host portion.

Routers use the network portion to move packets between networks. Hosts use a subnet mask or prefix length to determine whether a destination is local or remote.

Packets and Ports

IP packets carry Layer 4 data. TCP and UDP use port numbers so traffic reaches the correct application or service.

Examples to know:

• HTTP: TCP 80
• HTTPS: TCP 443 for HTTP/1.1 and HTTP/2; HTTP/3 uses QUIC over UDP, commonly 443.
• DNS: UDP/TCP 53
• SSH: TCP 22
• FTP control: TCP 21
• SMTP: TCP 25
• DHCP server/client: UDP 67/68
• TFTP initial read/write request: UDP 69; subsequent transfer packets use selected UDP endpoints.

Ports let one host run many network services at the same IP address.

Transmission Control Protocol (TCP) provides reliable ordered byte-stream delivery and retransmission. User Datagram Protocol (UDP) does not provide retransmission or ordering itself; an application can add its own recovery. A registered port is a conventional service association, not proof of application identity or encryption. Sources reviewed 2026-09-20: IANA service registry, RFC 9293, RFC 768, and RFC 1350.

Module 1 Must Know

• OSI layer order and function.
• Difference between frames, packets, and segments.
• Difference between MAC and IP addresses.
• How encapsulation works.
• What Ethernet frame fields do.
• What broadcast and unicast mean.
• Why ports are needed.

Module 2: Cabling and Topology

Big Picture

Physical network design includes topology, cabling type, connector type, distance, bandwidth, safety ratings, and installation environment. A good design must work electrically or optically, be maintainable, and meet building/fire requirements.

Network Topologies

Bus

All devices share one backbone cable. Older coaxial Ethernet used bus designs.

Pros:

• Simple in small old networks.
• Less cable than some designs.

Cons:

• A break can affect many devices.
• Harder to troubleshoot.
• Shared media limits performance.
• Rare in modern Ethernet LANs.

Ring

Each device connects to two neighbors, forming a loop.

Pros:

• Predictable traffic flow in classic ring systems.

Cons:

• Failure can disrupt the ring unless redundancy exists.
• Not common in modern office Ethernet LANs.

Star

Each device connects to a central device, usually a switch.

Pros:

• Common modern LAN design.
• Easy to add/remove devices.
• Easier troubleshooting.
• A single cable failure usually affects one endpoint.

Cons:

• Central switch is a critical dependency.

Mesh

Devices have multiple interconnections.

Pros:

• High redundancy.
• Useful for backbones, WANs, wireless mesh, and critical links.

Cons:

• More expensive.
• More complex to manage.

Hybrid

Most real networks combine topology ideas. A LAN may be physically star-shaped, while switches may be connected in a partial mesh or hierarchical design.

Coaxial Cabling

Coax uses a central conductor, insulation, shielding, and an outer jacket. It was common in older Ethernet and is still seen in cable internet and video distribution.

Know:

• RG-6 is common for cable TV/cable internet.
• RG-59 is older/thinner and common in some video/security installations.
• BNC connectors are associated with older coax Ethernet.
• F-type connectors are common with cable TV/cable modem use.

Exam value:

• Coax is shielded and can be durable.
• It is not the normal choice for modern switched Ethernet endpoints.

Twisted Pair Cabling

Twisted pair is the most common copper media for Ethernet LANs.

Types:

• UTP: Unshielded twisted pair. Common, inexpensive, flexible.
• STP/FTP variants: Shielded or foil-shielded designs for noisier environments.

Why twist pairs?

• Twisting helps reduce electromagnetic interference and crosstalk.
• Different twist rates reduce interference between pairs.

Common categories:

• Cat 5e: Common for 1 Gbps up to 100 meters.
• Cat 6: Supports 1 Gbps to 100 meters and 10 Gbps at shorter distances.
• Cat 6a: Better support for 10 Gbps up to 100 meters.

Connector:

• 8P8C modular connector, commonly called RJ-45.

Important maximum:

• Conventional four-pair structured cabling uses a maximum 90 m permanent link and a 100 m complete channel, including patch cords. Check the chosen application and installation limits.

Fiber Optic Cabling

Fiber uses light instead of electrical signals.

Advantages:

• Longer distances.
• Higher bandwidth potential.
• Immune to EMI/RFI.
• Harder to tap casually than copper.
• Useful between buildings or in electrically noisy environments.

Types:

• Multimode fiber: Larger core, shorter distances, often used inside buildings and data centers.
• Single-mode fiber: Smaller core, longer distances, often used for campus, metro, and carrier links.

Common connectors:

• LC: Small form factor, very common with modern transceivers.
• SC: Square push-pull connector.
• ST: Older bayonet-style connector.

Fiber exam cautions:

• Match the optical standard, fiber, connector, and each transmitter to the opposite receiver's wavelength. Bidirectional single-fiber optics can require complementary wavelengths rather than identical modules.
• Keep connectors clean.
• Observe bend radius.
• Do not look into fiber ends.

Fire Ratings

Cable jacket ratings matter because cables can spread smoke or flame through a building.

Common ratings:

• Plenum-rated cable: Listed for applicable air-handling spaces with flame-spread and smoke-performance requirements; this does not make its smoke harmless.
• Riser-rated cable: Used for vertical runs between floors.
• General-purpose cable: Do not substitute it where a plenum or riser listing is required. Jacket chemistry alone does not establish a cable's listing.

Exam clue:

• If the question mentions air-handling space, HVAC return, drop ceiling used for airflow, or plenum, choose plenum-rated cable.

Module 2 Must Know

• Star topology is common for modern Ethernet LANs.
• Bus and coax are older Ethernet concepts but still exam-relevant.
• UTP is common for LAN drops.
• Fiber is best for long distance and EMI-heavy environments.
• Plenum/riser ratings are safety requirements, not performance ratings.
• Cable category affects supported speed and distance.

Module 3: Ethernet Basics

Big Picture

Ethernet defines how devices communicate on wired LANs. Modern Ethernet uses switches, MAC addressing, frames, and structured cabling. Understanding Ethernet means understanding frames, termination, switching, and how devices connect.

What Ethernet Is

Ethernet is a family of LAN technologies defined by IEEE 802.3. It includes physical media standards and frame behavior.

Core points:

• Ethernet uses frames at Layer 2.
• Ethernet uses MAC addresses for local delivery.
• Modern Ethernet usually uses switches.
• Ethernet standards define speed, media, connector expectations, and distance.

Ethernet Frames

Important frame components:

• Preamble and start frame delimiter: Synchronization and frame start.
• Destination MAC address: Receiver.
• Source MAC address: Sender.
• Type/length: Payload type or size information.
• Payload: Often an IP packet.
• FCS: Error detection.

An ordinary untagged Ethernet MAC frame is 64-1518 bytes from destination address through FCS, excluding the 8-byte preamble/start delimiter and interpacket gap. A single 802.1Q tag adds 4 bytes to the usual maximum. The common IP MTU is 1500 bytes, not the complete frame size. Jumbo-frame MTU and frame-size terminology vary by platform, so verify compatible limits throughout the path.

Terminating Twisted Pair

Twisted pair cables must be terminated correctly so each wire lands on the correct pin.

Standards:

• T568A
• T568B

Straight-through cable:

• Same standard on both ends.
• Used for typical endpoint-to-switch connections.

Crossover cable:

• T568A on one end and T568B on the other makes the familiar two-pair 10/100 Ethernet crossover. A full four-pair crossover has additional pair swaps; do not generalize the two-pair diagram to every PHY.
• Historically used for like-device connections, such as switch-to-switch or PC-to-PC.
• Less necessary today because many ports support Auto-MDIX.

Important installation habits:

• Keep pairs twisted as close as practical to the termination.
• Avoid excessive untwisting.
• Do not exceed bend radius.
• Use the right connector and cable category.
• Test the cable after termination.

Hubs vs Switches

Hub

A hub is a Layer 1 device. It repeats incoming bits out all other ports.

Consequences:

• All ports share bandwidth.
• All devices are in one collision domain.
• Half-duplex behavior is common.
• Less secure and inefficient.
• Rare in modern networks.

Switch

A switch is a Layer 2 device. It learns source MAC addresses and forwards frames intelligently.

Consequences:

• Each switch port is its own collision domain.
• Full duplex is common.
• Better performance than hubs.
• Switches forward unknown unicast and broadcast traffic appropriately.
• MAC address tables map MAC addresses to switch ports.

Exam contrast:

• Hub repeats.
• Switch forwards based on MAC address table.
• Router forwards based on IP routes.

Connecting Switches

Switches can be connected to extend the network.

Important concepts:

• Uplink ports were historically used to connect switches.
• Crossover cables were historically needed for like devices.
• Auto-MDIX lets ports automatically adjust transmit/receive pairs.
• Trunks carry multiple VLANs between switches.
• Prevent Layer 2 forwarding loops with a verified spanning-tree or compatible link-aggregation design.

If connecting switches causes unstable network behavior, suspect loops, spanning tree issues, wrong cable, disabled port, speed/duplex mismatch, or VLAN/trunk configuration problems.

Module 3 Must Know

• Ethernet is Layer 1/2 technology, but Ethernet frames are Layer 2.
• Standard Ethernet MTU is 1500 bytes.
• T568A and T568B define pinouts.
• Hubs are Layer 1 repeaters.
• Switches are Layer 2 forwarding devices.
• Switches reduce collisions and improve performance.
• Auto-MDIX reduces the need for crossover cables.

Module 4: Ethernet Standards

Big Picture

Ethernet standards describe speed, signaling, media type, and distance. For the exam, you must decode names like 100Base-TX, 1000Base-SX, and 10GBase-LR.

Reading Ethernet Names

Examples:

• 100Base-TX: 100 Mbps baseband Ethernet over twisted pair.
• 1000Base-T: 1 Gbps Ethernet over twisted pair.
• 1000Base-SX: 1 Gbps Ethernet over short-wavelength multimode fiber.
• 1000Base-LX: 1 Gbps Ethernet over long-wavelength fiber.
• 10GBase-SR: 10 Gbps short-range fiber.
• 10GBase-LR: 10 Gbps long-range fiber.

General decoding:

• Number: Speed.
• Base: Baseband signaling.
• T: Twisted pair copper.
• SX/SR: Short range, usually multimode fiber.
• LX/LR: Long range, often single-mode fiber.

100BaseT

100Base-T is Fast Ethernet.

Know:

• 100 Mbps.
• Common twisted pair version: 100Base-TX.
• Usually uses two pairs.
• Maximum copper segment commonly 100 meters.

Gigabit Ethernet

Common forms:

• 1000Base-T: 1 Gbps over twisted pair, commonly Cat 5e or better, up to 100 meters.
• 1000Base-SX: 1 Gbps over multimode fiber, shorter distances.
• 1000Base-LX: 1 Gbps over longer wavelength fiber, longer distances.

1000Base-T uses all four pairs in the cable.

10-Gigabit Ethernet

Common forms:

• 10GBase-T: 10 Gbps over twisted pair, usually Cat 6a for 100 meters.
• 10GBase-SR: 10 Gbps over short-range multimode fiber.
• 10GBase-LR: 10 Gbps over long-range single-mode fiber.
• 10GBase-ER: Extended reach single-mode fiber.

Exam idea:

• For short rack/data center fiber links, SR is common.
• For longer building/campus links, LR or ER may be appropriate.
• For copper 10G to 100 meters, Cat 6a is the safe answer.

Transceivers

Transceivers convert between the network device and the physical medium.

Common types:

• GBIC: Older, larger modular transceiver.
• SFP: Small form-factor pluggable, commonly 1 Gbps.
• SFP+: Commonly 10 Gbps.
• QSFP/QSFP+: Higher density and higher speed options.

Important matching rules:

• Match speed.
• Match fiber type.
• Match transmit wavelengths to the remote receive specifications, including complementary BiDi pairs where required.
• Match connector.
• Match distance requirement.
• Check device compatibility.

Conventional QSFP/QSFP+ (quad small form-factor pluggable) uses four electrical lanes, compared with the single lane of SFP/SFP+. Four lanes do not imply four fiber strands: optical modules may use parallel fibers or multiplex wavelengths over a duplex pair. Check the module standard and host support. Cisco QSFP examples.

Duplex and Ethernet Connectivity

Half duplex:

• Devices cannot send and receive at the same time.
• Collisions are possible.
• Associated with hubs and old Ethernet designs.

Full duplex:

• Devices can send and receive simultaneously.
• No collisions on the link.
• Standard for modern switch connections.

Speed/duplex mismatch can cause poor performance, errors, late collisions, and intermittent connectivity.

Connecting Ethernet Scenarios

When troubleshooting Ethernet standards and connectivity, work from physical to logical:

1. Link light present?
2. Correct cable type and category?
3. Correct port and transceiver?
4. Within distance limit?
5. Matching speed and duplex?
6. VLAN/trunk/access settings correct?
7. Interface enabled?
8. Error counters increasing?

Common symptoms:

• No link: bad cable, wrong transceiver, disabled port, power issue, physical damage.
• Slow/intermittent: duplex mismatch, bad cable, excessive distance, EMI, failing NIC.
• One VLAN cannot communicate: trunk/access/VLAN configuration issue.
• Fiber link down: wrong fiber type, wrong polarity, dirty connector, incompatible optics.

Module 4 Must Know

• Decode Ethernet standard names.
• 1000Base-T is 1 Gbps copper using four pairs.
• 10GBase-T often requires Cat 6a for full 100-meter support.
• SR/SX imply shorter fiber reach; LR/LX imply longer reach.
• Transceivers must match speed, media, connector, and distance.
• Full duplex eliminates collisions on switched links.

Module 5: Installing a Physical Network

Big Picture

Structured cabling is the organized physical system that connects endpoints to network equipment. It includes work areas, wall jacks, horizontal cabling, patch panels, equipment rooms, racks, switches, and testing.

Structured Cabling

Structured cabling creates a predictable, maintainable physical network.

Common components:

• Work area: User device location.
• Wall outlet/jack: Endpoint connection point.
• Horizontal cabling: Permanent cable run from work area to telecommunications room.
• Patch panel: Termination point for horizontal cables.
• Patch cable: Short cable from patch panel to switch, or device to wall jack.
• Equipment room or telecommunications room: Network equipment location.
• Rack/cabinet: Physical mounting structure.

Why it matters:

• Easier troubleshooting.
• Cleaner moves/adds/changes.
• Reduced wear on permanent cable runs.
• Better labeling and documentation.

Terminating Structured Cabling

Permanent cable is often punched down to patch panels and keystone jacks rather than crimped directly like a patch cord.

Tools and parts:

• Punchdown tool.
• 110 block or patch panel.
• Keystone jack.
• Patch panel.
• Cable stripper.
• Cable tester/certifier.

Best practices:

• Label both ends.
• Maintain pair twists.
• Avoid kinks and tight bends.
• Keep copper away from EMI sources when possible.
• Use cable management.
• Test every run.

Equipment Room

The equipment room or telecom room houses switches, routers, patch panels, racks, UPS devices, and sometimes servers.

Good equipment room design includes:

• Proper rack mounting.
• Patch cable management.
• Adequate cooling.
• Clean power and UPS.
• Labeling.
• Physical security.
• Grounding/bonding where required.
• Space for growth.

The main distribution frame (MDF) is the building's primary distribution point, commonly connecting the service entrance and backbone. An intermediate distribution frame (IDF) serves a floor or local area and connects back to the MDF.

Device hardening includes administratively disabling unused switch access ports and replacing known vendor-default management passwords with unique strong managed credentials. A management VLAN or encrypted session does not remove the risk of an active unused port or a known password. These controls are listed under N10-009 objective 4.3.

Distribution Panels and Blocks

Alternative distribution hardware may include:

• 66 blocks: Older telephone-style punchdown blocks.
• 110 blocks: Common data/voice punchdown blocks.
• Patch panels: Common Ethernet cabling termination points.
• Fiber distribution panels: Organize and protect fiber terminations.

Exam clue:

• Patch panels make moves and changes easier because switch ports connect to patch panel ports with short patch cables.

Testing Cable

Cable testing verifies that a run works and meets requirements.

Common tools:

• Basic cable tester: Verifies continuity and wire map.
• Wire map tester: Detects faults such as opens, shorts, and reversals; split-pair detection requires a tester that supports that measurement, not just continuity LEDs.
• Cable certifier: Validates cable against a performance standard/category.
• TDR: Time-domain reflectometer for copper distance/fault location.
• OTDR: Optical time-domain reflectometer for fiber.
• Toner and probe: Traces cable paths.
• Loopback plug: Tests ports.
• Multimeter: Electrical checks, not a full data cable certifier.

Common cable faults:

• Open: Broken conductor or incomplete termination.
• Short: Conductors touch.
• Reversed pair: Pair polarity reversed.
• Crossed pair: Pins mapped to wrong pair positions.
• Split pair: Continuity may pass, but pair twist is wrong, causing crosstalk.
• Excessive attenuation: Signal loss over distance or poor cable.
• Crosstalk: Interference between pairs.

Troubleshooting Structured Cabling

Use a structured process:

1. Identify the symptom.
2. Check link lights.
3. Check the obvious physical items first.
4. Try a known-good patch cable.
5. Try a known-good port.
6. Test the permanent cable run.
7. Check termination and pinout.
8. Replace suspect cable if repair is not worth the time.

Common quick wins:

• Reseat connectors.
• Replace a patch cable.
• Move to a known-good switch port.
• Confirm the correct jack and patch panel port.
• Confirm speed/duplex and VLAN.

Toner and Probe

A toner and probe helps trace an unlabeled cable. The toner sends a signal onto the cable, and the probe detects it at the other end or along the path.

Use cases:

• Finding which cable goes to a wall jack.
• Tracing unlabeled cables.
• Identifying cable paths in a bundle.

Limitations:

• It identifies/traces cable; it does not certify high-speed performance.
• Use a cable tester or certifier for wiring and category compliance.

Wired Connection Scenarios

Common physical network scenarios:

• No link light: Check cable, port, NIC, switch, power, transceiver, and termination.
• Link light but no communication: Check IP configuration, VLAN, gateway, switch port state, and duplex/speed.
• Intermittent link: Suspect damaged cable, marginal termination, EMI, distance, bad port, or loose connector.
• Poor performance: Suspect duplex mismatch, cable category, excessive errors, congestion, or bad hardware.
• Fiber link failure: Check polarity, connector cleanliness, transceiver compatibility, and fiber type.

Module 5 Must Know

• Structured cabling separates permanent cable from patching.
• Patch panels centralize terminations.
• 110 blocks are common punchdown hardware.
• Cable certifiers verify category performance.
• TDR is for copper fault distance; OTDR is for fiber.
• Toner and probe traces cables but does not certify them.
• Opens, shorts, split pairs, and bad terminations are common physical faults.

N10-009 Modern Network Foundations

N10-009 adds cloud networking and software-defined designs to the physical and layered fundamentals. These technologies still depend on familiar forwarding concepts: an underlay carries packets, an overlay creates logical reachability, and a control plane decides policy.

Cloud And Virtual Network Foundations

Network functions virtualization (NFV) implements functions such as routing, firewalling, load balancing, and intrusion prevention as software workloads instead of requiring a dedicated hardware appliance for each function.

NFV design implications:

• Functions can run on general-purpose virtualization hosts.
• Capacity can scale by adding software instances.
• Placement and recovery can be automated.
• Physical NIC, CPU, memory, and underlay capacity still constrain performance.
• NFV describes virtualized network functions; it does not by itself define how the entire network control plane is programmed.

A virtual private cloud (VPC) is a logically isolated cloud network. A VPC commonly contains:

• Private address ranges and subnets.
• Route tables.
• Internet, NAT, VPN, or private-circuit gateways.
• Workload security groups and subnet-level security lists.
• Connections to other VPCs or on-premises networks.

Cloud deployment models describe where and for whom the environment operates:

• Public cloud: Provider infrastructure shared through tenant isolation.
• Private cloud: Cloud-style infrastructure dedicated to one organization.
• Hybrid cloud: Integrated private and public environments.

Cloud service models describe the customer's management boundary:

• IaaS: The customer manages guest operating systems, applications, and much of the virtual network.
• PaaS: The customer deploys applications while the provider manages more of the runtime and platform.
• SaaS: The provider operates the complete application and supporting platform.

Scalability is the ability to increase capacity. Elasticity is the ability to add and remove capacity dynamically as demand changes. Multitenancy allows several customers to share provider infrastructure while remaining logically isolated.

Content delivery networks (CDNs) place cacheable content at geographically distributed edge locations. A CDN can reduce latency and origin load, but it does not replace authoritative DNS, application authorization, or private WAN connectivity.

Software-Defined Networks And WANs

Software-defined networking (SDN) separates or centralizes control decisions so policy can program forwarding behavior through controllers and APIs. The forwarding devices still move traffic in the data plane.

Software-defined WAN (SD-WAN) applies these ideas to branch and WAN connectivity. Common SD-WAN characteristics include:

• Central policy management.
• Application-aware path selection.
• Use of different underlays such as broadband, MPLS, and cellular.
• Transport-agnostic overlays.
• Zero-touch provisioning for edge devices.

Do not treat SDN and SD-WAN as synonyms. SDN is the broader programmable-network concept; SD-WAN focuses on WAN edge, transport selection, and branch policy.

VXLAN creates a Layer 2 overlay across a Layer 3 IP underlay. It encapsulates Ethernet frames in UDP and uses a 24-bit VXLAN network identifier (VNI), allowing far more logical segments than the traditional 12-bit VLAN identifier space. Common use cases include tenant isolation, leaf-spine fabrics, and data-center interconnect.

SASE combines WAN connectivity with cloud-delivered security capabilities such as secure web gateway, cloud access security broker, firewall as a service, and zero-trust network access. Security Service Edge (SSE) is the security-services portion of that model and does not include the SD-WAN connectivity component.

Quick distinctions:

• NFV: Network functions implemented as software workloads.
• SDN: Programmable and centralized network control.
• SD-WAN: Policy-driven use of multiple WAN transports.
• VXLAN: Layer 2 overlay carried across a Layer 3 underlay.
• SASE: WAN plus cloud-delivered security.
• SSE: Cloud-delivered security without the WAN component.

September 2026 Worked Examples

Optical Power And Short Rack Links

For short rack connections, a supported direct-attach copper (DAC) cable is a twinax assembly with integrated pluggable ends. An active optical cable looks similar at its ends but carries light. A matching connector shape does not establish protocol, speed, host support, or distance compatibility.

Use dBm for absolute optical power and dB for gain or loss. Example values here are synthetic, not a specification for a particular optic:

Transmit power                 -5 dBm
Path loss                       7 dB
Expected receive power        -12 dBm  (-5 - 7)
Receiver sensitivity          -18 dBm
Headroom above sensitivity      6 dB
Required design reserve         3 dB
Remaining spare margin          3 dB

Also check the maximum receive level. A reading of -0.5 dBm exceeds a -3 dBm maximum because it is stronger, not weaker. Long-reach optics on a short path may require approved attenuation. Never increase power blindly or look into a fiber end. The vendor's receiver range and compatibility requirements govern acceptance. Cisco optical specifications.

A referenced light source and power meter measure end-to-end insertion loss. An OTDR helps localize events by distance; an inspection probe checks connector faces. These measurements answer different questions. Preserve wavelength, reference method, endpoint labels, and results. A power budget does not certify installation quality by itself. Fluke optical testing.

Permanent Links And Channel Limits

A 92 m fixed run plus 5 m of patch cords totals only 97 m but fails a conventional 90 m permanent-link requirement. An 87 m fixed run plus 10 m of cords totals 97 m and meets both length limits. Performance certification still matters: continuity does not prove category performance, and the wrong test limit can mask a fixed-run defect. Retain per-run results tied to both labels. Fluke permanent-link versus channel testing.

Power Runtime And Installation Evidence

A UPS must satisfy load capacity and battery runtime separately. Check both watt and VA ratings, voltage, supported receptacles, battery condition, growth allowance, and the runtime curve at the expected load. Include switch overhead and PoE endpoints. A larger VA number does not necessarily mean longer runtime.

For a synthetic 450 W load and six-minute target, a compatible 700 W UPS rated for eight minutes at 450 W meets those two requirements; a 900 W model providing four minutes does not. Validate the required bridge to generator operation through an approved test. Qualified facilities staff handle circuit capacity, grounding, humidity, cooling, and fire-suppression design. A PDU distributes power but supplies no battery energy. Schneider sizing and runtime.

The measured load must fit within both the UPS watt limit and its VA limit; passing only one is insufficient. A runtime figure applies to its documented load, not automatically to a higher one. Schneider Electric on watt and VA limits.

Collapsed Core And Traffic Flows

A collapsed-core campus combines distribution policy/aggregation and core backbone duties in one tier. Redundant devices may share that tier; two devices do not create two architectural layers. A three-tier campus separates access, distribution, and core. A leaf-spine fabric connects leaves through spines for predictable east-west paths. North-south traffic crosses between an environment and external users or networks; east-west traffic moves among internal workloads. Cisco campus designs.

Private Address Boundaries

RFC 1918 reserves 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 for private use. The middle range ends at 172.31.255.255, not 172.255.255.255. For example, 172.28.9.7 is inside; 172.32.9.7 is outside. Outside RFC 1918 does not automatically mean usable public unicast: other special-purpose ranges exist. RFC 1918, section 3.

Anycast Service Selection

An anycast service presents the same service IP at multiple locations. Routing chooses one instance for traffic; it does not copy each packet to all locations. A nearby geographic site may lose to another site's routing policy. Changing paths can affect stateful sessions, so anycast is not automatically transparent application failover. RFC 4786.

Voice And Data On One Access Port

A supported phone-facing access port can combine an untagged data VLAN and a tagged voice VLAN. With data VLAN 40 and voice VLAN 140, the attached PC's untagged frames enter VLAN 40 and the phone's tagged voice enters VLAN 140. Both VLANs need the appropriate upstream paths and services. This does not mean every user port should become an unrestricted trunk, and voice VLAN membership is not proof of device identity. Cisco voice VLAN behavior.

Authoritative Sources

Reviewed 2026-09-08. Worked values and practice scenarios are original; source documents establish the underlying behavior, not exam answers.

• CompTIA N10-009 objectives, version 4.0: scope and objective mapping.
• Cisco SFP+ data sheet: DAC and optical limits.
• Fluke optical reference measurements: insertion-loss testing.
• Fluke cabling test limits: permanent links and channels.
• Schneider UPS sizing: capacity versus runtime.
• Cisco campus design: collapsed core and hierarchy.
• RFC 1918 and RFC 4786: private addressing and anycast.
• Cisco voice VLANs: tagged voice with untagged data.
• RFC 9114: HTTP/3 transport distinction.
• RFC 9542: Ethernet address administration and organizational identifiers.

Exam Strategy

If A Question Mentions No Link

Think Layer 1 first:

• Cable unplugged or damaged.
• Wrong cable or connector.
• Bad transceiver.
• Disabled port.
• Excessive distance.
• Bad NIC or switch port.
• Fiber polarity or dirty connector.

If A Question Mentions One Host Cannot Communicate

Check:

• Link light.
• IP address, subnet mask, gateway.
• VLAN assignment.
• Bad patch cable.
• Switch port configuration.
• MAC address table if switching issue is suspected.

If A Question Mentions Slow Or Intermittent Ethernet

Check:

• Speed/duplex mismatch.
• Bad cable or bad termination.
• EMI.
• Excessive cable length.
• Interface errors.
• Oversubscribed link.

If A Question Mentions Air Handling Space

Choose plenum-rated cable.

If A Question Mentions Long Distance Or EMI

Choose fiber optic cabling.

If A Question Mentions Tracing An Unknown Cable

Choose toner and probe.

If A Question Mentions Certifying Cat 6/Cat 6a

Choose cable certifier, not just a basic continuity tester.

Final Review Checklist

• I can list all OSI layers in order.
• I can identify the layer for MAC, IP, TCP/UDP, and applications.
• I can explain encapsulation and decapsulation.
• I can identify Ethernet frame fields and their purpose.
• I can compare MAC and IP addressing.
• I can explain broadcast vs unicast.
• I can compare bus, ring, star, mesh, and hybrid topologies.
• I can choose coax, twisted pair, or fiber for a scenario.
• I can choose plenum or riser cable when given a building scenario.
• I can explain T568A, T568B, straight-through, and crossover.
• I can compare hubs and switches.
• I can decode Ethernet standard names.
• I can choose SFP/SFP+/QSFP and fiber standards for scenarios.
• I can identify structured cabling components.
• I can choose the right cable testing/tracing tool.
• I can troubleshoot common wired connectivity symptoms.