- A
Use Vault's batch encryption
Why wrong: Batch encryption is for multiple small payloads, not for large files.
- B
Use Vault's seal-wrapping feature
Why wrong: Seal-wrapping is for encrypting Vault data at rest, not for application data encryption.
- C
Use Vault's datakey endpoint to get a data encryption key, encrypt locally, then wrap with Vault
Envelope encryption: the data key is used locally and its ciphertext is stored alongside the encrypted file.
- D
Encrypt the file directly with Vault's transit encrypt API
Why wrong: Sending several GB through the API is inefficient and may hit size limits.
- E
Split the file into chunks and encrypt each chunk via transit
Why wrong: Still involves excessive API calls and network overhead.
VA-003 Explain encryption as a service Practice Question
This VA-003 practice question tests your understanding of explain encryption as a service. 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 DevOps team needs to encrypt large files (several GB) using Vault's transit engine. What is the recommended approach?
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
Use Vault's datakey endpoint to get a data encryption key, encrypt locally, then wrap with Vault
The transit engine is designed for encrypting small data payloads (typically a few KB), not multi-GB files. The recommended approach is to use the `/transit/datakey/plaintext` endpoint to generate a data encryption key (DEK), encrypt the large file locally with that DEK using a symmetric algorithm like AES-256-GCM, and then wrap (encrypt) the DEK with Vault using the transit engine. This keeps the large file out of Vault while still leveraging Vault for key management and audit logging.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use Vault's batch encryption
Why it's wrong here
Batch encryption is for multiple small payloads, not for large files.
- ✗
Use Vault's seal-wrapping feature
Why it's wrong here
Seal-wrapping is for encrypting Vault data at rest, not for application data encryption.
- ✓
Use Vault's datakey endpoint to get a data encryption key, encrypt locally, then wrap with Vault
Why this is correct
Envelope encryption: the data key is used locally and its ciphertext is stored alongside the encrypted file.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Encrypt the file directly with Vault's transit encrypt API
Why it's wrong here
Sending several GB through the API is inefficient and may hit size limits.
- ✗
Split the file into chunks and encrypt each chunk via transit
Why it's wrong here
Still involves excessive API calls and network overhead.
Common exam traps
Common exam trap: answer the scenario, not the keyword
HashiCorp often tests the misconception that Vault's transit engine can handle large payloads directly, leading candidates to choose Option D, but the actual limitation is that transit encrypt/decrypt operations are designed for small data (e.g., database fields, tokens) and envelope encryption is required for large files.
Detailed technical explanation
How to think about this question
Under the hood, the `/transit/datakey/plaintext` endpoint returns a plaintext DEK (e.g., a 256-bit key) and a ciphertext version of that DEK wrapped by Vault's key encryption key (KEK). The client uses the plaintext DEK to encrypt the file locally with AES-256-GCM, then discards the plaintext DEK and stores only the wrapped DEK alongside the encrypted file. For decryption, the client sends the wrapped DEK to Vault's `/transit/decrypt` endpoint to retrieve the plaintext DEK, then decrypts the file locally. This pattern is known as envelope encryption and is standard in cloud KMS services (e.g., AWS KMS, GCP Cloud KMS).
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
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
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Explain encryption as a service — study guide chapter
Learn the concepts, then practise the questions
- →
Explain encryption as a service 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
Related VA-003 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Compare authentication methods practice questions
Practise VA-003 questions linked to Compare authentication methods.
Assess Vault tokens practice questions
Practise VA-003 questions linked to Assess Vault tokens.
Create Vault policies practice questions
Practise VA-003 questions linked to Create Vault policies.
Manage Vault leases practice questions
Practise VA-003 questions linked to Manage Vault leases.
Compare and configure secrets engines practice questions
Practise VA-003 questions linked to Compare and configure secrets engines.
Utilize Vault CLI and API practice questions
Practise VA-003 questions linked to Utilize Vault CLI and API.
Explain Vault architecture practice questions
Practise VA-003 questions linked to Explain Vault architecture.
Explain encryption as a service practice questions
Practise VA-003 questions linked to Explain encryption as a service.
VA-003 fundamentals practice questions
Practise VA-003 questions linked to VA-003 fundamentals.
VA-003 scenario practice questions
Practise VA-003 questions linked to VA-003 scenario.
VA-003 troubleshooting practice questions
Practise VA-003 questions linked to VA-003 troubleshooting.
Practice this exam
Start a free VA-003 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this VA-003 question test?
Explain encryption as a service — This question tests Explain encryption as a service — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use Vault's datakey endpoint to get a data encryption key, encrypt locally, then wrap with Vault — The transit engine is designed for encrypting small data payloads (typically a few KB), not multi-GB files. The recommended approach is to use the `/transit/datakey/plaintext` endpoint to generate a data encryption key (DEK), encrypt the large file locally with that DEK using a symmetric algorithm like AES-256-GCM, and then wrap (encrypt) the DEK with Vault using the transit engine. This keeps the large file out of Vault while still leveraging Vault for key management and audit logging.
What should I do if I get this VA-003 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
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 →
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.