Question 870
At Administration Block, an uplink forwards VLAN 120 but silently drops newly introduced VLAN 350. What should the engineer implement first to correct the stated condition?
Explanation
Correct Answer
For Administration Block, 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 Administration Block 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 Administration Block 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 Administration Block 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