VA-003 Compare authentication methods Practice Question
A Vault administrator needs to allow users to authenticate using their existing corporate Active Directory credentials. The administrator has configured the LDAP authentication method but users cannot log in. The Vault logs show 'LDAP bind successful' but then 'user not found in group' error. What is the most likely issue?
⚠ Common exam trap
HashiCorp often tests the distinction between authentication (bind) and authorization (group lookup) — candidates mistakenly focus on the bind success and assume the issue is with user attributes or server connectivity, when the real problem lies in the group membership configuration.
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
✓
The groupfilter or groupattr configuration is incorrect
The error 'LDAP bind successful' confirms that the Vault server can connect and authenticate to the LDAP server using the bind credentials. The subsequent 'user not found in group' error indicates that while the user exists and can bind, the group membership lookup fails. This is most commonly caused by an incorrect `groupfilter` or `groupattr` configuration, which defines how Vault queries the LDAP directory to map users to groups for authorization.
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 LDAP server hostname is incorrect
Why it's wrong here
An incorrect hostname would prevent the TCP connection and LDAP bind entirely, contradicting the logged 'LDAP bind successful'. Correct hostname configuration is essential during initial setup, but once binds succeed the fault lies in group resolution, not connectivity.
- ✗
The userattr configuration is incorrect
Why it's wrong here
The userattr setting names the attribute Vault matches against the group membership, so a mismatch produces exactly this 'user not found in group' error after a successful bind. It is the right setting to check when group resolution fails, but here the stem's error points to group membership rather than the matching attribute.
- ✓
The groupfilter or groupattr configuration is incorrect
Why this is correct
A successful LDAP bind followed by 'user not found in group' means credentials validated but group membership resolution failed. Vault's groupfilter and groupattr settings control how groups are queried and mapped, so incorrect values there prevent the user matching any group.
- ✗
The LDAP server does not allow anonymous queries
Why it's wrong here
Anonymous query restrictions would cause the bind itself to fail, yet the logs show 'LDAP bind successful', so the server accepted the service account's credentials. Anonymous access is disabled in hardened directories by design; that setting matters when Vault must query without a bind DN, which is not this scenario.
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.