HashiCorp Vault Associate (003) Question 222
Single answer8d Explain the uses of disaster recovery and performance replicationA global company runs Vault Enterprise in a primary datacenter in Virginia. Most applications write secrets and auth data to this cluster, but a large development team in Singapore experiences high latency when reading dynamic database credentials and KV secrets. The company also requires a standby environment in another region that can be promoted if the primary cluster becomes unavailable. Which solution best meets both requirements?
- A
Configure a performance replication secondary in Singapore for low-latency reads, and configure a disaster recovery secondary in another region for failover if the primary cluster is lost.
- B
Configure disaster recovery replication to Singapore so local applications can serve reads there, and configure a second disaster recovery secondary in another region for additional read scaling.
- C
Configure performance replication secondaries in both Singapore and the other region, because performance replication provides both read scaling and automatic disaster failover.
- D
Configure Vault Agent caches in Singapore for all secrets access, and use integrated storage snapshots in another region instead of disaster recovery replication.
Show answer and explanation
Correct answer: A
Explanation
The key distinction is purpose: performance replication is used to improve scale and reduce read latency for distributed clients, while disaster recovery replication is used to maintain a standby cluster that can be promoted after a primary failure. In real deployments, organizations often use both together: performance replication for regional access patterns and DR replication for business continuity. HashiCorp documentation and best practices describe performance replication as appropriate for serving client requests in remote locations, whereas DR replication is intended for recovery and promotion during outage scenarios rather than day-to-day traffic handling.
- A. Correct.
Correct. Performance replication is designed to improve read scalability and reduce latency for geographically distributed clients by allowing local reads on performance secondary clusters. Disaster recovery (DR) replication is intended to maintain a warm standby copy of the cluster's data so it can be promoted if the primary cluster fails. This combination directly matches the scenario: low-latency regional access plus a separate failover environment.
- B. Incorrect.
Incorrect. Disaster recovery secondaries are not used for general-purpose read scaling or routine client traffic. A DR secondary is a standby copy intended for failover, not for serving normal read workloads in a remote region. Someone might choose this if they confuse 'replica' with 'read replica,' but in Vault, that role belongs to performance replication.
- C. Incorrect.
Incorrect. Performance replication helps with read scaling and regional access, but it does not replace disaster recovery replication for maintaining a designated failover cluster. A performance secondary is not the same as a DR secondary, and this option overstates performance replication by implying it covers disaster recovery needs by itself.
- D. Incorrect.
Incorrect. Vault Agent caching can reduce some repeated secret fetches, but it is not a substitute for performance replication when applications need broad, low-latency access to Vault data and services across regions. Integrated storage snapshots may help with backup and recovery processes, but snapshots are not equivalent to a continuously replicated DR secondary that can be promoted during an outage.