VA-003 Explain encryption as a service Practice Question
A development team is building a microservices application that needs to encrypt sensitive customer data before storing it in a shared database. They want to minimize changes to their existing code and avoid managing encryption keys themselves. Which Vault feature should they use?
⚠ Common exam trap
A common mix-up: candidates confuse the Key Management Secrets Engine (KMSE) with encryption-as-a-service, but KMSE only distributes keys to external KMS providers and does not perform server-side encryption operations, which is the core requirement for minimizing code changes.
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
✓
Vault's Transit secrets engine
The Transit secrets engine is designed for encryption-as-a-service, allowing applications to encrypt data without exposing encryption keys to the application code. It performs encryption and decryption operations on the Vault server, so the development team can minimize code changes and avoid managing keys themselves.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Vault's Database secrets engine
Why it's wrong here
Database secrets engine generates short-lived database credentials, not encryption of stored values. It appeals because the data resides in a shared database, yet dynamic credential rotation addresses authentication, whereas the transit secrets engine performs encryption as a service.
- ✗
Vault's PKI secrets engine
Why it's wrong here
Vault's PKI secrets engine issues and revokes X.509 certificates, so it cannot encrypt application data at rest. It is tempting because it removes key management for TLS, and would be correct if the microservices needed mutual TLS certificates between services rather than encrypting customer records in a shared database.
- ✓
Vault's Transit secrets engine
Why this is correct
The transit secrets engine offers encryption as a service, so applications call Vault's API to encrypt and decrypt while Vault manages and protects the keys. This minimises code changes and removes the burden of key management, satisfying both stated constraints.
- ✗
Vault's Key Management Secrets Engine
Why it's wrong here
Key Management Secrets Engine distributes and manages keys across external KMS providers; it does not encrypt application data itself. It tempts because the stem mentions avoiding key management, but that engine targets cloud KMS key synchronisation, not transparent database encryption.
Go deeper
Related to this question
About these practice questions
Courseiva writes every VA-003 question from scratch — 366 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.