Scenario: A Citrix Administrator is configuring a Citrix ADC high availability (HA) pair with an existing Primary Citrix ADC with all resources configured. The administrator added the Secondary Citrix ADC in high availability and found that the configuration on the existing primary was removed. It is now the Secondary Citrix ADC in the HA pair.
Which two configurations could the administrator have made to prevent this from happening? (Choose two.)
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 the interfaces of the PRIMARY device.
D. Enable HA monitoring on all the interfaces of the SECONDARY device.
|
Download Printable PDF. VALID exam to help you PASS. |
 |
the reference https://docs.citrix.com/en-us/citrix-adc/13/system/high-availability-introduction/forcing-the-primary-node-stay-primary.html just elucidates A as correct. AveryC’s reference https://support.citrix.com/article/CTX116748 affirms A and reveals B and the seconds correct answer.
From the article : https://support.citrix.com/article/CTX116748
Log in to the primary NetScaler appliance and run the following command from CLI:
set ha node -hastatus STAYPRIMARY
Log in to the secondary NetScaler appliance and run the following command from CLI:
set ha node -hastatus STAYSECONDARY
So AB.
A & B
https://support.citrix.com/article/CTX116748
I think the right answer is AB or AD
On a standalone system, you must run this command before you can add a node to create an HA pair. When you add the new node, it becomes the primary node. The existing node stops processing traffic and becomes the secondary node in the HA pair.
The high availability monitor is a virtual entity that monitors an interface. You must disable the monitor for interfaces that are not connected or being used for traffic. When the monitor is enabled on an interface whose status is DOWN, the state of the node becomes NOT UP. In a high availability configuration, a primary node entering a NOT UP state might cause a high availability failover.
STAYSECONDARY is used to force the secondary device to stay as secondary, independent of the
state of the primary device.