In a default ADC configuration, if VLAN 20 is bound to an interface as tagged, which VLANs will be bound as tagged?

In a default ADC configuration, if VLAN 20 is bound to an interface as tagged, which VLANs will be bound as tagged?

• A. VLAN 20 tagged only.
• B. VLAN 20 untagged.
• C. VLAN 1 tagged; VLAN 20 tagged.
• D. VLAN 1 tagged; VLAN 20 untagged.

Answer: (D)

On a trunk interface, one VLAN is native (untagged) and all other VLANs that are carried on the trunk are tagged with 802.1Q tags. In a default Citrix ADC setup, VLAN 1 is typically treated as the native VLAN, so frames for VLAN 1 are untagged, while other VLANs bound to that interface can be tagged. If VLAN 20 is bound as tagged, the interface will tag frames for VLAN 20, and VLAN 1 will remain untagged as the native VLAN. So the VLANs bound as tagged on that interface would be VLAN 20 only, with VLAN 1 staying untagged. If you wanted VLAN 1 to be tagged as well, you would need to bind it as tagged explicitly.

On a trunk interface, one VLAN is native (untagged) and all other VLANs that are carried on the trunk are tagged with 802.1Q tags. In a default Citrix ADC setup, VLAN 1 is typically treated as the native VLAN, so frames for VLAN 1 are untagged, while other VLANs bound to that interface can be tagged.

If VLAN 20 is bound as tagged, the interface will tag frames for VLAN 20, and VLAN 1 will remain untagged as the native VLAN. So the VLANs bound as tagged on that interface would be VLAN 20 only, with VLAN 1 staying untagged. If you wanted VLAN 1 to be tagged as well, you would need to bind it as tagged explicitly.