Question 570
An engineer chooses an IPv6 route based on the printed address alone without comparing prefix length. Which next action best resolves this observed routing or switching failure?
Explanation
Correct Answer
This option addresses the stated case rather than another networking issue. Principle: IPv6 route selection follows prefix matching and route eligibility, not textual address order. Remedy: Apply longest-prefix-match route lookup to the IPv6 destination. Proof: A destination lookup chooses the intended most specific valid route.
Incorrect Answers
Tunneling carries one protocol over an underlay that may not route that payload natively describes a neighboring protocol concern. In this case the controlling fact is iPv6 route selection follows prefix matching and route eligibility, not textual address order. A correct remediation would apply longest-prefix-match route lookup to the IPv6 destination and demonstrate: A destination lookup chooses the intended most specific valid route.
The proposed principle concerns another network fault: A tunnel can carry inner packet types over an underlay forwarding only the outer header. Here, iPv6 route selection follows prefix matching and route eligibility, not textual address order. The most direct correction is to apply longest-prefix-match route lookup to the IPv6 destination, confirmed by a destination lookup chooses the intended most specific valid route.
That result would be useful for a different failure, namely: A new Junos edge router can ping IPv4 customers but cannot route IPv6 traffic to the same site. The current case specifically calls for: Apply longest-prefix-match route lookup to the IPv6 destination. The required observed result is: A destination lookup chooses the intended most specific valid route.