Question 780
A data center offers centralized DNS across isolated customers while requiring strict east-west access boundaries. Which design or operational principle best explains this behavior?
Explanation
Correct Answer
shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation. Here, a data center offers centralized DNS across isolated customers while requiring strict east-west access boundaries. A useful discriminating check is to inspect the proposed external or shared-services routing path, import policy and required security controls.
Incorrect Answers
The option “DCI design must coordinate intended virtual-network IDs, routing zones and controlled route distribution between sites” is useful in a different setting: A multiregion deployment needs to preserve tenant boundaries while propagating specific data center routes across a DCI. The case being tested is: A data center offers centralized DNS across isolated customers while requiring strict east-west access boundaries. Shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation. The controlling principle is “Shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation”.
“Hypervisor network labels and Apstra fabric virtual-network connectivity must both represent the intended tenant service” is relevant to a different condition: A virtualized server moves to another rack and vCenter shows the correct network label while the fabric lacks the required VN attachment. The stated question instead concerns: A data center offers centralized DNS across isolated customers while requiring strict east-west access boundaries. Shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation. The controlling principle is “Shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation”.
That choice—“Routing policy and connectivity-template scope determine which tenant prefixes cross external boundaries”—addresses this other problem: A route export template applied to a border device advertises all tenant prefixes beyond the data center. Here the scenario is: A data center offers centralized DNS across isolated customers while requiring strict east-west access boundaries. Shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation. The controlling principle is “Shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation”.