VA-003 Utilize Vault CLI and API Practice Question
Exhibit
Refer to the exhibit.
path "secret/data/team/*" {
capabilities = ["create", "update", "read"]
}A user with this policy wants to delete secrets under the 'team/' path. Which additional capability must be added?
⚠ Common exam trap
HashiCorp often tests the misconception that 'sudo' is a catch-all permission or that 'update' implies delete capability, but in Vault, each operation is explicitly scoped and 'delete' must be granted separately.
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
✓
delete
The user's policy grants 'create' and 'update' capabilities on 'team/*', but not 'delete'. In Vault's ACL policy system, each operation (create, read, update, delete, list, sudo) must be explicitly allowed. Since 'delete' is missing, the user cannot delete secrets under 'team/'. Adding the 'delete' capability to the policy is required.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
sudo
Why it's wrong here
The 'sudo' capability bypasses root-protected API endpoints; it grants no permission to delete data. It is tempting because it sounds like an elevated privilege, but deletion requires 'delete' on the team/ path, which sudo does not confer.
- ✓
delete
Why this is correct
Granting the delete capability on the 'team/' path lets the user remove secrets there, satisfying the stem's requirement. Vault policies are path-scoped, so read and list permissions alone cannot authorise destruction; the delete capability must be explicitly added to that path's policy stanza.
- ✗
list
Why it's wrong here
'list' permits enumerating keys under a path, not removing them. It is tempting because listing team/ is a natural precursor to deleting, but the delete operation itself needs the 'delete' capability on the team/ path.
- ✗
patch
Why it's wrong here
'patch' permits partial updates to existing data at a path, not removal of secrets. It is tempting because patch is a write-style capability, but deleting keys under team/ requires the 'delete' capability, which patch does not supply.
Visual reference
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.