ExamFinch.com My Study

Study guide

Static vs Dynamic Routing and Route Selection

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

Static vs Dynamic Routing and Route Selection

Key Takeaways Explain This Topic AI

Network+ N10-009 routing questions test how a router chooses a path, not vendor command memorization.

Static routes are manually configured and predictable; dynamic protocols learn and reconverge after topology changes.

Route selection is longest prefix match first, then administrative distance, then metric when ties remain.

A default route (0.0.0.0/0 or ::/0) is used only when no more specific route matches the destination.

N10-009 has five domains: Networking Concepts 23%, Network Implementation 20%, Network Operations 19%, Network Security 14%, Network Troubleshooting 24%.

Last updated: June 2026

How a Router Forwards a Packet

Routing moves packets between IP networks. When a packet arrives, the router compares the destination IP address against every entry in its routing table, selects the single best matching route, and forwards the packet out the chosen interface or to the chosen next hop . If no route matches and no default route exists, the packet is dropped and the router may return an ICMP "destination unreachable" message.

For N10-009 (the only Network+ exam available in 2026, launched June 20, 2024), routing lives primarily in Domain 2, Network Implementation , which is 20% of the exam. The exam is up to 90 questions in 90 minutes, scored 100-900 with a passing score of 720. Current domain weights:

  • Domain Weight
  • Networking Concepts 23%
  • Network Implementation 20%
  • Network Operations 19%
  • Network Security 14%
  • Network Troubleshooting 24%

Note the official N10-009 Domain 1 name is "Networking Concepts" (the older N10-008 called it "Networking Fundamentals"). Expect routing logic to also surface inside Domain 5 troubleshooting scenarios.

Route Sources

Every entry in a routing table came from somewhere, and the source determines how trustworthy and how stable the route is.

Route type How it appears Best use Main risk

Connected (C) An interface has an IP and is up/up Directly attached subnets Vanishes when the interface goes down

Local (L) The exact /32 or /128 of the interface IP Reaching the router itself Rarely changed manually

Static (S) Admin configures destination + next hop Stub networks, backups, control Does not adapt unless tracked

Default (S* / gateway of last resort) Route to 0.0.0.0/0 or ::/0 Send unknown destinations upstream A bad default blackholes traffic

Dynamic (O, D, B...) Learned from OSPF, EIGRP, BGP, RIP Larger or changing topologies Needs neighbor design + monitoring

A connected route is the foundation: a dynamic protocol can only advertise a subnet the router is actually connected to or has been told about. If the interface IP is missing or the interface is down, the connected route disappears and any route depending on it fails too.

Static vs Dynamic Routing

  • Feature Static routing Dynamic routing
  • Configuration effort Manual, one route at a time Protocol setup plus policy/filters
  • Adaptation to failure None unless object-tracked Reconverges automatically
  • Resource overhead Negligible CPU, memory, and protocol traffic
  • Predictability Very high Depends on metrics and protocol state
  • Scale Best for one-exit stub paths Best for many routers/paths
  • First troubleshooting move Verify destination, mask, next hop Check neighbors, ads, metrics, filters

Static routing is not amateur. It is the correct answer for a stub branch with one exit, a management network, or a deliberate backup path. Dynamic routing earns its overhead when there are multiple routers, multiple redundant paths, frequent topology changes, or a requirement for automatic failover.

A floating static route is a static route given an artificially high administrative distance (for example, distance 200) so it sits dormant in the table and is installed only when the preferred dynamic or lower-distance route disappears. This is the classic way to back up a primary WAN with a secondary link without running a routing protocol over the backup.

Route Selection Order (Memorize This)

Routers do not just grab the lowest metric across every candidate. They narrow the field in strict order:

Longest prefix match - the most specific (largest mask) matching destination wins, regardless of source.

Administrative distance (AD) - among routes with identical prefix length, the most trusted source wins. Typical defaults: Connected 0, Static 1, eBGP 20, EIGRP 90, OSPF 110, RIP 120, iBGP 200.

Metric - if the same protocol offers two routes of equal prefix length, the lowest metric (cost) wins.

Worked example - destination 10.10.40.25

Route Source AD Metric Matches?

  • 0.0.0.0/0 via 203.0.113.1 Static default 1 0 Yes
  • 10.10.0.0/16 via 10.1.1.1 OSPF 110 20 Yes
  • 10.10.40.0/24 via 10.2.2.2 Static 1 0 Yes
  • 10.10.40.0/25 via 10.3.3.3 OSPF 110 30 Yes

The winner is 10.10.40.0/25 because /25 is the longest matching prefix for 10.10.40.25. Administrative distance and metric never enter the picture here - the static /24 with AD 1 loses to an OSPF /25 with AD 110 purely on prefix length. This trips up candidates who reach for AD or metric first.

Scenario Method and Common Traps

When a host cannot reach a remote subnet, walk the path methodically rather than guessing:

  • Check What it proves
  • Host IP/mask/default gateway correct Host can hand off-subnet traffic to the router
  • Source router has a route to the destination A forward path exists
  • Next hop is reachable (ping, ARP) The route points to a live neighbor
  • Destination router has a route back A return path exists
  • ACL/firewall permits the flow The failure is not filtering masquerading as routing

Common traps:

Picking the lowest metric across all protocols - longest prefix and AD are evaluated first.

Adding a default route to "fix" one missing internal subnet - the default can hide the real gap and send traffic the wrong way.

Troubleshooting only the forward path - many "routing" failures are missing return routes; replies leave the source but never come back.

Assuming connected routes are configured by hand - they appear automatically when an addressed interface is up.

PBQ practice prompt

Three routers, one route table. Branch users reach the internet but not data-center subnet 10.50.20.0/24. The branch router holds only a default route to the ISP and nothing for the private WAN. Correct move: add a specific static route for 10.50.20.0/24 toward the WAN next hop, then confirm the data-center router has a route back to the branch subnet.