A Citrix ADC has Interface 1/1 bound to VLAN 40. After executing bind vlan 20 ifnum1/1, what is the result?

• A. Interface 1/1 is bound to VLAN 20, and native VLAN is 20.
• 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 NOT changed.
• D. Interface 1/1 is bound to VLAN 20, and native VLAN is 40.

Answer: (C)

Binding a VLAN to an interface in Citrix ADC adds that VLAN as a tagged membership on the port, meaning traffic for that VLAN is carried with 802.1Q tagging on that interface. The native VLAN, which carries untagged frames, remains unchanged unless you explicitly reconfigure it. In this scenario, interface 1/1 was already bound to VLAN 40 as its native (untagged) context, and binding VLAN 20 simply adds VLAN 20 as a tagged VLAN on the same interface. So the interface ends up bound to VLAN 20 as a tagged VLAN while the native VLAN continues to be 40. That’s why the result is that the interface is bound to VLAN 20 and the native VLAN is not changed.