VA-003 Explain Vault architecture Practice Question
A small startup wants to run Vault in a development environment with minimal operational overhead. They need to store secrets in memory only, without any persistence. Which storage backend should they choose?
⚠ Common exam trap
HashiCorp often tests the misconception that Integrated Storage (Raft) is the default or simplest backend, but candidates must recognize that Raft is persistent and requires cluster management, whereas the in-memory backend is the only option that guarantees zero persistence and minimal overhead.
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
✓
In-memory storage backend
The in-memory storage backend stores all data in RAM with no persistence to disk, making it ideal for development environments where secrets must be lost on restart and operational overhead must be minimized. It requires no configuration, no external dependencies, and no data management, perfectly matching the requirement for minimal overhead and memory-only storage.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Integrated Storage (Raft) backend
Why it's wrong here
Integrated Storage (Raft) persists secrets to disk and requires cluster quorum, directly contradicting the in-memory, no-persistence requirement. It is tempting because it removes external dependencies, which is the right choice for a production Vault cluster needing HA and durable data, but it cannot run purely in memory.
- ✓
In-memory storage backend
Why this is correct
The in-memory backend stores all secrets solely in RAM with no disk writes, so nothing persists across restarts. This matches the requirement for zero persistence and minimal operational overhead, making it ideal for ephemeral development environments.
- ✗
Consul storage backend
Why it's wrong here
Consul stores secrets on Consul's disk-backed KV store, so data persists and an external Consul cluster must be operated, contradicting both requirements. It is tempting because Consul provides HA and service discovery, which suits production Vault deployments, but it is not an in-memory backend.
- ✗
File storage backend
Why it's wrong here
The file backend writes secrets to a filesystem path, so data persists across restarts, contradicting the in-memory-only requirement. It is tempting because it needs no external service and is trivial to configure, which suits a single persistent dev server, but it cannot hold secrets solely in RAM.
Go deeper
Related to this question
About these practice questions
One of 366 original VA-003 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.