VA-003 Compare and configure secrets engines Practice Question
An application needs to obtain short-lived, time-limited credentials to access an external database using username/password authentication. Which secrets engine should be used?
⚠ Common exam trap
HashiCorp often tests the distinction between static secret storage (KV) and dynamic secret generation (Database, AWS, etc.), so the trap here is assuming that any secrets engine can produce time-limited credentials, when only engines like Database, AWS, or PKI are designed for dynamic, lease-based credentials.
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
✓
Database secrets engine
The Database secrets engine is designed specifically to generate short-lived, dynamic credentials for databases, including external databases accessed via username/password authentication. It creates unique, time-limited usernames and passwords on-the-fly, which are automatically revoked after a configurable TTL, meeting the requirement for temporary credentials.
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 it's wrong here
KV v2 stores static secrets you write yourself; it cannot dynamically generate time-limited database credentials. It tempts because it is the default engine for holding passwords, which suits storing pre-existing static credentials rather than leasing short-lived ones.
- ✓
Database secrets engine
Why this is correct
The database secrets engine dynamically generates unique, short-lived database credentials on demand, then automatically revokes them at lease expiry. This directly satisfies the stem's requirement for time-limited credentials using username/password authentication against an external database, rather than issuing static long-lived passwords that persist until manually rotated.
- ✗
Consul secrets engine
Why it's wrong here
The Consul secrets engine mints Consul ACL tokens for service mesh access, not database username/password credentials. It tempts because it produces short-lived, dynamically generated tokens, which suits granting services access to Consul rather than to an external database.
- ✗
Identity secrets engine
Why it's wrong here
The identity secrets engine issues Vault tokens and entity metadata for authentication, not database credentials. It tempts because it manages identity and short-lived tokens, which suits workload identity federation scenarios rather than generating username/password pairs against an external database.
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.