VA-003 Utilize Vault CLI and API Practice Question
A user attempts to read a secret at path 'secret/data/app' and receives a 403 Forbidden error. What is the most likely cause?
⚠ Common exam trap
HashiCorp often tests the distinction between HTTP status codes in Vault: candidates confuse a 403 (policy denial) with a 404 (path not found) or assume an expired token always returns a 403, but the trap is that a 403 can also occur with a valid token lacking the correct policy, which is the most common scenario in practice.
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
✓
The token's policy does not grant read capability on that path
A 403 Forbidden error in Vault indicates that the token used for the request is valid and the path exists, but the token's attached policy does not grant the required 'read' capability on that specific path. This is a policy enforcement action by Vault's ACL system, which explicitly denies access when the policy lacks a matching 'read' rule for the path.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The secret engine is not mounted at 'secret/'
Why it's wrong here
If the KV engine were not mounted at 'secret/', the API would return a 404 or unsupported-path error, not 403 Forbidden. Unmounted paths are tempting because mount misconfiguration breaks access broadly, but that scenario yields path-not-found responses rather than an authorisation denial.
- ✗
The secret key does not exist
Why it's wrong here
A missing key returns 404 or an empty-data response after the path is authorised, not 403 Forbidden. Nonexistent keys are tempting because they block reads, but Vault evaluates the token's policy against the path first; denial happens before key existence is checked.
- ✗
The token has expired
Why it's wrong here
An expired token produces a 403 because Vault rejects the token before evaluating the path, but the stem gives no timing or TTL detail, so expiry is speculative. Expiry is the classic cause when a previously working token suddenly fails; here the path-based error points elsewhere.
- ✓
The token's policy does not grant read capability on that path
Why this is correct
Vault returns 403 when the token's attached policy lacks a read capability matching the requested path. Since 'secret/data/app' is the exact path being read, the absence of that capability in the policy is the direct cause of the forbidden response.
Visual reference
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.