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.)
To prevent the problem where the existing primary Citrix ADC's configuration is removed and it becomes the secondary, the administrator could have set the Secondary Citrix ADC to stay secondary in the Configure HA Node settings. This would ensure that even after addition to the HA pair, the secondary device does not take over as primary. Additionally, setting the Primary Citrix ADC to stay primary in the Configure HA Node settings would ensure it retains its primary role regardless of new devices being added to the HA pair.
B and C -> https://support.citrix.com/article/CTX116748
Agree its B and C, I have set this up before.
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-availability-introduction/forcing-a-secondary-node-to-stay-secondary.html 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 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-availability-introduction/forcing-the-primary-node-stay-primary.html B and C sounds good for me too
correct