Study guide
Routing Basics and Longest Prefix Match
CompTIA Network+ N10-009
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
Current Exam Facts and Applied Networking Judgment Official Domain Weights and an 8-12 Week Study Plan How to Use Labs, Practice, and PBQ Workflow Missed-Question Notebook and Final Readiness Metrics
2 Domain 1: Networking Concepts (23%)
OSI and TCP/IP Models with Device and Protocol Mapping Networking Appliances and Where They Operate Ports and Protocol Decision Table Traffic Types and Encapsulation Flow
3 Domain 1: Media, Connectors, Transceivers, and Network Architectures
Copper, Fiber, Coax, and DAC Media Connector and Transceiver Selection Network Topologies and Design Patterns Cloud and Virtual Networking Concepts
4 Domain 1: IP Addressing and Subnetting Mastery
IPv4 Classes, Private/Public, APIPA, and Loopback CIDR, VLSM, and Subnet Math IPv6 Address Types and Notation Routing Basics and Longest Prefix Match
5 Domain 2: Network Implementation - Routing
Static vs Dynamic Routing and Route Selection OSPF, EIGRP, and BGP Basics at Network+ Depth NAT/PAT, VIP/FHRP, and Subinterfaces Routing PBQs and Troubleshooting Route Table Clues
6 Domain 2: Network Implementation - Switching
VLANs, Access Ports, Trunks, and Native VLAN STP/RSTP Loop Prevention and Bridge Roles Port Aggregation/LACP, MTU, Jumbo Frames, and Interface Settings Switch Implementation PBQs and Common Misconfigurations
7 Domain 2: Network Implementation - Wireless and Physical Implementation
Wi-Fi Standards, Bands, and Channels SSID Security, Guest Networks, and Authentication Antennas, Coverage, Roaming, Interference, and Site Surveys Physical Installation Implications
8 Domain 2: Network Implementation - Services Implementation
DNS Record Types and Troubleshooting Cues DHCP, DHCPv6, SLAAC, Scopes, Leases, and Relay NTP, PTP, NTS, and Time-Sensitive Networking Service Implementation PBQs: DNS, DHCP, VLANs, and Firewall Direction
9 Domain 3 Part A: Network Operations Documentation and Governance
Physical, Logical, Rack, Cable, Wireless Diagrams, and IPAM Asset Inventory, Baselines, SLAs, SOPs, and Runbooks Change Management and Request Tracking Lifecycle, EOL, EOS, Decommissioning, and Configuration Management
10 Domain 3 Part B: Monitoring, Remote Access, and Resilience
SNMP, Flow, Syslog, Packet Capture, Log Aggregation, APIs, and Port Mirroring Baselines and Performance Metrics Remote Access, Management Paths, and Secure Admin Habits DR and HA Concepts: RPO, RTO, MTTR, MTBF, Sites, Failover, and Testing
11 Domain 4: Logical Security and Secure Access (14%)
Encryption in Transit, Encryption at Rest, PKI, and Certificates IAM, MFA, SSO, Directory Services, and AAA Authorization, Least Privilege, RBAC, Geofencing, and Time-Based Access VPNs and Secure Management Design
12 Domain 4: Segmentation, Risk, and Network Attacks (14%)
Segmentation for Guest, BYOD, IoT, IIoT, SCADA, ICS, and OT Risk, Compliance, Audit, Data Locality, PCI, and GDPR Network Attacks and Scenario Cues Attack-to-Mitigation PBQ Tables
13 Domain 4: Security Controls and Hardening (14%)
Firewalls, IDS, IPS, Security Zones, and Screened Subnets ACLs, Filtering, NAC, Hardening, and Key Management Deception Technologies and Physical Security Zero Trust, SASE, and Trusted or Untrusted Zone Decisions
14 Domain 5: Troubleshooting Methodology and Tools (24%)
Official Troubleshooting Methodology and Evidence Handling Command-Line Tools: ping, traceroute, nslookup, dig, ipconfig, ifconfig, ip, arp, netstat, ss, and route Packet, Protocol, and Wi-Fi Analyzers Choosing the Right Tool by Symptom PBQs
15 Domain 5: Physical, Interface, and Wireless Troubleshooting (24%)
Cable Issues: Type, Attenuation, Crosstalk, Termination, and TX/RX Interface Issues: Errors, Discards, Duplex, Speed, Port Status, and PoE Transceiver, Fiber, and Signal Strength Troubleshooting Wireless Troubleshooting: Interference, Channels, Roaming, RSSI/SNR, Security, and Captive Portals
16 Domain 5: Network Services, Switching, Routing, and Performance Troubleshooting (24%)
DHCP, DNS, NTP, and IP Addressing Issues VLAN, STP, Trunk, Native VLAN, and ACL Issues Routing, Default Gateway, Route Table, and NAT Issues Congestion, Latency, Jitter, Packet Loss, and Application Performance Clues
17 Performance-Based Question Labs
Subnetting and VLSM Design Lab VLAN, Trunk, Router-on-a-Stick, and Firewall Rule Lab Wireless Deployment and Troubleshooting Lab Monitoring, Log Triage, and Route or Service Troubleshooting Lab
18 High-Yield Reference and Final Study Plan
High-Yield Ports and Protocols Table Wi-Fi, Cabling, Connectors, and Transceivers Quick Table Acronyms and Command-Line Tool Quick Table Final 7-Day Review Plan and Readiness Checklist
19 Final Synthesis: Strategy, Remediation, and Readiness
Mixed-Set Decision Strategy for Qualifiers and Close Answers Missed-Question Remediation Notebook by Error Type Exam-Day Time Management and PBQ Order 100-Question Readiness Simulation Blueprint Mapped to N10-009 Weights
Routing Basics and Longest Prefix Match
Key Takeaways Explain This Topic AI
A host sends traffic directly only when the destination shares its local subnet; otherwise it forwards the packet to its default gateway.
Routers select a path using the routing table, then longest prefix match, then administrative distance, then metric as successive tie-breakers.
Longest prefix match means the most specific matching route wins; a /24 beats a /16, and a /32 host route beats both.
The default route 0.0.0.0/0 (or ::/0 in IPv6) is the least specific entry and is used only when no more specific route matches.
Routing failures usually trace to subnet membership errors, an unreachable gateway, a missing return route, or an asymmetric or filtered path.
Last updated: June 2026
What Routing Does
Routing moves packets between IP networks. Before sending, a host compares the destination against its own address and mask. If the destination is in the same subnet , the host delivers it directly on the LAN using Layer 2. If the destination is remote , the host forwards the packet to its default gateway , the router that knows how to reach other networks.
- Concept Meaning Exam clue
- Default gateway Router for off-subnet destinations Host cannot reach other networks
- Routing table Known prefixes and their next hops Route-lookup question
- Static route Manually configured entry Small or specific path
- Dynamic route Learned via a protocol OSPF/BGP/RIP/EIGRP context
- Metric Preference within one protocol Lower cost is better
- Administrative distance Trust ranking across route sources Static vs dynamic comparison
- Default route 0.0.0.0/0 or ::/0 Route of last resort
- Local or Remote Decision
The host ANDs its address and the destination against its mask; matching network portions mean local delivery.
- Host Destination Decision
- 192.168.10.25/24 192.168.10.80 Local
- 192.168.10.25/24 192.168.11.80 Send to gateway
- 10.1.5.130/25 10.1.5.20 Send to gateway (different /25 subnets)
- 2001:db8:10::25/64 2001:db8:10::80 Local (same /64)
- Longest Prefix Match
When several routes could carry a packet, the router picks the most specific one, meaning the route with the longest prefix length . A /24 is more specific than a /16, and a /32 host route is the most specific of all.
- Route in table Matches 10.1.2.55? Specificity
- 0.0.0.0/0 Yes Least specific
- 10.0.0.0/8 Yes Broad
- 10.1.0.0/16 Yes More specific
- 10.1.2.0/24 Yes Most specific here
- 10.1.3.0/24 No Different subnet
With every route present, traffic to 10.1.2.55 takes 10.1.2.0/24 because it is the longest matching prefix. The default route is used only when nothing more specific matches. Administrative distance breaks ties between equally specific routes from different sources (a static route, AD 1, beats an OSPF route, AD 110), and metric breaks ties within a single protocol.
Routing Troubleshooting
- Symptom Check
- Reaches local subnet, not the internet Default gateway, NAT, upstream route
- One way works, replies fail Missing return route, firewall state, asymmetry
- Traffic takes an unexpected path A more specific route, metric, or policy route
- VPN tunnel up but app fails Local/remote route, overlapping CIDR, firewall
- Cloud peering exists, no traffic Route tables and security filters on both sides
- PBQ-Style Thinking
Scenario: a router holds routes for 10.0.0.0/8 via Router A, 10.2.0.0/16 via Router B, and 10.2.5.0/24 via Router C. A packet to 10.2.5.99 goes to Router C , 10.2.9.99 goes to Router B , and 10.9.9.9 goes to Router A . Walk each destination against the table and pick the longest match; this is the single most common routing PBQ pattern.
Scenario: a branch subnet 192.168.40.0/24 can initiate traffic to a data center, but servers cannot reply. The branch edge has a route, but the data center core lacks a return route to 192.168.40.0/24. Traffic flows out and dies on the way back. Add or advertise the return route and verify firewalls permit the reply.
Routing Protocol Context
N10-009 wants conceptual recognition, not vendor configuration.
- Protocol High-level idea
- OSPF Interior link-state IGP using cost
- BGP Exterior protocol between autonomous systems
- RIP Older distance-vector, 15-hop limit
- EIGRP Advanced distance-vector, Cisco-associated
- Static Manual entries, predictable, less scalable
The selection order to recite is: longest prefix match first , then administrative distance to compare route sources, then metric within a protocol. Master that order and most routing-table questions resolve themselves.
Administrative Distance Versus Metric
Candidates often blur these two tie-breakers, but they operate at different stages. Administrative distance (AD) ranks the trustworthiness of route sources and only matters when two routes to the same prefix come from different protocols. A directly connected route has AD 0, a static route AD 1, EIGRP 90, OSPF 110, and RIP 120, so a static route to a destination will be installed over an OSPF route to the same destination even though OSPF may know a technically shorter path. Metric only breaks ties inside one protocol, choosing the lower-cost path among routes the same protocol learned.
The exam may show a static and a dynamic route competing; the answer hinges on AD, not metric. It may instead show two OSPF paths with different costs; there the lower metric wins.
Default Gateway Versus Default Route
These sound identical but live on different devices. A default gateway is configured on an end host and names the single router the host uses for any off-subnet destination. A default route (0.0.0.0/0 or ::/0) lives in a router's table and tells that router where to send packets it has no specific route for. A host with a wrong default gateway cannot reach remote networks even if every router is perfectly configured; a router missing a default route may drop traffic to unknown destinations even though hosts are configured correctly. Read each scenario to determine which device owns the misconfiguration.
Return Paths and Asymmetry
The hardest routing PBQs are reachability problems where traffic flows one direction only. IP routing is hop-by-hop and independent in each direction, so a packet can reach a destination while the reply has no valid route home. The branch-to-data-center example earlier is the canonical case: outbound works because the path is fully routed, but the reply dies because the far side never learned a route back to the source subnet.
Always verify both a forward and a return route exist, and remember that stateful firewalls add a second requirement, the reply must traverse the same firewall that saw the request, or the connection state will not match and the firewall will silently drop it.