When an auto-failover occurs and a Standby is promoted to Leader, the old Leader is considered lost by the cluster. To reintroduce it, it must be rebuilt as a Standby. The correct procedure involves generating a new Standby seed file on the current Leader. This seed file contains the necessary configuration and certificates for the old Leader node to securely connect and synchronize with the new Leader. The old Leader node is then re-initialized as a Standby using this seed file, effectively re-enrolling it into the cluster in its new role.

B: This is incorrect because it describes rebuilding the newly promoted Leader, which is the active and functioning node. This would cause a service outage and is the opposite of the required repair.

C: This is incorrect as it suggests rebuilding both the new Leader and the other healthy Standby. This is a destructive and unnecessary action that would dismantle the entire working cluster.

D: This is incorrect because re-uploading the auto-failover policy is not a required step for re-enrolling a failed node. The seed generation process on the new Leader is sufficient to prepare the cluster for the new Standby.

1. CyberArk Conjur Enterprise Documentation v12.8

"Set up a High Availability Cluster" -> "Recover from a Leader failure". The official procedure states: "After a failover

the old Leader is no longer part of the cluster. To add it back to the cluster

you must reconfigure it as a Standby." The documented steps include generating a seed file on the new Leader for the old Leader's host

and then using that seed to configure the old Leader as a new Standby. This directly supports option A.

2. CyberArk Conjur Enterprise Documentation v12.8

"evoke command reference" -> "evoke seed standby". The documentation for this command specifies that it is run on the Leader to "generate and package the configuration files and certificates for a new Standby." This confirms that the new Leader must generate the seed for the node being re-enrolled.