VA-003 Compare and configure secrets engines Practice Question
After migrating from an older version of Vault, the operator wants to replace the deprecated 'generic' secrets engine with a modern alternative. Which secrets engine should be used to store static key-value pairs?
⚠ Common exam trap
HashiCorp often tests the misconception that the 'generic' secrets engine is still valid or that any secrets engine can store static key-value pairs, leading candidates to overlook the specific deprecation and the KV v2 replacement.
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
✓
KV v2 secrets engine
The KV v2 secrets engine is the modern replacement for the deprecated 'generic' secrets engine in Vault. It stores static key-value pairs with added features such as versioning, configurable delete and destroy behaviors, and check-and-set operations, making it the correct choice for this use case.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
KV v2 secrets engine
Why this is correct
KV v2 stores static key-value pairs and replaces the deprecated generic engine, satisfying the migration constraint. It adds versioning, metadata and soft-delete, letting the operator retain prior secret versions and recover deleted data. Enable it at a chosen path, then migrate existing generic secrets into it.
- ✗
AWS secrets engine
Why it's wrong here
The AWS secrets engine dynamically generates AWS IAM credentials and leases; it stores no static key-value pairs. It is tempting because it modernises cloud credential handling, and it would be correct when workloads need short-lived AWS access keys rather than static secrets.
- ✗
Database secrets engine
Why it's wrong here
The database secrets engine dynamically generates short-lived database credentials on demand; it does not store static key-value pairs. It is tempting because it is a modern replacement for static credentials, and it would be correct when applications need dynamically generated database logins instead of stored secrets.
- ✗
Transit secrets engine
Why it's wrong here
Transit performs encryption-as-a-service, encrypting and decrypting data in transit without persisting it; it cannot store static key-value pairs. It is tempting because Transit is a modern engine often adopted during migrations, and it would be correct for centralised cryptographic operations rather than secret storage.
Go deeper
Related to this question
About these practice questions
This VA-003 question is part of Courseiva's 366-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.