Question 380
At Harborstone Rail Logistics, while reviewing route policies, the data center fabric team observes: A BGP session is Established but the expected underlay prefix is not learned. What ongoing operational safeguard directly addresses this root issue?
Explanation
Correct Answer
At Harborstone Rail Logistics, while reviewing route policies, the preventive control is: Test announced routes and applied policy alongside session state. It catches the same mechanism (The prefix was not originated or an export policy prevented its advertisement) before the symptom recurs. An appropriate regression observation is: The remote peer receives the expected prefix with the intended next hop.
Incorrect Answers
At Harborstone Rail Logistics, while reviewing route policies, this option proposes: Validate symmetric reachability across fabric-to-external boundaries. Although related to Underlay routing, BGP, BFD and ECMP, the proposed change fits another mechanism: The fabric edge lacks a route toward the external destination or the return subnet. The evidence in the current case requires a different result: The remote peer receives the expected prefix with the intended next hop.
At Harborstone Rail Logistics, while reviewing route policies, this option proposes: Capture selected next hops before and after routing policy deployment. Using that approach would investigate Traffic follows an unexpected spine after a route-policy update instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The prefix was not originated or an export policy prevented its advertisement.
At Harborstone Rail Logistics, while reviewing route policies, this option proposes: Review fast-detection timers against real network jitter and loss. The alternative focuses on BFD detection values are too aggressive for the observed link characteristics, not on the stated defect. For this scenario the expected acceptance result would be: The remote peer receives the expected prefix with the intended next hop.