On a 802.1Q trunk, what is true about the native VLAN frames?

On a 802.1Q trunk, what is true about the native VLAN frames?

• A. Native VLAN frames are sent untagged; all other VLAN frames are tagged.
• B. All frames on the trunk are tagged.
• C. Native VLAN frames are dropped.
• D. There is no concept of a native VLAN.

Answer: (A)

On an 802.1Q trunk, one VLAN is designated as the native VLAN. Frames for that VLAN are sent across the trunk untagged, while frames for all other VLANs are tagged with their VLAN ID. This arrangement lets multiple VLANs share a single physical link, with the native VLAN traffic remaining untagged to preserve compatibility with devices that don’t understand tagging for that VLAN. If the native VLAN configuration differs on two ends of the trunk, untagged frames can be misinterpreted, causing traffic to be associated with the wrong VLAN or dropped.

On an 802.1Q trunk, one VLAN is designated as the native VLAN. Frames for that VLAN are sent across the trunk untagged, while frames for all other VLANs are tagged with their VLAN ID. This arrangement lets multiple VLANs share a single physical link, with the native VLAN traffic remaining untagged to preserve compatibility with devices that don’t understand tagging for that VLAN. If the native VLAN configuration differs on two ends of the trunk, untagged frames can be misinterpreted, causing traffic to be associated with the wrong VLAN or dropped.