- A
Configure the Kubernetes auth role to use 'token_policies' with a restrictive policy and ensure the bound service account names are correct.
Why wrong: This is already assumed to be done; the issue is the policy content, not the binding.
- B
Create a new secrets engine for each team and mount them at 'team-alpha' and 'team-beta', then assign each service to its respective engine.
Why wrong: While this would work, it is overkill and not necessary; policy restrictions on the existing engine are sufficient.
- C
Add a 'path_deny' capability in the policy for the disallowed paths.
Why wrong: Vault policies use 'deny' as a capability only in Sentinel policies, not in standard ACL policies; the correct approach is to simply not grant access.
- D
Review and update the policy attached to the Kubernetes auth roles to restrict capabilities to the specific paths, e.g., 'path "shared-kv/data/team-alpha/*" { capabilities = ["read"] }'.
This directly restricts each service to its allowed paths using Vault's policy language.
Quick Answer
The correct answer is to update the policy attached to the Kubernetes auth roles to restrict capabilities to specific paths like `shared-kv/data/team-alpha/*`. This is necessary because KV v2 engines require the `data/` prefix in the path to access secret data, and the current policy grants overly broad read access to the entire `shared-kv/*` path, violating least privilege. On the HashiCorp Vault Associate VA-003 exam, this scenario tests your understanding of how Kubernetes auth roles bind service accounts to policies, and the common trap is forgetting the `data/` prefix for KV v2 secrets—candidates often write `shared-kv/team-alpha/*` instead of the correct `shared-kv/data/team-alpha/*`. A reliable memory tip: for KV v2, always insert `data/` between the mount path and the secret path when writing policies, as Vault treats the metadata and data as separate sub-paths.
VA-003 Compare and configure secrets engines Practice Question
This VA-003 practice question tests your understanding of compare and configure secrets engines. 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 financial services company runs a microservices application on Kubernetes. Each service needs to authenticate to Vault using Kubernetes auth and then read secrets from a shared KV v2 engine mounted at 'shared-kv'. The security team requires that Service-A can only read secrets under 'shared-kv/team-alpha/*' and Service-B can only read secrets under 'shared-kv/team-beta/*'. The Vault administrator has already configured the Kubernetes auth method and created roles for each service with bound service account names. However, both services are currently able to read all paths under 'shared-kv/'. The administrator wants to enforce the least privilege access. Which course of action should the administrator take?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"least"Why it matters: You want the option with minimum overhead, fewest steps, or lowest impact — not the most feature-rich or comprehensive answer.
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
Review and update the policy attached to the Kubernetes auth roles to restrict capabilities to the specific paths, e.g., 'path "shared-kv/data/team-alpha/*" { capabilities = ["read"] }'.
Option D is correct because the issue is that the policy attached to the Kubernetes auth roles grants read access to the entire 'shared-kv/*' path. By updating the policy to restrict capabilities to specific paths like 'shared-kv/data/team-alpha/*' and 'shared-kv/data/team-beta/*', the administrator enforces least privilege. The 'data' prefix is required for KV v2 engines to access secret data, and the wildcard ensures only the respective team's secrets are readable.
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.
- ✗
Configure the Kubernetes auth role to use 'token_policies' with a restrictive policy and ensure the bound service account names are correct.
Why it's wrong here
This is already assumed to be done; the issue is the policy content, not the binding.
- ✗
Create a new secrets engine for each team and mount them at 'team-alpha' and 'team-beta', then assign each service to its respective engine.
Why it's wrong here
While this would work, it is overkill and not necessary; policy restrictions on the existing engine are sufficient.
- ✗
Add a 'path_deny' capability in the policy for the disallowed paths.
Why it's wrong here
Vault policies use 'deny' as a capability only in Sentinel policies, not in standard ACL policies; the correct approach is to simply not grant access.
- ✓
Review and update the policy attached to the Kubernetes auth roles to restrict capabilities to the specific paths, e.g., 'path "shared-kv/data/team-alpha/*" { capabilities = ["read"] }'.
Why this is correct
This directly restricts each service to its allowed paths using Vault's policy language.
Clue confirmation
The clue word "least" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
HashiCorp often tests the misconception that 'path_deny' is a valid capability in Vault ACL policies, when in fact Vault uses default-deny and explicit allow, so candidates incorrectly choose Option C instead of updating the allowed paths.
Detailed technical explanation
How to think about this question
In Vault's KV v2 engine, secrets are accessed under the 'data/' sub-path (e.g., 'shared-kv/data/team-alpha/secret'), while metadata is under 'metadata/'. Policies must explicitly include the 'data/' prefix for read operations. Additionally, Vault policies are additive and deny by default, so granting access to 'shared-kv/*' inadvertently allows all sub-paths. A common real-world scenario is when teams share a KV engine but need isolated access; using path-based policies with specific prefixes is the standard pattern.
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.
- →
Compare and configure secrets engines — study guide chapter
Learn the concepts, then practise the questions
- →
Compare and configure secrets engines 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?
Compare and configure secrets engines — This question tests Compare and configure secrets engines — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Review and update the policy attached to the Kubernetes auth roles to restrict capabilities to the specific paths, e.g., 'path "shared-kv/data/team-alpha/*" { capabilities = ["read"] }'. — Option D is correct because the issue is that the policy attached to the Kubernetes auth roles grants read access to the entire 'shared-kv/*' path. By updating the policy to restrict capabilities to specific paths like 'shared-kv/data/team-alpha/*' and 'shared-kv/data/team-beta/*', the administrator enforces least privilege. The 'data' prefix is required for KV v2 engines to access secret data, and the wildcard ensures only the respective team's secrets are readable.
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: "least". You want the option with minimum overhead, fewest steps, or lowest impact — not the most feature-rich or comprehensive answer.
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.