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 adds the secondary Citrix ADC in HA and discovers that the configuration on the existing primary was removed and is now the secondary Citrix ADC in the HA pair.
Which two configurations could the administrator have used to prevent this from happening?
(Choose two.)
A.
Set the primary Citrix ADC to stay primary in the Configure HA Node settings.
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.
B.
Set the secondary Citrix ADC to stay secondary in the Configure HA Node settings.
C.
Enable HA monitoring on all secondary device interfaces.
C.
Enable HA monitoring on all secondary device interfaces.
D.
Enable HA monitoring on all primary device interfaces.
D.
Enable HA monitoring on all primary device interfaces.
Suggested answer: B, C
Explanation:
Forcing the node to stay secondary works on both standalone and secondary nodes. On a standalone node, you must use this option before you can add a node to create an HA pair. When you add the new node, the existing node stops processing traffic and becomes the secondary node. The new node becomes the primary node.
https://docs.citrix.com/en-us/citrix-adc/current-release/system/high-availabilityintroduction/forcing-a-secondary-node-to-stay-secondary.htmlOn a standalone node, you must use this option before you can add a node to create an HA pair.
When you add the new node, the existing node continues to function as the primary node, and the new node becomes the secondary node.
https://docs.citrix.com/en-us/citrix-adc/current-release/system/high-availabilityintroduction/forcing-the-primary-node-stay-primary.html
Question