VA-003 Compare authentication methods Practice Question
An organization previously used userpass auth and is migrating to LDAP auth. After enabling LDAP and configuring the bind user, users can authenticate but their policies do not apply. What is the most likely cause?
⚠ Common exam trap
Candidates often assume successful authentication automatically grants permissions, but in Vault, authentication and authorization are decoupled — LDAP only verifies identity, and group-to-policy mapping is a separate configuration step that is easy to overlook.
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
✓
LDAP groups are not mapped to Vault policies
When users can authenticate but policies do not apply, it indicates that authentication itself is working (LDAP bind succeeded), but Vault has no way to associate the authenticated user with the correct policies. In Vault, LDAP authentication relies on group membership mapping: the LDAP server returns the user's groups, and Vault must have those groups mapped to Vault policies via `vault write auth/ldap/groups/<group_name> policies=<policy_name>`. Without this mapping, the user authenticates but receives no policies, resulting in an empty token with no permissions.
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 bind credentials are incorrect
Why it's wrong here
Incorrect bind credentials would cause the bind to fail, so authentication itself would break; here users authenticate, proving the bind works. It is tempting because bind misconfiguration is a frequent LDAP migration fault, and it would be correct if no users could authenticate.
- ✗
The userpass auth method is still enabled
Why it's wrong here
Leaving userpass enabled does not stop LDAP-authenticated users' policies applying; the mapping of LDAP identities to Vault entities and groups is what fails. It is tempting because overlapping auth methods do cause duplicate entities, a genuine issue when both backends serve the same users.
- ✓
LDAP groups are not mapped to Vault policies
Why this is correct
LDAP authentication resolves group membership from directory attributes, and Vault applies policies only when those groups are mapped via the groups parameter. Without that mapping, users authenticate successfully but receive only the default policy, so their intended policies never apply.
- ✗
The LDAP server is unreachable
Why it's wrong here
Unreachable LDAP would prevent authentication entirely, yet users authenticate successfully, so connectivity to the directory is proven. It is tempting because reachability is a common LDAP fault, and it would be the cause if binds timed out or no users could log in at all.
Go deeper
Related to this question
About these practice questions
One of 366 original VA-003 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.