Practice Exams:

CompTIA N10-009: Routing Tables in Plain English

A routing table is easier to understand when every entry is translated into a sentence: traffic for this destination prefix uses this next hop or outgoing interface, and the entry came from this source. The decisive task is to identify which entry matches the destination most specifically. A routing table does not tell the whole story of an end-to-end connection, but it tells a technician what the local forwarding device intends to do next. Reading that intention accurately helps separate wrong-route problems from filtering, address translation and failures further along the path.

CompTIA
On this page
  1. Translate one route into ordinary language
  2. Longest-prefix match comes first
  3. Understand route preference only for equivalent prefixes
  4. Resolve the next hop and verify its reachability
  5. Follow both forward and return paths
  6. Apply a short, repeatable route-tracing checklist

The CompTIA Network+ N10-009 exam covers routing technologies and practical network troubleshooting. For enterprise network engineering, this knowledge becomes essential whenever traffic crosses multiple sites, firewalls, virtual networks or redundant WAN paths. Instead of memorizing a vendor’s command output, start by identifying the destination and what the forwarding device should do with it.

Translate one route into ordinary language

An entry such as 10.20.40.0/24 via 192.0.2.1 indicates a destination network and the next-hop address to which matching traffic will be forwarded, subject to the device’s other forwarding behavior. The /24 is a prefix length: the first 24 bits of the destination must match that entry’s network. In an actual routing table, related fields may include protocol source, metric, preference and interface. Their display varies by platform, but the conceptual questions do not.

A connected network route means the prefix is reachable through an interface of the device; a static route represents a configured forwarding instruction. Routes learned from a protocol reflect information received through that protocol under its policy and selection rules. These sources imply different failure conditions, so identify the origin before changing anything. Deleting a route without understanding how it was learned may simply cause it to reappear or break a neighboring path.

Longest-prefix match comes first

Suppose a router has 10.20.0.0/16 through one gateway and 10.20.40.0/24 through another. A packet for 10.20.40.25 matches both, but the /24 is more specific and is selected for destination-based forwarding. That choice is separate from administrative distance or protocol metric. More-specific routes can therefore divert a small population of hosts even when a broad default or summary route looks healthy.

The default route, commonly 0.0.0.0/0 for IPv4, is the least-specific catch-all match. It does not override a valid specific prefix. When diagnosing a partial outage, start with the exact destination address; a test to a different host within a neighboring subnet can select a different route and falsely reassure the technician. The deeper method for reading a routing table follows the same destination-first approach.

Understand route preference only for equivalent prefixes

After longest-prefix match, a device may have multiple candidate routes to the same prefix. Administrative preference determines which route source is favored under the platform’s rules, while routing-protocol metrics typically compare choices within one protocol. Equal-cost multipath can place multiple next hops into forwarding; that may be intended redundancy rather than a configuration error. Verify actual forwarding state, because protocol databases, routing tables and hardware forwarding tables can differ during convergence or programming failure.

Do not assume a numerically smaller metric from one protocol always wins against a route from another protocol. A technician should know which selection stage a field participates in, and should avoid mixing metrics that were designed for different purposes. If a route disappears during failover, inspect whether its next hop remains reachable, whether the protocol adjacency is healthy and whether route import or filter policy rejected it.

Resolve the next hop and verify its reachability

A route can look correct while its next hop is unreachable. The forwarding device may need another route to reach the next-hop address, or a directly connected interface and neighbor resolution may be failing. Work recursively until the intended egress interface and adjacent device are clear. Check physical and Layer 2 state, ARP or neighbor discovery, and the expected VLAN or tunnel membership rather than treating a configured route as proof of connectivity.

Tunnels introduce underlay dependencies. A route through a virtual tunnel is useful only if the tunnel endpoint itself remains reachable and the tunnel security or encapsulation state is valid. An underlay route change may disrupt a logical network that seems untouched. Capture the expected tunnel endpoint and its physical path in the documentation before troubleshooting a confusing recursive next-hop result.

Follow both forward and return paths

A successful connection requires that a request reach its destination and an appropriate response return. The request may traverse one firewall while its reply chooses another route, creating a stateful inspection failure. NAT can make the observed return destination differ from the original client address. When the forward routing table looks plausible, inspect the destination-side route, filtering policy and translation state rather than changing the source router repeatedly.

Traceroute can provide useful clues but is not conclusive: intermediary devices may filter, rate-limit or source replies in unexpected ways. Combine its observations with routing-table entries and packet evidence. If only one subnet fails, compare the working and failing prefixes and their next hops. Often the difference identifies a more-specific route, security zone or policy boundary that deserves testing.

Apply a short, repeatable route-tracing checklist

Write down the exact source and destination addresses. Find the most specific route at the source gateway, record its source and next hop, then confirm how that next hop is reached. Follow the path to the next relevant forwarding device. At each step, ask whether destination-based routing, policy routing, tunnels, NAT or stateful controls can alter the expected flow. Record which test confirmed each hop instead of treating a diagram as live evidence.

The final incident explanation should name the wrong forwarding decision or missing reachability, not simply state “network issue.” For example, a stale /25 route to a retired site may have diverted one application server subnet while other traffic used the updated WAN. Verify the repaired path and return traffic from the affected client before closing the ticket. A route is understood when a technician can predict its behavior, not merely recite its syntax.

Related Posts

• Your Ultimate Guide to CompTIA Network+ N10-009 Certification

• Laying the Foundation — Why the CompTIA Network+ N10-009 Matters More Than Ever

• Your Complete Guide to the CompTIA Network+ Certification: Prep, Pricing & Pro Tips

• CompTIA 220-1201: Wi-Fi Problems Are Often Radio Problems

• CompTIA 220-1201: IPv4, DHCP, and DNS From the Help Desk Point of View

• CompTIA N10-009: Subnetting for Technicians: Read the Boundary First

• CompTIA N10-009: DNS, DHCP, and NTP: Small Services With Outsized Impact

• CompTIA N10-009: Wi-Fi Troubleshooting Starts With RF, Not Reboots

• CompTIA N10-009: Routing Protocols: Separate Discovery From Decision

• CompTIA N10-009: Network Monitoring: What Baselines Reveal Before an Outage