Question 770
A new virtual network is created with a VNI inconsistent with its tenant service record, causing one leaf to encapsulate traffic into the wrong overlay segment. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
The preventive practice is aligned with the diagnosed mechanism, not an unrelated protection. Maintain a tenant VNI allocation register and validate mapping when expanding virtual networks across racks. Local VLAN numbers are not a sufficient global tenant identifier in an EVPN-VXLAN fabric.
Incorrect Answers
Routing-zone connectivity and security policy authorization are distinct requirements when business traffic crosses controlled service boundaries. Here, apstra virtual network intent must map the correct attachment VLAN and EVPN/VXLAN identity to the intended isolated tenant service.
An Apstra connectivity template can represent intended Layer 2 endpoint attachment and its tagged or untagged VLAN behavior. However, the present prevention decision is grounded in: A new virtual network is created with a VNI inconsistent with its tenant service record, causing one leaf to encapsulate traffic into the wrong overlay segment. For this issue, inspect virtual network and VNI definitions with connectivity template assignments and correct any mismatched tenant service mappings.
Document tenant-scoped addressing and avoid using global subnet uniqueness as the only isolation control. Here, apstra virtual network intent must map the correct attachment VLAN and EVPN/VXLAN identity to the intended isolated tenant service.