Question 250
Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An IS-IS link shows Level-2 Up while remote IPv6 prefixes are absent because address-family participation differs. Which observable result most directly verifies that this network issue was resolved?
Explanation
Correct Answer
For this scenario, the observed situation is: An IS-IS link shows Level-2 Up while remote IPv6 prefixes are absent because address-family participation differs. The most directly supported response is: Check IS-IS IPv6 topology advertisements, supported AF configuration, and next-hop calculation. Technical basis: A live IS-IS adjacency does not guarantee all address-family reachability is exchanged. Evidence of success: IPv6 prefixes appear in the intended database and routing table after AF correction. Ongoing protection: Track adjacency and per-family prefix counters separately.
Incorrect Answers
NAT64 bridges IPv6 endpoints to IPv4 destinations with state and addressing considerations. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: A live IS-IS adjacency does not guarantee all address-family reachability is exchanged. A passing check should show: IPv6 prefixes appear in the intended database and routing table after AF correction.
OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: A live IS-IS adjacency does not guarantee all address-family reachability is exchanged. A passing check should show: IPv6 prefixes appear in the intended database and routing table after AF correction.
BFD supplies fast bidirectional failure detection independently of slower protocol hello timers. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: A live IS-IS adjacency does not guarantee all address-family reachability is exchanged. A passing check should show: IPv6 prefixes appear in the intended database and routing table after AF correction.