Question 340
At Highcrest Rail Logistics, while planning a link-failure test, the data center fabric team observes: A static default route appears in configuration but never forwards traffic. What repeatable acceptance check would reduce recurrence?
Explanation
Correct Answer
At Highcrest Rail Logistics, while planning a link-failure test, for Highcrest Rail Logistics, include the safeguard: Monitor next-hop resolution, not merely static-route configuration presence. It reduces repeat risk from the original mechanism and complements a validation of: The default route resolves to an active next hop and controlled traffic reaches the gateway.
Incorrect Answers
At Highcrest Rail Logistics, while planning a link-failure test, this option proposes: Check data-plane path programming whenever peer counts change. The option describes a different failure mode: A network engineer assumes multiple BGP peers automatically imply load-balanced traffic. It would address The active forwarding table has only one selected path despite several control-plane peers, but here the case reports A static default route appears in configuration but never forwards traffic. The current required evidence is: The default route resolves to an active next hop and controlled traffic reaches the gateway.
At Highcrest Rail Logistics, while planning a link-failure test, this option proposes: Include post-reboot persistence in routing change acceptance. That choice would be more relevant when this different symptom occurs: An underlay route vanishes after a leaf is reloaded but returns after a manual CLI edit. The present scenario instead points to: The referenced next-hop group has no reachable selected member. The correct resolution has its own verification outcome: The default route resolves to an active next hop and controlled traffic reaches the gateway.
At Highcrest Rail Logistics, while planning a link-failure test, this option proposes: Include peer transport checks before tuning route policies. Although related to Underlay routing, BGP, BFD and ECMP, the proposed change fits another mechanism: The peer address is unreachable or TCP 179 is blocked by the underlay policy. The evidence in the current case requires a different result: The default route resolves to an active next hop and controlled traffic reaches the gateway.