When a DR Vault Server becomes an active vault, it will automatically fail back to the original state once the Primary Vault comes back online.

Automatic failback from a Disaster Recovery (DR) Vault to the Primary Vault is not the default behavior. By default, failback is a manual process to ensure the Primary Vault is stable and fully synchronized before resuming production operations. However, automatic failback can be configured. This is controlled by the EnableFailback parameter within the padr.ini file on the DR Vault server. Setting this parameter to Yes will cause the DR service to automatically fail back when the Primary Vault becomes available. Although the question uses the name AllowFailback, option C correctly identifies the mechanism (a configurable setting) and the correct configuration file (padr.ini).

A. The default behavior is manual failback (EnableFailback=No), not automatic. This prevents flapping scenarios where an unstable Primary Vault repeatedly comes online and fails.

B. Automatic failback is a possible, albeit non-default, feature that can be enabled through configuration.

D. The dbparm.ini file is the primary configuration file for the Vault server itself, not for the Disaster Recovery service agent, which is configured via padr.ini.

1. CyberArk Privileged Access Security Documentation. PADR.ini. In the section detailing the parameters of the padr.ini file

the EnableFailback parameter is described.

Reference: CyberArk Docs > Privileged Access Security v12.6 > Installation > CyberArk Digital Vault server > Disaster Recovery > PADR.ini

Quote/Paraphrase: The EnableFailback parameter determines whether the DR Vault will automatically fail back to the Primary Vault when it becomes available again. The default value is No. To enable automatic failback

this must be set to Yes.