Inspect
Review the problem, diagram, and evidence.
Two routes matched the destination. The router chose the more specific prefix, not the visually simpler route.
Inspect, commit, prove, fix, and sign off.
Follow the investigation process used in the field β in five guided steps.
Review the problem, diagram, and evidence.
Choose your hypothesis.
Run calculations and test your idea.
Select and validate a safe correction.
See the full debrief and key takeaways.
A router has two relevant entries: 10.0.0.0/8 via Interface A and 10.1.2.0/24 via Interface B. A packet is destined for 10.1.2.55. A technician expects the /8 route because it appears first in the table. The router sends the packet through Interface B. Diagnose the route-selection rule and identify which entry wins.
Find the root cause, confirm the fix, and see how this connects to the exam.
The expected route was based on table order and breadth rather than specificity.
The shorter prefix would win.
Use longest-prefix matching among all routes that contain the destination.
When multiple IP routes match a destination, a router selects the longest matching prefix. For destination 10.1.2.55, both 10.0.0.0/8 and 10.1.2.0/24 match, but /24 is more specific and is selected.
Route lookup uses the most specific matching network prefix: the longest prefix length among matching entries.
Choose the matching route with the greatest prefix length, meaning the most specific network.
The /24 route, assuming no even more-specific match exists.
Each case is designed to build the judgment, analysis, and confidence you need for engineering exams β and beyond.
Basic subject familiarity helps, but every case is designed to teach through the investigation itself.
Most cases are designed for a focused 5β10 minute investigation.
Each case is mapped to a verified exam, subject, topic, and misconception before publication.
The sealed debrief unlocks with the root cause, corrected reasoning, fix, and takeaway.