VA-003 Compare authentication methods Practice Question
An organization uses Vault with LDAP authentication. Users report they are unable to log in, and the administrator sees errors like 'LDAP bind failed: invalid credentials' in the Vault logs. The LDAP server is reachable. What is the most likely cause?
⚠ Common exam trap
HashiCorp often tests the distinction between authentication failures (invalid credentials) and connectivity/TLS errors, so candidates mistakenly choose TLS or certificate issues when the error message clearly points to credential mismatch.
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 binddn or bindpass configured in Vault is incorrect
The error 'LDAP bind failed: invalid credentials' specifically indicates that the authentication attempt to the LDAP server using the configured binddn and bindpass failed. Since the LDAP server is reachable, the most direct cause is that the bind credentials stored in Vault's LDAP configuration do not match what the LDAP server expects. This is a configuration mismatch, not a connectivity or TLS issue.
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 binddn or bindpass configured in Vault is incorrect
Why this is correct
Vault performs an LDAP simple bind using the configured binddn and bindpass before searching for the user. If those service-account credentials are wrong or expired, the bind fails with 'invalid credentials' even though the LDAP server itself is reachable.
- ✗
Vault is not configured to use SSL/TLS for LDAP
Why it's wrong here
The bind error reports invalid credentials, so the failure occurs during authentication, not transport; missing SSL/TLS would surface as a connection or handshake error instead. Enabling LDAPS is the right step when the directory rejects plaintext binds or the environment mandates encrypted LDAP traffic.
- ✗
The LDAP server does not allow anonymous binds
Why it's wrong here
Vault performs the bind using the configured bind DN and password, so anonymous-bind restrictions do not produce an invalid-credentials error. Allowing anonymous binds matters when Vault is deliberately configured to search the directory without service-account credentials.
- ✗
The LDAP server certificate is not trusted by Vault
Why it's wrong here
An untrusted certificate causes TLS verification errors, not 'invalid credentials' bind failures. That message means the bind DN or password Vault uses is wrong, or the account is locked. Certificate trust would be the cause if Vault reported x509 verification failures instead.
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.