VA-003 Compare and configure secrets engines Practice Question
A company wants to securely store database credentials for a dynamic application that spins up new instances frequently. They need to ensure each instance gets a unique, time-limited username/password pair with minimal operational overhead. Which approach should they use?
⚠ Common exam trap
HashiCorp often tests the distinction between secrets engines that generate dynamic credentials (database secrets engine) versus those that manage static secrets (KV v2) or provide encryption (transit) or certificates (PKI), leading candidates to confuse the purpose of each engine.
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
✓
Enable the database secrets engine and configure role-based dynamic credential generation
The database secrets engine in HashiCorp Vault is designed specifically for dynamic credential generation, creating unique, time-limited username/password pairs on-demand for each instance. This approach minimizes operational overhead by automating credential lifecycle management, including automatic revocation after the TTL expires, which aligns perfectly with the requirement for frequently spinning up instances.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Enable the database secrets engine and configure role-based dynamic credential generation
Why this is correct
Configuring the database secrets engine with role-based dynamic credential generation lets Vault mint a unique username/password pair per instance on demand, each tied to a lease that expires automatically. This satisfies the frequent-instance, time-limited and minimal-overhead constraints, since no static credentials are stored or rotated manually.
- ✗
Use the transit secrets engine to encrypt the static credentials and distribute them
Why it's wrong here
The transit secrets engine performs cryptographic operations such as encryption and signing; it does not generate database credentials, so instances would still share static passwords. It is tempting when the goal is encrypting data in transit or at rest, where transit would be the correct engine.
- ✗
Use the PKI secrets engine to issue certificates for database authentication
Why it's wrong here
The PKI secrets engine issues X.509 certificates for TLS authentication, not database username/password pairs, so it cannot satisfy the unique time-limited credential requirement. It is tempting because it does provide dynamic, short-lived credentials, but for certificate-based identity rather than database logins.
- ✗
Store the credentials in KV v2 and have each instance read them
Why it's wrong here
KV v2 stores static secrets that every instance reads, so all instances share one long-lived credential with no automatic expiry or rotation. It is tempting for simple configuration secrets, where static storage is the correct choice, but it fails the unique time-limited requirement.
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.