ExamFinch.com My Study

Study guide

Routing PBQs and Troubleshooting Route Table Clues

Practice this exam

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 PBQs and Troubleshooting Route Table Clues

Key Takeaways Explain This Topic AI

Routing PBQs combine route tables, interface status, gateways, VLANs, NAT, and protocol clues into one repair task.

Read a route table by matching prefix length first, then route source code, then next-hop reachability.

A missing route, wrong next hop, down interface, wrong gateway, NAT fault, or ACL can all produce the same user complaint.

ping, traceroute, ARP/neighbor tables, interface status, and the route table together localize the failure.

Always test the return path and decide whether the failure is routing, switching, translation, or filtering.

Last updated: June 2026

How Routing PBQs Are Built

Performance-based questions (PBQs) present a partial topology - a few routers, a switch, a route table, maybe a NAT or firewall hint - and ask you to restore reachability. The winning approach is always the same disciplined flow: identify the source host, its default gateway, the routed path, the destination's return path, and any policy controls in between. Change the smallest thing that explains all symptoms.

Reading Route-Table Codes

  • Code Meaning
  • C - connected Subnet directly attached and interface up
  • L - local A /32 or /128 for the router's own interface IP
  • S - static Administrator configured the route
  • O - OSPF Learned via OSPF
  • D - EIGRP Learned via EIGRP (D = DUAL)
  • B - BGP Learned via BGP
  • S* - gateway of last resort A default route is present
  • (no match) Packet dropped unless a default route catches it

Exact code letters vary by vendor, but a PBQ gives enough context. Anchor on four facts per line: source code, destination prefix, next hop, and interface state.

The Troubleshooting Flow

Apply this in order; do not skip ahead:

  • Step Question Evidence / tool
  • 1 Is the host configured correctly? IP, mask, default gateway, DNS if name-based
  • 2 Can the host reach its gateway? ping gateway, ARP table, VLAN membership
  • 3 Does the router know the destination? Route table, longest-prefix match
  • 4 Is the next hop reachable? Interface up/up, ARP/neighbor, ping next hop
  • 5 Does the destination know the return path? Remote route table and gateway
  • 6 Is translation involved? NAT/PAT table, inside vs outside interface roles
  • 7 Is policy blocking it? ACL, firewall rule, security group
  • User-report decoder
  • User report Best first clue Likely fix
  • One internal subnet cannot reach another Route table lacks a specific route Add route or advertise the subnet
  • All offsite networks fail from one VLAN Wrong host default gateway Fix the DHCP scope or static gateway
  • Internet fails but private WAN works Default route or NAT/PAT Add default route or repair translation
  • Server gets traffic but replies never arrive Return path missing Add reverse route or fix the server gateway
  • A dynamic route vanished after maintenance Adjacency down Fix interface, protocol settings, or auth
  • Longest-Match Practice
  • Destination: 172.16.8.45
  • Route Next hop
  • 0.0.0.0/0 ISP
  • 172.16.0.0/16 WAN-A
  • 172.16.8.0/24 WAN-B
  • 172.16.8.32/27 WAN-C

Work the math: a /27 covers 32 addresses, so 172.16.8.32/27 spans 172.16.8.32-172.16.8.63. The destination .45 falls inside that block, so WAN-C wins - it is the longest matching prefix. If WAN-C's next hop is down and no alternate is installed for that prefix, the router may drop the packet even though broader /24, /16, and default routes still match. This is why "there is a default route, so it must work" is a flawed assumption: a more specific dead route is still preferred over a healthy broader one.

PBQ Repair Examples

Evidence in the PBQ Interpretation Action

Branch has only a default route; HQ subnet should reach via MPLS Specific private route missing Add a static route or fix the advertisement

OSPF neighbor absent after a password change Authentication mismatch Correct OSPF auth on both ends

VLAN 30 gateway responds but no inter-VLAN routing Missing route or subinterface Add the routed/subinterface gateway

PAT table empty during internet test NAT not matching traffic Fix the NAT ACL or inside/outside roles

Traceroute stops at the firewall Filtering or missing route at that hop Check route table and firewall policy there

Common Traps and the Exam Tactic

  • Trap Better reasoning
  • Blame DNS when ping by IP already fails Layer 3 reachability must work before name resolution matters
  • Fix only the source router Return-path routing breaks replies just as easily
  • Sprinkle broad default routes everywhere Specific internal routes are safer and easier to reason about
  • Ignore interface status A perfect route through a down interface forwards nothing

Read a traceroute timeout as definitive failure Some devices silently forward but block ICMP/traceroute responses

Exam tactic

When a PBQ shows many devices, narrate the flow in your head: source host -> default gateway -> router path -> destination gateway -> destination host -> return. Then change the single smallest setting that accounts for every symptom. If one VLAN works and an adjacent one does not, line up their differences: gateway address, VLAN tag, route entry, and ACL. The differing field is almost always the answer. Resist replacing hardware or rewriting whole configs - PBQs reward a precise edit, and the broader, more dramatic option is usually the distractor.

Finally, sanity-check that your fix does not blackhole other traffic, especially when you add or change a default route.