- A
The policy path is incorrect; KV v2 requires 'secret/data/engineering/*' for read access
For KV v2, data is under 'secret/data/'; the policy path must match the data path.
- B
The secret is stored in a different mount path
Why wrong: The path matches the mount; if moved, the policy would still need exact path.
- C
The policy is missing 'update' capability for the path
Why wrong: Read and list should be sufficient for reading the secret.
- D
The users are in a different namespace that doesn't inherit the policy
Why wrong: Namespaces can affect scope, but the question assumes no namespace.
VA-003 Explain Vault architecture Practice Question
This VA-003 practice question tests your understanding of explain vault architecture. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 Vault administrator creates a policy that grants 'read' and 'list' on 'secret/data/engineering/*' for a group. However, users in that group cannot read 'secret/data/engineering/project/db_password'. What is the most likely issue?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 policy path is incorrect; KV v2 requires 'secret/data/engineering/*' for read access
In Vault KV v2, secrets are accessed via a path that includes 'data' between the mount point and the secret name (e.g., 'secret/data/engineering/project/db_password'). The policy grants 'read' and 'list' on 'secret/data/engineering/*', which correctly covers the 'data' prefix. However, the user cannot read the secret because KV v2 also requires the 'read' capability on the 'metadata' path for the same secret (e.g., 'secret/metadata/engineering/project/db_password') to resolve version metadata. Without 'list' or 'read' on the metadata path, the read operation fails. The most likely issue is that the policy is missing the metadata path capability, but among the given options, A is correct because the policy path is incorrect—it should include both 'data' and 'metadata' paths for KV v2.
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.
- ✓
The policy path is incorrect; KV v2 requires 'secret/data/engineering/*' for read access
Why this is correct
For KV v2, data is under 'secret/data/'; the policy path must match the data path.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The secret is stored in a different mount path
Why it's wrong here
The path matches the mount; if moved, the policy would still need exact path.
- ✗
The policy is missing 'update' capability for the path
Why it's wrong here
Read and list should be sufficient for reading the secret.
- ✗
The users are in a different namespace that doesn't inherit the policy
Why it's wrong here
Namespaces can affect scope, but the question assumes no namespace.
Common exam traps
Common exam trap: answer the scenario, not the keyword
HashiCorp often tests the distinction between KV v1 and KV v2 path structures, specifically that KV v2 requires both 'data' and 'metadata' paths, and candidates mistakenly think granting 'read' on the data path alone is sufficient.
Detailed technical explanation
How to think about this question
KV v2 uses a two-path structure: the 'data' path for reading/writing secret data and the 'metadata' path for managing secret versions and metadata. A policy granting 'read' on 'secret/data/engineering/*' allows reading the secret data, but Vault's read operation for KV v2 also requires 'list' or 'read' on the corresponding 'secret/metadata/engineering/*' path to retrieve version information. In real-world scenarios, administrators often forget to grant capabilities on the metadata path, leading to 'permission denied' errors even when the data path is correctly configured.
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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
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 Vault architecture — study guide chapter
Learn the concepts, then practise the questions
- →
Explain Vault architecture 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 Vault architecture — This question tests Explain Vault architecture — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The policy path is incorrect; KV v2 requires 'secret/data/engineering/*' for read access — In Vault KV v2, secrets are accessed via a path that includes 'data' between the mount point and the secret name (e.g., 'secret/data/engineering/project/db_password'). The policy grants 'read' and 'list' on 'secret/data/engineering/*', which correctly covers the 'data' prefix. However, the user cannot read the secret because KV v2 also requires the 'read' capability on the 'metadata' path for the same secret (e.g., 'secret/metadata/engineering/project/db_password') to resolve version metadata. Without 'list' or 'read' on the metadata path, the read operation fails. The most likely issue is that the policy is missing the metadata path capability, but among the given options, A is correct because the policy path is incorrect—it should include both 'data' and 'metadata' paths for KV v2.
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.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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.