Question 490
At West Clinic, a trunk between two AOS-CX switches loses WLAN guest VLAN traffic after a template update. Which implementation directly addresses this campus fault without replacing the wrong component?
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. Permit required tagged VLANs on both trunk interfaces while restricting unnecessary VLANs establishes the needed configuration in the case rather than merely measuring a symptom.
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, Changing that neighboring feature does not implement the missing function. 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, Changing that neighboring feature does not implement the missing function. 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, Changing that neighboring feature does not implement the missing function. The specific mechanism is a VLAN trunk forwards only permitted tagged VLANs and its native VLAN according to configuration