The correct answer is to map the GitHub team to a Vault policy in the auth method configuration. This is because Vault’s GitHub authentication method does not natively enforce team membership directly; instead, it relies on team-to-policy mappings to grant access. When a user authenticates with a GitHub personal access token, Vault queries the GitHub API to identify which teams the user belongs to, then checks those teams against the configured mappings. Only if a user’s team is explicitly mapped to a Vault policy will they receive that policy’s permissions, effectively restricting access by team membership. On the HashiCorp Vault Associate VA-003 exam, this concept tests your understanding of how external identity providers integrate with Vault’s policy engine. A common trap is assuming you can restrict by individual user or repository—Vault only evaluates team membership for authorization. Remember the mnemonic: “Team to policy, not user to policy.”
VA-003 Compare authentication methods Practice Question
This VA-003 practice question tests your understanding of compare authentication methods. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 company uses Vault for secrets management. They want to authenticate using GitHub tokens, but only for users who are members of a specific GitHub team. What must be configured?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Map the GitHub team to a Vault policy in the auth method configuration.
Option D is correct because Vault's GitHub auth method requires mapping GitHub teams to Vault policies. When a user authenticates with a GitHub personal access token, Vault checks the token's associated teams against the configured team-to-policy mappings. Only users belonging to a mapped team receive the corresponding Vault policy, enabling access control based on team membership.
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.
✗
Vault validates the token's scope.
Why it's wrong here
Vault does not validate token scope.
✗
Users must generate a personal access token with repo scope.
Why it's wrong here
No specific scope is required beyond the ability to read team membership.
✗
The GitHub token must include the team scope.
Why it's wrong here
The token does not need a team scope; Vault uses the API to check membership.
✓
Map the GitHub team to a Vault policy in the auth method configuration.
Why this is correct
Mapping teams to policies is required to enforce membership.
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 Vault validates token scopes or that GitHub tokens have a 'team' scope, when in reality Vault relies on GitHub API team membership lookups and the token must have the appropriate OAuth scope (read:org) to retrieve that information.
Detailed technical explanation
How to think about this question
Under the hood, Vault's GitHub auth method uses the GitHub API endpoint /user/teams to retrieve the list of teams the authenticated user belongs to. Vault then compares these teams against the configured team-to-policy mappings in the auth method's configuration. A subtle behavior is that the token must have the 'read:org' OAuth scope (or be a personal access token with 'read:org' permission) to access team membership data; otherwise, Vault cannot determine the user's teams and authentication fails. In a real-world scenario, if a user has a token with only 'repo' scope, they can authenticate but will not be associated with any team, resulting in no policies being assigned.
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 practitioner preparing for the VA-003 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
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 authentication methods — This question tests Compare authentication methods — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Map the GitHub team to a Vault policy in the auth method configuration. — Option D is correct because Vault's GitHub auth method requires mapping GitHub teams to Vault policies. When a user authenticates with a GitHub personal access token, Vault checks the token's associated teams against the configured team-to-policy mappings. Only users belonging to a mapped team receive the corresponding Vault policy, enabling access control based on team membership.
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.
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 →
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.