Question 320
At Parkhaven Municipal Networks, while verifying multiple equal-cost paths, the data center fabric team observes: A route remains installed after its intended physical next hop fails. Which review gate should be added to prevent the same error?
Explanation
Correct Answer
At Parkhaven Municipal Networks, while verifying multiple equal-cost paths, exercise next-hop failure against all critical static routes. This ongoing review specifically addresses: The static next hop is not being withdrawn or tracked through a supported reachability mechanism. It should remain part of change acceptance, not only incident closure.
Incorrect Answers
At Parkhaven Municipal Networks, while verifying multiple equal-cost paths, this option proposes: Include post-reboot persistence in routing change acceptance. It tests a different symptom: An underlay route vanishes after a leaf is reloaded but returns after a manual CLI edit. For the observed case, the relevant distinction is The static next hop is not being withdrawn or tracked through a supported reachability mechanism, with verification: The failed path leaves the forwarding set while a healthy path remains selected.
At Parkhaven Municipal Networks, while verifying multiple equal-cost paths, this option proposes: Capture selected next hops before and after routing policy deployment. That choice would be more relevant when this different symptom occurs: Traffic follows an unexpected spine after a route-policy update. The present scenario instead points to: The static next hop is not being withdrawn or tracked through a supported reachability mechanism. The correct resolution has its own verification outcome: The failed path leaves the forwarding set while a healthy path remains selected.
At Parkhaven Municipal Networks, while verifying multiple equal-cost paths, this option proposes: Check data-plane path programming whenever peer counts change. This is a valid category of fabric maintenance for another scenario (A network engineer assumes multiple BGP peers automatically imply load-balanced traffic), not the targeted action for Parkhaven Municipal Networks. The distinction is the actual cause: The static next hop is not being withdrawn or tracked through a supported reachability mechanism.