Question 390
At Brightwater Digital Commerce, while commissioning a routed spine uplink, the data center fabric team observes: A routed subinterface can ping its neighbor but the wrong routing table is being populated. Which result would establish that the original defect has been corrected?
Explanation
Correct Answer
At Brightwater Digital Commerce, while commissioning a routed spine uplink, for Brightwater Digital Commerce, accept the repair only after this observation: The route appears in the target tenant or underlay table and not elsewhere. The test distinguishes real recovery from a superficial status change.
Incorrect Answers
At Brightwater Digital Commerce, while commissioning a routed spine uplink, this option proposes: The forwarding state lists the intended next-hop set for the test destination. It tests a different symptom: A network engineer assumes multiple BGP peers automatically imply load-balanced traffic. For the observed case, the relevant distinction is The BGP or static route belongs to an incorrect network instance, with verification: The route appears in the target tenant or underlay table and not elsewhere.
At Brightwater Digital Commerce, while commissioning a routed spine uplink, this option proposes: The test destination is reached while the blackhole action is absent from the route. That choice would be more relevant when this different symptom occurs: A static route sends production traffic into a blackhole after an emergency change. The present scenario instead points to: The BGP or static route belongs to an incorrect network instance. The correct resolution has its own verification outcome: The route appears in the target tenant or underlay table and not elsewhere.
At Brightwater Digital Commerce, while commissioning a routed spine uplink, this option proposes: A controlled single-link failure leaves remote VTEP loopbacks reachable. This is a valid category of fabric maintenance for another scenario (Link failure takes down tenant services even though another physical underlay path is up), not the targeted action for Brightwater Digital Commerce. The distinction is the actual cause: The BGP or static route belongs to an incorrect network instance.