VA-003 Assess Vault tokens Practice Question
A cloud-native application uses Vault's Kubernetes auth method to inject tokens into pods. Each pod receives a Vault token with a TTL of 1 hour, renewable. The application is designed to renew tokens before they expire. However, after a recent update, some pods are failing to authenticate with Vault, reporting 'token not found' errors. The operations team checks the Vault audit logs and sees that tokens associated with these pods are being revoked immediately after creation. The pods have not performed any revocation. What is the most likely cause?
⚠ Common exam trap
Hashicorp often tests the dependency between Kubernetes service account tokens and Vault-derived tokens, trapping candidates who assume the issue is with Vault's token configuration (TTL, batch, or renewal) rather than the upstream identity source.
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 Kubernetes service account that the pod uses has been deleted or its token has been invalidated, causing Vault to revoke derived tokens.
Vault's Kubernetes auth method creates a derived token that is tied to the Kubernetes service account token used during login. If the Kubernetes service account is deleted or its token is invalidated (e.g., due to rotation or expiration), Vault immediately revokes all derived tokens. The audit logs confirm revocation without pod action, and the TTL/renewal design points to an external dependency failure, not a Vault-side 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 Kubernetes auth method's 'kubernetes_ca_cert' has expired, causing Vault to invalidate all tokens.
Why it's wrong here
Incorrect: If the CA cert expired, new logins would fail, but existing tokens would not be immediately revoked.
- ✓
The Kubernetes service account that the pod uses has been deleted or its token has been invalidated, causing Vault to revoke derived tokens.
Why this is correct
Correct: Vault automatically revokes tokens when the underlying identity (service account) is removed or the JWT becomes invalid.
- ✗
The Vault tokens are being created as batch tokens and are immediately revoked due to a misconfiguration.
Why it's wrong here
Incorrect: Batch tokens are not automatically revoked upon creation; they have no lifetime management issues related to identity.
- ✗
The pods are attempting to renew tokens too frequently, exceeding a rate limit.
Why it's wrong here
Incorrect: Rate limits would cause errors but not immediate token revocation; also, the error is 'token not found', not rate limit.
Go deeper
Related to this question
About these practice questions
Courseiva writes every VA-003 question from scratch — 498 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.