Question 120
At fictional Pinewell Electronics, a network engineer supporting engineering labs is reviewing VRRP, BFD and redundancy design during a lab-to-production acceptance (HCIP-H12-821-RELIABILITY-030). The observed network issue is: An operator increases routing protocol Dead timers to stabilize a flaky link but overlooks the resulting slow failover. Which next engineering action best addresses the reported problem?
Explanation
Correct Answer
The directly responsive action is: Repair the underlying link and choose supported detection timers or BFD that match availability requirements. The specific reported fault is: An operator increases routing protocol Dead timers to stabilize a flaky link but overlooks the resulting slow failover. Confirmation should show: Failure detection meets the service objective without spurious adjacency resets. The supporting technical principle is: Reliability design balances false failures against convergence latency.
Incorrect Answers
“Configure suitable upstream route tracking and investigate WAN reachability beyond the LAN gateway” responds to another technical or business failure: A VRRP virtual IP responds locally but remote services fail because both gateway uplinks have lost their default route. That source case depends on: Gateway availability and end-to-end network reachability are different reliability properties. The present issue is: An operator increases routing protocol Dead timers to stabilize a flaky link but overlooks the resulting slow failover. The more direct action is “Repair the underlying link and choose supported detection timers or BFD that match availability requirements” because Reliability design balances false failures against convergence latency.
“Redesign independent backup next-hop reachability and validate actual alternate path availability” responds to another technical or business failure: An interface failure is detected rapidly by BFD but the backup route points to the same failed upstream dependency. That source case depends on: Fast fault detection is ineffective without a genuinely independent recovery path. The present issue is: An operator increases routing protocol Dead timers to stabilize a flaky link but overlooks the resulting slow failover. The more direct action is “Repair the underlying link and choose supported detection timers or BFD that match availability requirements” because Reliability design balances false failures against convergence latency.
“Identify shared physical dependencies and add independent power or placement where feasible” responds to another technical or business failure: A campus design has redundant routers and switches but both power feeds terminate on one supply circuit. That source case depends on: Network reliability depends on eliminating shared risks, not only duplicating network devices. The present issue is: An operator increases routing protocol Dead timers to stabilize a flaky link but overlooks the resulting slow failover. The more direct action is “Repair the underlying link and choose supported detection timers or BFD that match availability requirements” because Reliability design balances false failures against convergence latency.