Question 360
A BGP peer carries IPv4 prefixes but the team assumes IPv6 prefixes are automatically shared. Which post-change observation most strongly confirms the correction?
Explanation
Correct Answer
Correct diagnosis: BGP family negotiation and route policy control IPv6 NLRI exchange. The appropriate action is: Enable and verify the intended IPv6 BGP family and export policy. The follow-up evidence required is: The selected inet6 route appears on the authorized IPv6 peer.
Incorrect Answers
This answer would be more suitable when an IS-IS neighbor appears only at Level 2 even though the design expects a Level 1 core segment, where the corrective action is to compare interface level settings and area configuration. The failure here is different: BGP family negotiation and route policy control IPv6 NLRI exchange. Required validation: The selected inet6 route appears on the authorized IPv6 peer.
A configured IPv6 static route still depends on reachable forwarding next hops describes a neighboring protocol concern. In this case the controlling fact is bGP family negotiation and route policy control IPv6 NLRI exchange. A correct remediation would enable and verify the intended IPv6 BGP family and export policy and demonstrate: The selected inet6 route appears on the authorized IPv6 peer.
The proposed principle concerns another network fault: Underlying endpoint reachability does not guarantee permitted encapsulated payloads. Here, bGP family negotiation and route policy control IPv6 NLRI exchange. The most direct correction is to enable and verify the intended IPv6 BGP family and export policy, confirmed by the selected inet6 route appears on the authorized IPv6 peer.