VA-003 Explain Vault architecture Practice Question
A company uses Vault Enterprise with Performance Replication across two data centers. The primary data center is in us-east-1 and the secondary is in eu-west-1. They have an application that writes secrets to the primary cluster, and those secrets are replicated to the secondary cluster for read access. Recently, they noticed that some secrets written to the primary are not appearing on the secondary even after several minutes. The latency between data centers is typically 50ms. The administrator checks the replication status and sees a 'merkle sync' in progress. What is the most likely reason for the delay?
⚠ Common exam trap
Watch out — candidates often assume replication is always instant or that a merkle sync indicates a permanent failure, when in fact it is a normal recovery mechanism triggered by transient load or latency issues.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The secondary cluster is experiencing write load that is causing replication to fall behind.
Performance Replication in Vault Enterprise uses asynchronous streaming of write-ahead log (WAL) entries to replicate data to secondary clusters. When a 'merkle sync' is in progress, it indicates that the secondary cluster has fallen behind and is performing a full tree comparison to reconcile differences. The most likely cause is that the secondary cluster is under write load, which can cause it to process replication WAL streams more slowly, leading to a backlog and triggering a merkle sync to catch up.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The replication token has expired.
Why it's wrong here
Expired token would cause disconnection, not just lag.
- ✗
The primary cluster is using a different seal type than the secondary.
Why it's wrong here
Seal type does not affect replication.
- ✓
The secondary cluster is experiencing write load that is causing replication to fall behind.
Why this is correct
Heavy load can cause replication lag.
- ✗
Performance Replication only replicates data once per hour by default.
Why it's wrong here
Performance Replication is continuous.
Visual reference
Go deeper
Related to this question
About these practice questions
This VA-003 question is part of Courseiva's 498-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This VA-003 practice question is part of Courseiva's free HashiCorp certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the VA-003 exam.