In VLAN trunk configuration, what does the native VLAN specify?

In VLAN trunk configuration, what does the native VLAN specify?

• A. The VLAN used for untagged traffic on the trunk
• B. The VLAN used for management traffic
• C. The VLAN used for guest traffic
• D. The VLAN used for voice traffic

Answer: (A)

On a VLAN trunk, most traffic is tagged with 802.1Q VLAN IDs, but the native VLAN is the one whose traffic is sent untagged on the trunk. In other words, frames for the native VLAN traverse the trunk without a VLAN tag, and the receiving switch associates those untagged frames with the same native VLAN. This is why the native VLAN specifies the untagged traffic on the trunk. The other options describe traffic types that might be assigned to specific VLANs (like management, guest, or voice), but they aren’t what the native VLAN defines. The native VLAN is simply the VLAN whose traffic is untagged on the trunk, independent of the traffic’s role.

On a VLAN trunk, most traffic is tagged with 802.1Q VLAN IDs, but the native VLAN is the one whose traffic is sent untagged on the trunk. In other words, frames for the native VLAN traverse the trunk without a VLAN tag, and the receiving switch associates those untagged frames with the same native VLAN. This is why the native VLAN specifies the untagged traffic on the trunk.

The other options describe traffic types that might be assigned to specific VLANs (like management, guest, or voice), but they aren’t what the native VLAN defines. The native VLAN is simply the VLAN whose traffic is untagged on the trunk, independent of the traffic’s role.