HashiCorp Vault Associate (003) Question 224
Single answer8d Explain the uses of disaster recovery and performance replicationA company runs a Vault Enterprise cluster in us-east-1 as its primary deployment. Most application writes occur there, but teams in Europe report high latency when reading secrets and authenticating. The company also needs a standby environment in another region that can be promoted if the primary region becomes unavailable. Which replication design best meets both requirements?
- A
Configure a performance secondary in Europe to serve local read and auth traffic, and configure a disaster recovery secondary in another region for failover promotion if the primary cluster is lost.
- B
Configure only a disaster recovery secondary in Europe, because DR replication is intended to reduce read latency for geographically distant users while also providing failover.
- C
Configure two performance secondaries, one in Europe and one in another region, because performance replication alone provides the recommended failover mechanism for regional outages.
- D
Configure Vault Agent caches in Europe and avoid replication, because replication is only needed when multiple primary clusters must accept writes simultaneously.
Show answer and explanation
Correct answer: A
Explanation
In Vault Enterprise, performance replication and disaster recovery replication serve different operational goals. Performance replication is used to improve horizontal scale and reduce latency for distributed users by placing secondary clusters closer to consumers of Vault services. Disaster recovery replication is used to maintain a secondary cluster that can be promoted if the primary cluster becomes unavailable. In this scenario, the company has two separate needs: better regional performance for Europe and a recoverable standby in another region. The best-practice design is therefore to use a performance secondary for the Europe latency issue and a DR secondary for failover. This aligns with HashiCorp Vault documentation describing performance replication for scaling/read locality and DR replication for standby recovery and promotion.
- A. Correct.
Correct. Performance replication is used to scale read-heavy workloads and reduce latency for clients in other regions by allowing local handling of reads and many client interactions such as authentication requests. Disaster recovery replication is intended to maintain a warm standby copy of the cluster state that can be promoted if the primary cluster fails. This combination directly addresses both the low-latency access requirement and the regional failover requirement.
- B. Incorrect.
Incorrect. Disaster recovery replication is primarily for business continuity and failover, not for serving day-to-day low-latency read traffic in remote regions. A DR secondary is not the right tool to offload normal read/auth workloads for geographically distributed users. This option reflects a common misconception that DR replication is a general-purpose read scaling feature.
- C. Incorrect.
Incorrect. Performance replication helps distribute read traffic and improve regional access, but it is not the recommended substitute for disaster recovery failover planning. A performance secondary is not the same as a DR secondary for recovery use cases. Choosing only performance secondaries leaves the design misaligned with the explicit requirement for a standby environment intended for promotion after loss of the primary region.
- D. Incorrect.
Incorrect. Vault Agent caching can reduce some client-side latency and load, but it does not replace replication for cross-region availability or failover. It also does not create a promotable standby copy of the Vault cluster. The statement that replication is only needed for multiple writable primaries is false; Vault replication is specifically used for read scaling and disaster recovery scenarios.