Question 50
For a converged broadband aggregation team, operators addressed: Two OSPFv2 neighbors exchange hellos but a recently inserted ACL blocks protocol 89, preventing database synchronization on the transit segment. What is the strongest acceptance evidence?
Explanation
Correct Answer
A lab adjacency reaches Full and the LSDB counts converge without permitting unrelated sources. This confirms the approved response: Permit the required OSPF control traffic between approved peers at the correct interface policy boundary. It is relevant because: Filtering routing-protocol IP traffic can prevent adjacency even when ordinary ICMP reachability succeeds.
Incorrect Answers
Adjacency and LSP integrity counters remain stable during repeated authenticated hello exchanges. This would validate ANOTHER scenario: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. The specific correction here is: Permit the required OSPF control traffic between approved peers at the correct interface policy boundary.
In a test switchover, BFD stabilizes and the IGP reconverges within the agreed target. This would validate ANOTHER scenario: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. The specific correction here is: Permit the required OSPF control traffic between approved peers at the correct interface policy boundary.
A link-loss test switches eligible prefixes onto the backup next hop within the documented recovery target. This would validate ANOTHER scenario: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes. The specific correction here is: Permit the required OSPF control traffic between approved peers at the correct interface policy boundary.