Question 780
A routing peer detects a dead neighbor too slowly for a real-time service even when the interface stays up. What implementation step and validation result should be selected?
Explanation
Correct Answer
Because bFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments, the best response is to evaluate BFD liveness detection with the associated routing protocol. A reviewer can close the technical case only after confirming that a controlled forwarding failure is detected within the approved target.
Incorrect Answers
That result would be useful for a different failure, namely: A Routing Engine switchover retains data-plane traffic briefly but causes OSPF adjacencies to restart. The current case specifically calls for: Evaluate BFD liveness detection with the associated routing protocol. The required observed result is: A controlled forwarding failure is detected within the approved target.
Review VRRP virtual router roles, priority and failover behavior is a relevant step for the separate scenario in which two edge routers advertise one gateway service and an engineer expects both to be virtual master without a redundancy plan. It does not directly fix this case. Instead evaluate BFD liveness detection with the associated routing protocol; verify: A controlled forwarding failure is detected within the approved target.
The alternative addresses a broadcast OSPF segment experiences repeated DR elections after interface priority changes, not the present root cause. Here the selected correction must reflect bFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments. Test for: A controlled forwarding failure is detected within the approved target.