A network technician configures an 802.1Q trunk link between two switches. After the configuration, VLAN 20 traffic is not passing across the trunk, although VLAN 10 traffic works fine. The technician verifies that both switches have VLAN 20 created and that the trunk is up. What is the most likely cause?
By default, trunk ports allow all VLANs, but if an allowed VLAN list is configured, only listed VLANs are forwarded. VLAN 20 is likely missing.
Why this answer
The most likely cause is that VLAN 20 is not included in the allowed VLAN list on the trunk. By default, an 802.1Q trunk allows all VLANs, but if the allowed VLAN list has been manually configured or pruned, VLAN 20 may have been excluded. Since VLAN 10 works, the trunk is operational, and both switches have VLAN 20 created, the issue is specifically that the trunk is not permitting VLAN 20 traffic.
Exam trap
CompTIA often tests the misconception that a native VLAN mismatch is the default cause of VLAN-specific traffic failures, but the real issue is usually the allowed VLAN list being misconfigured or pruned.
How to eliminate wrong answers
Option A is wrong because a native VLAN mismatch would cause control plane issues (e.g., CDP or STP problems) or traffic for the native VLAN to be misdirected, but it would not selectively block only VLAN 20 while allowing VLAN 10. Option C is wrong because dynamic desirable mode is a DTP setting that negotiates trunking; if the trunk is already up and passing VLAN 10 traffic, the trunk mode is not the issue. Option D is wrong because if the encapsulation type were ISL instead of 802.1Q, the trunk would not form or would not pass any VLAN traffic correctly, not just VLAN 20; the question states the trunk is up and VLAN 10 works, so encapsulation is compatible.