What is a recommended practice for managing a Citrix ADC high availability (HA) pair to ensure that management changes are always made on the primary Citrix ADC?

Question

Options

• AEnable management access on the Cluster IP (CLIP) address.
• BEnable USIP on both nodes (primary and secondary).
• CEnable management access to a SNIP
• DConnect to both Citrix ADCs to see which one is the primary.

• A
  6% (1)
• D
  94% (16)

Explanation

Option D is the recommended practice because each Citrix ADC node in an HA pair has its own dedicated management IP (NSIP), and after a failover event the primary/secondary roles can swap - meaning the node you managed yesterday may be the secondary today. By connecting to both nodes and checking the HA status, you confirm which is currently primary before making any configuration changes, ensuring changes replicate correctly to the secondary.

Why the distractors are wrong:

• A (CLIP): The Cluster IP address is used in a Citrix ADC cluster deployment, not an HA pair - these are two distinct architectures, and CLIP has no role in HA management.
• B (USIP): Use Source IP (USIP) is a traffic-forwarding feature that preserves the client's source IP toward backend servers; it has no bearing on HA management access.
• C (SNIP on management): SNIPs are used for ADC-to-server communication, not as a reliable management anchor. Enabling management on a SNIP does not guarantee you're connecting to the primary node.

Memory tip: Think "check before you wreck" - HA roles can flip after any failover, so always verify primary status on both nodes before touching configuration. If you just assume and configure the wrong node, the change may be overwritten during the next sync.

No community discussion yet for this question.