Which VLANs are allowed on the trunk in the correct port-access configuration for the APs?

Which VLANs are allowed on the trunk in the correct port-access configuration for the APs?

• A. 100,200,300
• B. 100,200
• C. 200,300
• D. 100

Answer: (C)

In port-access for APs, the switch port acts like a trunk that carries both a native management VLAN (untagged) and additional VLANs that tag wireless traffic. The VLANs used to carry SSID traffic—those that map to the wireless networks—must be allowed as tagged traffic on the trunk. Choosing the VLANs 200 and 300 reflects that those are the VLANs assigned to the APs for wireless data (the tagged traffic). VLAN 100 is the native management VLAN, which remains untagged on the trunk and isn’t listed among the allowed tagged VLANs. If you tried to allow 100 as a tagged VLAN, it would disrupt the native untagged management traffic and cause APs to misbehave. So, the trunk should permit the VLANs used for user data (200 and 300), while the management VLAN (100) stays native.

In port-access for APs, the switch port acts like a trunk that carries both a native management VLAN (untagged) and additional VLANs that tag wireless traffic. The VLANs used to carry SSID traffic—those that map to the wireless networks—must be allowed as tagged traffic on the trunk.

Choosing the VLANs 200 and 300 reflects that those are the VLANs assigned to the APs for wireless data (the tagged traffic). VLAN 100 is the native management VLAN, which remains untagged on the trunk and isn’t listed among the allowed tagged VLANs. If you tried to allow 100 as a tagged VLAN, it would disrupt the native untagged management traffic and cause APs to misbehave.

So, the trunk should permit the VLANs used for user data (200 and 300), while the management VLAN (100) stays native.