VA-003 Compare authentication methods Practice Question
An administrator wants to use Vault's authentication method that allows users to log in with their corporate credentials via a federated identity system. The credentials are stored in an external identity provider (IdP) and Vault should not store any passwords. Which authentication method should be configured?
⚠ Common exam trap
In HashiCorp Vault, the key distinction is between LDAP (direct authentication against an LDAP directory, where Vault validates credentials) and OIDC (federated authentication where an external IdP handles credential validation). Candidates often confuse LDAP with true federation, but LDAP still requires Vault to verify passwords, whereas OIDC delegates authentication entirely to the IdP.
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
✓
OIDC authentication
OIDC (OpenID Connect) authentication is the correct choice because it enables federated identity, allowing users to log in with corporate credentials managed by an external IdP (e.g., Microsoft Entra ID, Okta) without Vault storing any passwords. Vault acts as a relying party, delegating authentication to the IdP and receiving identity tokens, which aligns with the requirement for a passwordless, federated approach.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
LDAP authentication
Why it's wrong here
LDAP authentication validates credentials directly against a directory bind, requiring Vault to receive and check the password rather than delegating to a federated IdP. It tempts for corporate directory logins, but federation needs OIDC or JWT, where Vault trusts IdP-issued assertions.
- ✓
OIDC authentication
Why this is correct
OIDC authentication delegates login to an external identity provider via federated tokens, so Vault never stores or verifies passwords itself. This satisfies the stem's requirement that credentials reside in the IdP and Vault hold no passwords.
- ✗
Userpass authentication
Why it's wrong here
Userpass stores username and password pairs inside Vault's own backend, directly contradicting the requirement that Vault hold no passwords. It tempts as a simple built-in login, but federation requires OIDC or JWT, where the external IdP authenticates and Vault validates the signed assertion.
- ✗
Token authentication
Why it's wrong here
Token authentication issues Vault-generated tokens after an initial login; it performs no federated identity exchange with an external IdP. It tempts because tokens are the output of every auth method, but the requirement is authenticating corporate credentials via federation, which OIDC or JWT provides.
Go deeper
Related to this question
About these practice questions
Courseiva writes every VA-003 question from scratch — 366 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.