Question 250
At Pinebrook Energy Services, while commissioning a routed spine uplink, the data center fabric team observes: A leaf can reach its directly connected spine but not the loopback used for BGP sessions. What observation should be required before this case is closed?
Explanation
Correct Answer
At Pinebrook Energy Services, while commissioning a routed spine uplink, the decisive validation is: The loopback addresses ping in the underlay and the corresponding BGP transport succeeds. It verifies that the change (Provide correct loopback reachability through the intended routing design) resolved the mechanism: The underlay lacks a route to the remote loopback or its advertised prefix.
Incorrect Answers
The active forwarding table has only one selected path despite several control-plane peers, but here the case reports A leaf can reach its directly connected spine but not the loopback used for BGP sessions. Here, the underlay lacks a route to the remote loopback or its advertised prefix.
Link failure takes down tenant services even though another physical underlay path is up. Here, the underlay lacks a route to the remote loopback or its advertised prefix.
At Pinebrook Energy Services, while commissioning a routed spine uplink, this option proposes: The default route resolves to an active next hop and controlled traffic reaches the gateway. Although related to Underlay routing, BGP, BFD and ECMP, the proposed change fits another mechanism: The referenced next-hop group has no reachable selected member. The evidence in the current case requires a different result: The loopback addresses ping in the underlay and the corresponding BGP transport succeeds.