Question 720
A hypervisor trunk is planned to carry two tagged virtual networks, yet the leaf attachment is configured as a single untagged access connection. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
This control reduces recurrence of the same class of failure: An Apstra connectivity template can represent intended Layer 2 endpoint attachment and its tagged or untagged VLAN behavior. Apply the recurring practice: Verify server-facing tagging requirements whenever a host changes operating system or virtualization configuration. The previous example was: A hypervisor trunk is planned to carry two tagged virtual networks, yet the leaf attachment is configured as a single untagged access connection.
Incorrect Answers
Track border interface, routing-zone and peer parameters together for tenant interconnect changes. That concerns routing zone external BGP connection, while the issue here is tenant VLAN tagging through connectivity template. Select the supported access or tagged connection primitive for the generic system and verify the host-side VLAN or trunk configuration.
Apstra virtual network intent must map the correct attachment VLAN and EVPN/VXLAN identity to the intended isolated tenant service. However, the present prevention decision is grounded in: A hypervisor trunk is planned to carry two tagged virtual networks, yet the leaf attachment is configured as a single untagged access connection. For this issue, select the supported access or tagged connection primitive for the generic system and verify the host-side VLAN or trunk configuration.
Recheck virtualization inventory and network attachment mappings during cluster onboarding or maintenance. Here, an Apstra connectivity template can represent intended Layer 2 endpoint attachment and its tagged or untagged VLAN behavior. Specifically for the prevention question, the case to validate is: A hypervisor trunk is planned to carry two tagged virtual networks, yet the leaf attachment is configured as a single untagged access connection.