Scenario: A Citrix Administrator manages an environment that has a Citrix ADC high availability (HA) pair running on two MPX appliances. The administrator notices that the state of the secondary…

Question

Options

• AThe remote procedure call (RPC) nodes are incorrectly configured.
• BTCP port 22 is disabled between the primary and secondary ADCs.
• CThe administrator made both Citrix ADCs primary.
• DThe administrator made both Citrix ADCs primary.

• A
  82% (27)
• B
  3% (1)
• C
  6% (2)
• D
  9% (3)

Explanation

RPC nodes are the dedicated communication channel Citrix ADC HA pairs use to synchronize configuration and exchange state information. When RPC nodes are misconfigured - such as having mismatched passwords or incorrect IP addresses - the primary node loses the ability to query the secondary's health, causing the secondary to report an "Unknown" state rather than "UP" or "DOWN."

Why the distractors are wrong:

• B (TCP port 22): Port 22 is SSH for management access, not HA communication. Citrix ADC HA heartbeats use UDP 3003, and blocking port 22 would only affect CLI/SSH access, not HA state reporting.
• C and D are identical options (both describe forcing both nodes to primary), which appears to be a question error. Forcing both nodes primary typically results in a "split-brain" or "Independent" state - not "Unknown" - since both nodes can still report their own status.

Memory tip: Think of RPC as the "referee" between the two ADC nodes. If the referee can't reach a player (broken RPC), the game status of that player becomes unknown - not lost, not won, just invisible to the system.

No community discussion yet for this question.