nerdexam
Citrix

1Y0-231 · Question #18

Scenario: While performing a disaster recovery test, a Citrix Administrator decides to failover the Citrix ADC high availability (HA) pair appliances. The administrator notices that the failover is…

The correct answer is A. HA monitoring is enabled on an interface of the secondary node that shows as ENABLED. Option A is correct because when HA monitoring (HAMON) is enabled on an interface of the secondary node - even one that appears administratively "ENABLED" - the secondary continuously evaluates its own interface health before accepting promotion. If that monitored interface has…

High Availability

Question

Scenario: While performing a disaster recovery test, a Citrix Administrator decides to failover the Citrix ADC high availability (HA) pair appliances. The administrator notices that the failover is NOT working as expected, and the secondary Citrix ADC is NOT taking over as primary. The administrator suspects that networking issues may be causing the failure. What could be the cause of this issue?

Options

  • AHA monitoring is enabled on an interface of the secondary node that shows as ENABLED,
  • BHA monitoring is enabled on a disabled interface of the primary node.
  • CHA heartbeats are only seen on some enabled interfaces of the secondary node.
  • DThe Independent Network Configuration (INC) mode is enabled on the primary node.

How the community answered

(52 responses)
  • A
    83% (43)
  • B
    2% (1)
  • C
    10% (5)
  • D
    6% (3)

Explanation

Option A is correct because when HA monitoring (HAMON) is enabled on an interface of the secondary node - even one that appears administratively "ENABLED" - the secondary continuously evaluates its own interface health before accepting promotion. If that monitored interface has a physical link problem (link down despite being admin-enabled), the secondary considers itself degraded and will refuse to take over as primary, triggering the "STAYSECONDARY" condition. This is a deliberate safety mechanism to prevent a degraded node from becoming primary and disrupting network traffic.

Why the distractors are wrong:

  • B is wrong because HAMON on a disabled interface of the primary would cause the primary to initiate a failover toward the secondary - the opposite problem; it triggers takeover rather than blocking it.
  • C is wrong because partial heartbeat visibility means HA communication is still partially functional; this may indicate a minor network issue but would not completely block failover.
  • D is wrong because INC (Independent Network Configuration) mode simply allows the HA pair to have different IP configurations per node (typically used for geographically separated pairs) and does not inhibit the failover mechanism itself.

Memory tip: Think "sick secondary stays seated" - if the secondary detects a HAMON-enabled interface is unhealthy, it refuses to stand up as primary, no matter what. HAMON on the primary pushes failover; HAMON on the secondary blocks it.

Topics

#Citrix ADC HA#HA Failover#HA Monitoring#Troubleshooting

Community Discussion

No community discussion yet for this question.

Full 1Y0-231 Practice