Question 270
At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, the data center fabric team observes: All spine-to-leaf BGP sessions exist but one leaf uses a single path instead of ECMP. Which evidence directly validates the intended repair?
Explanation
Correct Answer
At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, the decisive validation is: The selected route exposes multiple valid next hops and a link-loss test preserves access. It verifies that the change (Review BGP path attributes and ECMP configuration to permit only equivalent eligible paths) resolved the mechanism: The learned routes differ in preference or multipath eligibility.
Incorrect Answers
An eBGP leaf peering configuration uses an incorrect update source for loopback peering. Here, the learned routes differ in preference or multipath eligibility.
At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, this option proposes: BFD establishes and a controlled path failure triggers the intended rapid adjacency reaction. This is a valid category of fabric maintenance for another scenario (A BFD session shows Down while the BGP peer continues waiting for its normal hold timer), not the targeted action for Highcrest Municipal Networks. The distinction is the actual cause: The learned routes differ in preference or multipath eligibility.
At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, this option proposes: An end-to-end test succeeds with routes present in both forward and return directions. Using that approach would investigate A new server subnet cannot reach external routed services although its gateway replies instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The learned routes differ in preference or multipath eligibility.