You've set up multiple Vault clusters, one on-premises which is intended to be the primary cluster, and the second cluster in AWS, which was deployed to be used for performance replication. After enabling replication, developers complain that all the data they've stored in the AWS Vault cluster is missing. What happened?
- the data was moved to a recovery path after replication was enabled. Use the vault secrets move command to move the data back to its intended location
- there is a certificate mismatch after replication was enabled since Vault replication generates its own TLS certificates to ensure nodes are trusted entities
- the data was automatically copied to the primary cluster after replication was enabled since all writes are always forwarded to the primary cluster
- all of the data on the secondary cluster was deleted after replication was enabled
Answer(s): D
Explanation:
Replication relies on having a shared keyring between primary and secondaries and a shared understanding of the data store state.
As soon as replication is enabled, all of the secondary's existing data will be destroyed, which is irrevocable.
Generally, activating as a secondary will be the first thing that is done upon setting up a new cluster for replication.
Hence, create a backup first if there is a slight chance that you would need this existing storage in the future.
Reference:
https://www.hashicorp.com/resources/setting-up-configuring-performance- replication/