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 USIP on both nodes (primary and secondary).
• BConnect to both Citrix ADCs to see which one is the primary.
• CEnable management access to a SNIP.
• DEnable management access on the Cluster IP (CLIP) address.

• A
  3% (2)
• B
  10% (6)
• C
  79% (49)
• D
  8% (5)

Explanation

Enabling management access on a SNIP (Subnet IP) is correct because SNIPs are floating IPs - they always reside on the whichever node is currently primary. After a failover, the SNIP moves to the new primary automatically, so any administrator connecting to that SNIP is always guaranteed to be on the primary node without needing to check manually.

Why the distractors are wrong:

• (A) USIP (Use Source IP) controls how the ADC selects its source IP when connecting to backend servers - it's a traffic-forwarding feature with no relevance to HA management access.
• (B) Connecting to both nodes to identify the primary is manual, error-prone, and not a scalable practice - the question asks for a recommended (automated/reliable) method.
• (D) CLIP (Cluster IP) is used in Citrix ADC Clustering, which is a completely different redundancy model from an HA pair; HA pairs don't have a CLIP.

Memory tip: Think "SNIP follows the ship's captain" - the SNIP always floats to the primary (the captain), so management via SNIP means you're always steering the primary node.

No community discussion yet for this question.