Quick Answer
The KV v2 secrets engine is the correct choice because it is the only Vault secrets engine that supports versioning and rollback for static secrets. Unlike KV v1, which overwrites data without preserving history, KV v2 retains a configurable number of secret versions, enabling administrators to undelete or roll back to a previous state using the `vault kv rollback` command or API calls. On the HashiCorp Vault Associate VA-003 exam, this question tests your understanding of the core difference between KV v1 and KV v2, often appearing as a straightforward scenario where a team needs to store static secrets like API keys with versioning. A common trap is confusing KV v2 with dynamic secrets engines like AWS or PKI, which generate temporary credentials rather than versioning static data. Remember the memory tip: “KV v2 is the versioning vault for static secrets—rollback is its key feature.”
This VA-003 practice question tests your understanding of compare and configure secrets engines. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A security team wants to store static secrets like API keys in Vault. They need the secrets to be versioned and support rollback. Which secrets engine should they use?
Cubbyhole
Why wrong: Cubbyhole is a per-token private store, not for sharing static secrets.
KV v1
Why wrong: KV v1 does not support versioning or rollback.
Transit
Why wrong: Transit is an encryption engine, not for storing secrets.
KV v2
KV v2 supports versioning and rollback of secrets.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
KV v2
KV v2 is the correct choice because it is designed specifically for storing static secrets with built-in versioning and rollback capabilities. Unlike KV v1, which overwrites data without preserving history, KV v2 retains a configurable number of secret versions, allowing administrators to undelete or roll back to a previous version using the `vault kv rollback` command or API calls.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Cubbyhole
Why it's wrong here
Cubbyhole is a per-token private store, not for sharing static secrets.
KV v1
Why it's wrong here
KV v1 does not support versioning or rollback.
Transit
Why it's wrong here
Transit is an encryption engine, not for storing secrets.
KV v2
Why this is correct
KV v2 supports versioning and rollback of secrets.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
HashiCorp often tests the distinction between KV v1 and KV v2, trapping candidates who assume all KV engines support versioning, or who confuse the Transit engine's encryption capabilities with secret storage versioning.
Detailed technical explanation
Under the hood, KV v2 uses a metadata path (e.g., `secret/metadata/`) to track version numbers, creation timestamps, and deletion timestamps, while the actual secret data is stored under a data path (e.g., `secret/data/`). This separation allows operations like `vault kv undelete -versions=2 secret/mykey` to restore a specific version even after deletion, as long as it hasn't been permanently destroyed by the configured `delete_version_after` TTL. In real-world scenarios, this is critical for compliance requirements where audit trails and the ability to revert to a previous API key or credential are mandatory.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A practitioner preparing for the VA-003 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Compare and configure secrets engines — study guide chapter
Learn the concepts, then practise the questions
Compare and configure secrets engines practice questions
Targeted practice on this topic area only
All VA-003 questions
514 questions across all exam domains
HashiCorp Vault Associate VA-003 study guide
Full concept coverage aligned to exam objectives
VA-003 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise VA-003 questions linked to Compare authentication methods.
Practise VA-003 questions linked to Assess Vault tokens.
Practise VA-003 questions linked to Create Vault policies.
Practise VA-003 questions linked to Manage Vault leases.
Practise VA-003 questions linked to Compare and configure secrets engines.
Practise VA-003 questions linked to Utilize Vault CLI and API.
Practise VA-003 questions linked to Explain Vault architecture.
Practise VA-003 questions linked to Explain encryption as a service.
Practise VA-003 questions linked to VA-003 fundamentals.
Practise VA-003 questions linked to VA-003 scenario.
Practise VA-003 questions linked to VA-003 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Compare and configure secrets engines — This question tests Compare and configure secrets engines — Read the scenario before looking for a memorised answer..
The correct answer is: KV v2 — KV v2 is the correct choice because it is designed specifically for storing static secrets with built-in versioning and rollback capabilities. Unlike KV v1, which overwrites data without preserving history, KV v2 retains a configurable number of secret versions, allowing administrators to undelete or roll back to a previous version using the `vault kv rollback` command or API calls.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
Last reviewed: Jun 30, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.