This VA-003 practice question tests your understanding of assess vault tokens. 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 security team wants to enforce that all tokens created by a specific AppRole can only be used to read secrets from the path 'secret/data/team-a/*'. They have configured the AppRole with token_policies that include that path. However, a developer uses the token created from this AppRole to create a child token with broader policies, granting access to 'secret/data/team-b/*'. The security team wants to prevent such privilege escalation. Which action should be taken to ensure that child tokens cannot have broader policies than the parent?
Regularly audit and revoke tokens that violate policy
Why wrong: Reactive, not preventive.
B
Configure the AppRole's 'token_bound_cidrs' and 'token_policies' and set 'token_no_default_policy'? Actually none match. The nearest is to use the parent token's 'allowed_policies' metadata to restrict child token policies.
The parent token can set 'allowed_policies' to limit which policies child tokens can receive.
C
Use a root token to create all tokens and distribute them securely
Why wrong: Root tokens bypass policy restrictions, but this does not prevent escalation.
D
Set the parent token's 'orphan' property to 'true'
Why wrong: Orphan does not affect policy inheritance.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure the AppRole's 'token_bound_cidrs' and 'token_policies' and set 'token_no_default_policy'? Actually none match. The nearest is to use the parent token's 'allowed_policies' metadata to restrict child token policies.
Option D is correct. By setting 'token_bound_cidrs' or more relevantly, the parent token can have 'allowed_policies' that restrict child token policies. However, the correct mechanism is to set 'token_policies' on the AppRole and also set 'token_bound_policies' or use 'token_explicit_max_ttl'? Actually the best practice is to set the AppRole's 'token_policies' and also restrict child token creation by setting 'token_no_default_policy'? Wait, the question asks about child token policies. In Vault, when creating a child token, the parent's policies are inherited unless the parent has 'allowed_policies' set which limits the policies the child can have. If the parent does not set 'allowed_policies', the child can have any policies the creator has access to. To prevent this, set the parent's 'allowed_policies' to only include the desired policy. Option A is wrong because root tokens are not needed. Option B is wrong because setting 'orphan=true' does not affect policies. Option C is wrong because revoking tokens does not prevent future escalation. So the correct answer is to configure the parent token's 'allowed_policies' to restrict child token policies.
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Regularly audit and revoke tokens that violate policy
Why it's wrong here
Reactive, not preventive.
✓
Configure the AppRole's 'token_bound_cidrs' and 'token_policies' and set 'token_no_default_policy'? Actually none match. The nearest is to use the parent token's 'allowed_policies' metadata to restrict child token policies.
Why this is correct
The parent token can set 'allowed_policies' to limit which policies child tokens can receive.
Related concept
Authentication checks who the user is.
✗
Use a root token to create all tokens and distribute them securely
Why it's wrong here
Root tokens bypass policy restrictions, but this does not prevent escalation.
✗
Set the parent token's 'orphan' property to 'true'
Why it's wrong here
Orphan does not affect policy inheritance.
Common exam traps
Common exam trap: authentication is not authorization
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Detailed technical explanation
How to think about this question
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
KKey Concepts to Remember
Authentication checks who the user is.
Authorization controls what the user is allowed to do after login.
Privilege levels affect access to EXEC and configuration commands.
AAA, TACACS+ and RADIUS can separate login success from command access.
TExam Day Tips
→Do not assume successful login means full administrative access.
→Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
→Separate login problems from permission problems before choosing the answer.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
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.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related VA-003 questions on access control and AAA configuration.
Assess Vault tokens — This question tests Assess Vault tokens — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Configure the AppRole's 'token_bound_cidrs' and 'token_policies' and set 'token_no_default_policy'? Actually none match. The nearest is to use the parent token's 'allowed_policies' metadata to restrict child token policies. — Option D is correct. By setting 'token_bound_cidrs' or more relevantly, the parent token can have 'allowed_policies' that restrict child token policies. However, the correct mechanism is to set 'token_policies' on the AppRole and also set 'token_bound_policies' or use 'token_explicit_max_ttl'? Actually the best practice is to set the AppRole's 'token_policies' and also restrict child token creation by setting 'token_no_default_policy'? Wait, the question asks about child token policies. In Vault, when creating a child token, the parent's policies are inherited unless the parent has 'allowed_policies' set which limits the policies the child can have. If the parent does not set 'allowed_policies', the child can have any policies the creator has access to. To prevent this, set the parent's 'allowed_policies' to only include the desired policy. Option A is wrong because root tokens are not needed. Option B is wrong because setting 'orphan=true' does not affect policies. Option C is wrong because revoking tokens does not prevent future escalation. So the correct answer is to configure the parent token's 'allowed_policies' to restrict child token policies.
What should I do if I get this VA-003 question wrong?
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related VA-003 questions on access control and AAA configuration.
What is the key concept behind this question?
Authentication checks who the user is.
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 →
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.
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.