In a Citrix ADC high-availability pair, which configuration setting keeps the primary device from losing its role when the secondary is added?

In a Citrix ADC high-availability pair, which configuration setting keeps the primary device from losing its role when the secondary is added?

• A. Set the primary Citrix ADC to stay primary in the Configure HA Node settings.
• B. Set the secondary Citrix ADC to stay secondary in the Configure HA Node settings.
• C. Enable HA monitoring on all secondary device interfaces.
• D. Enable HA monitoring on all primary device interfaces.

Answer: (A)

In an HA pair, the system can be guided to keep the current master from changing roles when a second node joins by using the stay-primary option on the primary. Setting the primary Citrix ADC to stay primary explicitly pins its role as the master, so when the secondary is added, the primary does not relinquish its master status. This is the direct mechanism to prevent an automatic role flip during the initial HA setup. The other options don’t achieve this. Making the secondary stay secondary doesn’t enforce the primary’s master role, and turning on HA monitoring on interfaces affects failover behavior based on connectivity rather than locking the master role. Monitoring on primary interfaces could cause failover if the primary loses reachability, which is the opposite of preserving its role.

In an HA pair, the system can be guided to keep the current master from changing roles when a second node joins by using the stay-primary option on the primary. Setting the primary Citrix ADC to stay primary explicitly pins its role as the master, so when the secondary is added, the primary does not relinquish its master status. This is the direct mechanism to prevent an automatic role flip during the initial HA setup.

The other options don’t achieve this. Making the secondary stay secondary doesn’t enforce the primary’s master role, and turning on HA monitoring on interfaces affects failover behavior based on connectivity rather than locking the master role. Monitoring on primary interfaces could cause failover if the primary loses reachability, which is the opposite of preserving its role.