How to Validate Asymmetrical Routing Between Branch and Hub?
Clients have reported slowness between a branch and a hub location. The senior engineer suspects asymmetrical routing is causing the issue. Which of the following should the engineer run on both the source and the destination network devices to validate this theory?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
This question tests knowledge of network diagnostic commands, specifically how traceroute reveals the bidirectional path to detect asymmetry; the trap is choosing generic tools like ping that only verify connectivity.
When clients report slowness due to suspected asymmetrical routing, running traceroute on both source and destination network devices is the recommended diagnostic method. Community consensus confirms traceroute as the correct answer for identifying differing packet paths.
The most common wrong answer is ping, because it tests reachability and latency but does not show the route path, so it cannot reveal whether packets take different paths in each direction.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Traceroute displays the hop-by-hop path packets take from source to destination. Running it on both the source and destination devices allows the engineer to compare the forward and reverse paths. If the routes differ, it confirms asymmetrical routing. This directly aligns with the need to validate the theory.Why the Other Options Are Wrong
Ping only tests reachability and round-trip time; it does not reveal the path taken, so it cannot detect asymmetry. The route command shows the local routing table but does not show the actual path packets take across the network. Nslookup is used for DNS queries and is unrelated to routing path analysis.Community Comment Notes
Comments emphasize that traceroute is the correct diagnostic because it tracks the path taken by packets from one point to another, and running it on both ends allows comparison. One comment specifically explains that ping only tests connectivity, not the path, reinforcing why traceroute is superior for this scenario.Official Reference
Exam Strategy
For questions about diagnosing routing asymmetry, remember that traceroute (or tracert on Windows) is the go-to command because it reveals the actual path. Rule out tools that only test connectivity (ping) or display local tables (route) since they do not compare bidirectional paths.