After binding VLAN 20 to interface 1/1 on a Citrix ADC that is already bound to VLAN 40, which of the following describes the interface's VLAN binding and native VLAN?

After binding VLAN 20 to interface 1/1 on a Citrix ADC that is already bound to VLAN 40, which of the following describes the interface's VLAN binding and native VLAN?

• A. Interface 1/1 is bound to VLAN 20, and native VLAN is NOT changed.
• B. Interface 1/1 is bound to VLAN 20, and native VLAN is 1.
• C. Interface 1/1 is bound to VLAN 20, and native VLAN is 20.
• D. Interface 1/1 is bound to VLAN 20, and native VLAN is 40.

Answer: (C)

In Citrix ADC, a port can carry multiple VLANs, and the native VLAN is the one used for untagged frames on that port. When you bind a new VLAN to an interface that already has another VLAN bound, the interface’s native (untagged) VLAN becomes the VLAN you’ve just bound. So after binding VLAN 20 to interface 1/1 (which already had VLAN 40), the interface is configured to carry VLAN 20 as the native, untagged traffic, while VLAN 40 would be carried as tagged traffic. That’s why the correct description is that the interface is bound to VLAN 20 and the native VLAN is 20.

In Citrix ADC, a port can carry multiple VLANs, and the native VLAN is the one used for untagged frames on that port. When you bind a new VLAN to an interface that already has another VLAN bound, the interface’s native (untagged) VLAN becomes the VLAN you’ve just bound. So after binding VLAN 20 to interface 1/1 (which already had VLAN 40), the interface is configured to carry VLAN 20 as the native, untagged traffic, while VLAN 40 would be carried as tagged traffic. That’s why the correct description is that the interface is bound to VLAN 20 and the native VLAN is 20.