Scenario: A Citrix ADC is configured with Interface 1/1 and bound to VLAN 40. A Citrix Administrator executes the below command: > bind vlan 20 -ifnum 1/1 What is the result of executing this…

Question

Options

• AInterface 1/1 is bound to VLAN 20, and native VLAN is 40.
• BInterface 1/1 is bound to VLAN 20, and native VLAN is 20.
• CInterface 1/1 is bound to VLAN 20, and native VLAN
• Dinterface 1/1 is bound to VLAN 20, and native VLAN is NOT changed.

• A
  3% (1)
• B
  3% (1)
• C
  8% (3)
• D
  86% (31)

Explanation

Option D is correct because the bind vlan 20 -ifnum 1/1 command adds interface 1/1 as a member of VLAN 20, but does not alter the interface's existing native VLAN assignment - it simply extends VLAN membership without touching the native VLAN configuration, which remains at whatever it was previously set to (VLAN 40 in this case).

Why the distractors are wrong:

• A is misleading because while the native VLAN does remain 40, the phrasing implies the command set it to 40, when in reality the command made no change to the native VLAN at all - D captures this distinction more precisely.
• B is wrong because the native VLAN does not automatically become VLAN 20 just because you bind the interface to it; changing the native VLAN requires explicit untagged binding configuration.
• C is incomplete/incorrect - the native VLAN is not wiped or unset by this command.

Memory tip: Think of bind vlan as adding a VLAN membership, not moving the interface. The native VLAN is sticky - it only changes when you explicitly reconfigure it. "Bind adds, never moves."

No community discussion yet for this question.