Question 390
At West Clinic, a trunk between two AOS-CX switches loses WLAN guest VLAN traffic after a template update. How should the engineer validate success against the stated requirement?
Explanation
Correct Answer
For West Clinic, the decisive mechanism is Tagged trunk allowlist. A VLAN trunk forwards only permitted tagged VLANs and its native VLAN according to configuration. Generate tagged traffic across all intended VLANs and confirm blocked VLANs remain isolated supplies measurable, case-relevant evidence that the intended behavior actually occurs.
Incorrect Answers
This is relevant to Voice VLAN LLDP-MED, where lLDP-MED can advertise voice-network attributes while the switch enforces separate VLAN policies In the West Clinic case, That test could pass while the actual user-facing requirement still fails. The specific mechanism is a VLAN trunk forwards only permitted tagged VLANs and its native VLAN according to configuration
This is relevant to End-to-end MTU and frames, where a path's effective MTU is limited by the smallest supported segment and encapsulation overhead In the West Clinic case, That test could pass while the actual user-facing requirement still fails. The specific mechanism is a VLAN trunk forwards only permitted tagged VLANs and its native VLAN according to configuration
This is relevant to ACL direction and interface, where stateless ACL effectiveness depends on interface attachment direction and rule order In the West Clinic case, That test could pass while the actual user-facing requirement still fails. The specific mechanism is a VLAN trunk forwards only permitted tagged VLANs and its native VLAN according to configuration