VA-003 Explain Vault architecture Practice Question
An operator notices that after a network partition, a Vault cluster with integrated storage (Raft) has a node that is unreachable and does not automatically rejoin. The cluster has 5 nodes with a minimum quorum of 3. What is a likely cause for the node not rejoining?
⚠ Common exam trap
HashiCorp often tests the misconception that a single node failure in a Raft cluster is automatically recoverable, but the trap here is that candidates overlook the quorum requirement and assume the node's own configuration or clock is at fault, rather than recognizing that the cluster may have lost majority due to multiple nodes being down.
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 cluster may have lost quorum due to other nodes also being down
In a Raft-based Vault cluster with 5 nodes and a quorum of 3, if a node becomes unreachable due to a network partition and does not automatically rejoin, the most likely cause is that additional nodes are also down or unreachable, causing the cluster to lose quorum. Without a majority of nodes (3 out of 5) able to communicate, the Raft consensus protocol cannot elect a leader or process log entries, so the isolated node cannot rejoin because the cluster itself is in a degraded state. The node not rejoining is a symptom of the broader quorum loss, not an isolated issue with that node.
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 node's raft index is ahead of the leader's
Why it's wrong here
Raft handles index differences via log replication; being ahead is unusual and not a typical cause.
- ✓
The cluster may have lost quorum due to other nodes also being down
Why this is correct
If 2 of 5 nodes are down, the remaining 3 constitute quorum; if more than 2 are down, quorum is lost.
- ✗
The node's clock skew is causing Raft timeouts
Why it's wrong here
Clock skew can cause issues but with default settings, it rarely prevents rejoining after partition.
- ✗
The node must be manually removed from the raft configuration and re-added
Why it's wrong here
If the node is temporarily unreachable, it should automatically rejoin when network is restored; removal is needed only if permanently dead.
Go deeper
Related to this question
About these practice questions
Courseiva writes every VA-003 question from scratch — 498 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.