Question 300
At Northpoint Health Systems, while restoring an underlay BGP adjacency, the data center fabric team observes: Underlay BGP sessions appear stable but a wrong VLAN tag prevents one adjacency from exchanging routes. What ongoing operational safeguard directly addresses this root issue?
Explanation
Correct Answer
At Northpoint Health Systems, while restoring an underlay BGP adjacency, for Northpoint Health Systems, include the safeguard: Check encapsulation and interface state before route-policy adjustments. It reduces repeat risk from the original mechanism and complements a validation of: The appropriate Layer 3 adjacency forms and exchanges required routes.
Incorrect Answers
At Northpoint Health Systems, while restoring an underlay BGP adjacency, this option proposes: Validate symmetric reachability across fabric-to-external boundaries. This option assumes the other problem (A new server subnet cannot reach external routed services although its gateway replies) is present. The case instead describes Underlay BGP sessions appear stable but a wrong VLAN tag prevents one adjacency from exchanging routes, for which the causal issue is The control-plane frames do not reach the intended tagged subinterface.
At Northpoint Health Systems, while restoring an underlay BGP adjacency, this option proposes: Use positive and negative prefix fixtures when revising route policy. It tests a different symptom: A route policy intended to permit fabric loopbacks inadvertently permits all tenant prefixes. For the observed case, the relevant distinction is The control-plane frames do not reach the intended tagged subinterface, with verification: The appropriate Layer 3 adjacency forms and exchanges required routes.
At Northpoint Health Systems, while restoring an underlay BGP adjacency, this option proposes: Maintain explicit management-prefix exclusion tests. That choice would be more relevant when this different symptom occurs: A leaf exports its connected management subnet into tenant-visible fabric routing. The present scenario instead points to: The control-plane frames do not reach the intended tagged subinterface. The correct resolution has its own verification outcome: The appropriate Layer 3 adjacency forms and exchanges required routes.