Scenario: A Citrix Administrator deployed a Citrix ADC in one-arm mode. Currently, the VLANs 20, 30, and 40 are tagged on the interface with the option of tagall'. What is true regarding the VLANs…

Question

Options

• AVLANS 1, 20, 30, 40, and HA packets are tagged on the interface.
• BVLANS 20, 30, and 40 are tagged on the interface.
• CVLANS 1, 20, 30, and 40 are tagged on the interface.
• DVLANS 20, 30, 40, and HA packets are tagged on the interface.

• A
  2% (1)
• B
  2% (1)
• C
  89% (41)
• D
  7% (3)

Explanation

When tagall is enabled on a Citrix ADC interface, VLAN 1 (the default/native VLAN) is also tagged, in addition to the explicitly configured VLANs (20, 30, 40) - this is the defining behavior of tagall. Normally, VLAN 1 traffic is untagged; enabling tagall overrides that and forces 802.1Q tags on all VLANs including VLAN 1, making C correct.

Why the distractors fail:

• A & D are wrong because HA (High Availability) heartbeat packets are transmitted using their own dedicated mechanism and are not VLAN-tagged - they travel independently of the 802.1Q tagging configuration.
• B is wrong because it omits VLAN 1; tagall exists precisely to add tagging to VLAN 1, which would otherwise be untagged by default.

Memory tip: Think of tagall as "tag all - including VLAN 1." The moment you see tagall, add VLAN 1 to your tagged list. HA packets are a red herring - they live outside the VLAN tagging framework entirely, so any answer that includes "HA packets" in a VLAN list is automatically suspect.

No community discussion yet for this question.