VA-003 Compare and configure secrets engines Practice Question
Exhibit
$ vault read secret/metadata/myapp Key Value --- ----- cas_required true created_time 2023-01-01T00:00:00Z current_version 1 delete_version_after 0s max_versions 0 oldest_version 0 updated_time 2023-01-01T00:00:00Z
Refer to the exhibit. A user deletes the current version of 'secret/myapp' using 'vault kv delete secret/myapp'. What happens to the version?
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
✓
It is deleted and can be undeleted if not destroyed
With default delete_version_after=0s and max_versions=0, deleting a version marks it as deleted but does not destroy it. The version can be undeleted. The cas_required setting affects write operations, not delete. Permanent destruction requires a separate 'destroy' command or automatic cleanup if delete_version_after is set.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
It is destroyed because cas_required is true
Why it's wrong here
cas_required enforces check-and-set on writes, not deletion semantics; it has no bearing on what a delete does to a version. The tempting link is that both concern versioning, but cas_required governs write conflicts, whereas soft-delete behaviour is set by the KV v2 engine itself.
- ✓
It is deleted and can be undeleted if not destroyed
Why this is correct
A KV v2 delete marks the version as deleted by writing a deletion marker, removing it from reads. The underlying data remains, so the version can be undeleted unless it is destroyed or its metadata removed.
- ✗
It is permanently deleted immediately
Why it's wrong here
KV v2 delete marks the version as deleted rather than removing its data; the version remains recoverable via undelete. Permanent removal requires destroy or metadata deletion. It tempts because delete sounds final, but the v2 engine's soft-delete design deliberately separates deletion from destruction.
- ✗
It is marked as deleted but can be undeleted because cas_required is true
Why it's wrong here
The version is indeed soft-deleted and undeletable, but cas_required is not the reason; that setting only enforces check-and-set on writes. Undelete works because KV v2 retains version data. It tempts by pairing a true outcome with an unrelated configuration flag.
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.