A Citrix ADC is configured with Interface 1/1 and bound to VLAN 40. A command 'bind vlan 20' on ifnum 1/1 is executed. What is the result?

A Citrix ADC is configured with Interface 1/1 and bound to VLAN 40. A command 'bind vlan 20' on ifnum 1/1 is executed. What is the result?

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

Answer: (D)

The key idea here is how VLAN binding on a Citrix ADC interface works and what determines the native (untagged) VLAN for that interface. On a given interface, binding a VLAN sets the active VLAN for that port, and this binding replaces any previous binding on that same interface. So when you bind VLAN 20 to interface 1/1, the interface’s active VLAN becomes 20 and the untagged traffic on that interface is associated with VLAN 20 as its native VLAN. The prior binding to VLAN 40 is replaced by this new binding. Therefore, the interface ends up bound to VLAN 20 with the native VLAN also being 20.

The key idea here is how VLAN binding on a Citrix ADC interface works and what determines the native (untagged) VLAN for that interface. On a given interface, binding a VLAN sets the active VLAN for that port, and this binding replaces any previous binding on that same interface. So when you bind VLAN 20 to interface 1/1, the interface’s active VLAN becomes 20 and the untagged traffic on that interface is associated with VLAN 20 as its native VLAN. The prior binding to VLAN 40 is replaced by this new binding. Therefore, the interface ends up bound to VLAN 20 with the native VLAN also being 20.