VA-003 Compare authentication methods Practice Question
A company has a Vault cluster and wants to allow applications running in Kubernetes pods to authenticate without storing static secrets. Which Vault authentication method is specifically designed for Kubernetes?
⚠ Common exam trap
HashiCorp often tests the distinction between 'designed for Kubernetes' (Kubernetes auth) and 'can be used with Kubernetes' (JWT/OIDC or AppRole), leading candidates to pick a generic method that works but is not purpose-built.
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
✓
Kubernetes
The Kubernetes auth method is specifically designed for Kubernetes workloads. It allows pods to authenticate to Vault using their Kubernetes service account token, which Vault validates against the Kubernetes API server. This eliminates the need to store static secrets in the cluster.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
AWS IAM
Why it's wrong here
AWS IAM auth validates AWS-signed STS identity, so it only works for workloads holding AWS credentials — not pods. It is the right choice when Vault clients run on EC2 or Lambda and present IAM roles, but Kubernetes pods without AWS identity cannot use it.
- ✓
Kubernetes
Why this is correct
The Kubernetes auth method validates a pod's service account JWT against the Kubernetes API, then returns a Vault token, so pods authenticate without any static secret stored in the container. This directly satisfies the stem's requirement for secretless pod authentication.
- ✗
JWT/OIDC
Why it's wrong here
JWT/OIDC validates externally issued tokens against configured claims, which is correct for generic CI or cloud identity providers. It fails here because the Kubernetes auth method natively verifies pod service account tokens via the TokenReview API, requiring no separate OIDC discovery or issuer configuration.
- ✗
AppRole
Why it's wrong here
AppRole suits machines or CI jobs authenticating with RoleID and SecretID, but those credentials are still stored secrets, defeating the stem's no-static-secrets requirement. The Kubernetes auth method instead validates each pod's service account token against the Kubernetes API, so no long-lived secret is persisted.
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.