VA-003 Compare authentication methods Practice Question
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?
⚠ Common exam trap
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.
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
✓
Map the GitHub team to a Vault policy in the auth method configuration.
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.
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 authorise on token scope; it calls the GitHub API to list the user's teams and matches them against the auth method's configured team mapping. It tempts because scope-checking sounds like standard token validation, but team membership is the actual axis.
- ✗
Users must generate a personal access token with repo scope.
Why it's wrong here
The repo scope grants repository access and does not convey team membership; Vault's GitHub auth method reads team membership from the organisation via the token's read:org capability. It tempts because repo is the scope most developers already hold, yet it answers a different question.
- ✗
The GitHub token must include the team scope.
Why it's wrong here
GitHub tokens carry scopes such as repo or read:org, not a team scope; team membership is evaluated by Vault's GitHub auth method against the organisation's team mapping. It tempts because scoping sounds like the natural control, but no such token scope exists.
- ✓
Map the GitHub team to a Vault policy in the auth method configuration.
Why this is correct
Mapping the GitHub team to a Vault policy in the auth method configuration satisfies the team-membership constraint: Vault's GitHub auth method reads the user's team memberships from the GitHub API and assigns the mapped policy, so only members of that specific team receive the token's permissions.
Go deeper
Related to this question
About these practice questions
This VA-003 question is part of Courseiva's 366-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.