Question 110
A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. Which controlled change best addresses the described requirement?
Explanation
Correct Answer
This action addresses the stated defect: bind only authorized tagged and untagged VN attachments to the selected generic-system port. The underlying constraint is that connectivity templates define host-facing virtual-network endpoint membership and tagging behavior. Verify rather than assume success: confirm the host receives exactly the intended VLANs and no unrelated tenant traffic.
Incorrect Answers
That choice—“Create or correct a scoped connectivity template and routing policy for the authorized VRF”—addresses this other problem: A routed external firewall must exchange routes with a border leaf for only one tenant VRF. Here the scenario is: A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. Bind only authorized tagged and untagged VN attachments to the selected generic-system port. The most relevant correction is “Bind only authorized tagged and untagged VN attachments to the selected generic-system port”.
“Constrain the external peering policy to explicitly permitted prefixes and verify intended attachment” is associated with a distinct issue: A route export template applied to a border device advertises all tenant prefixes beyond the data center. By contrast, the actual problem is: A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. Bind only authorized tagged and untagged VN attachments to the selected generic-system port. The most relevant correction is “Bind only authorized tagged and untagged VN attachments to the selected generic-system port”.
“Apply documented DCI policies for only authorized tenant prefixes and virtual-network reachability” is relevant to a different condition: A data-center interconnect extends selected tenant segments between two sites but one site imports unrelated virtual networks. The stated question instead concerns: A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. Bind only authorized tagged and untagged VN attachments to the selected generic-system port. The most relevant correction is “Bind only authorized tagged and untagged VN attachments to the selected generic-system port”.