HashiCorp Vault Associate (003) Question 220
Single answer8d Explain the uses of disaster recovery and performance replicationA company runs Vault Enterprise in a primary data center and serves applications from multiple geographic regions. Users in Europe report high latency during read-heavy operations such as token validation and secret reads, while security leadership also requires a warm standby environment that can be promoted if the primary data center becomes unavailable. Which replication design best meets both requirements?
- A
Configure performance replication for regional clusters to serve local read requests, and configure a disaster recovery secondary in the standby data center for failover promotion if the primary is lost.
- B
Configure only disaster recovery replication in each region, because disaster recovery secondaries can actively serve application traffic and also be promoted during an outage.
- C
Configure performance replication only, because performance secondaries can be promoted for disaster recovery and eliminate the need for a separate standby environment.
- D
Configure Vault Agent caching in each region instead of replication, because caching provides both cross-region failover and authoritative copies of Vault data.
Show answer and explanation
Correct answer: A
Explanation
The key distinction is purpose: performance replication is for scale and locality of access, especially in geographically distributed environments, while disaster recovery replication is for business continuity and failover. In real deployments, organizations often use performance replication to place secondary clusters near users or applications to reduce latency for read-heavy workloads, and separately use DR replication to maintain a warm standby cluster in another site or region. HashiCorp documentation describes performance replication as supporting horizontal scaling and local reads, while DR replication maintains a secondary that can be promoted if the primary cluster is unavailable. For this scenario, the only option that satisfies both the operational performance goal and the recovery requirement is to use both replication types for their intended purposes.
- A. Correct.
Correct. Performance replication is used to scale read traffic and reduce latency by placing performance secondary clusters closer to clients. Disaster recovery (DR) replication is used to maintain a warm standby copy of the Vault cluster that can be promoted if the primary cluster fails. This combination addresses both business needs: better regional read performance and an outage recovery strategy.
- B. Incorrect.
Incorrect. This reflects a common misconception. DR secondaries are not intended to serve normal application traffic the way performance secondaries do. Their purpose is to maintain a replicated standby cluster for recovery and promotion during a disaster event. Using only DR replication would not solve the read-scaling and low-latency regional access requirement.
- C. Incorrect.
Incorrect. Performance replication improves scale and locality for requests, but it is not the same as disaster recovery replication. Although performance replication supports replicated clusters, the exam objective distinguishes DR replication as the feature specifically used to maintain a recoverable standby environment for failover. Relying only on performance replication does not best satisfy the explicit requirement for a warm standby DR design.
- D. Incorrect.
Incorrect. Vault Agent caching can reduce repeated requests to Vault and improve application performance in some patterns, but it is not a replication mechanism. It does not create an authoritative standby cluster and cannot be promoted during a data center outage. This option confuses client-side optimization with server-side replication capabilities.