VA-003 Assess Vault tokens Practice Question
A DevOps team is using Vault tokens for authentication in CI/CD pipelines. They notice that tokens are often expired before the pipeline completes, causing failures. Which Vault feature should they use to address this without manual intervention?
⚠ Common exam trap
HashiCorp often tests the misconception that increasing TTL or using orphan tokens solves indefinite expiration, but the key is that periodic tokens are the only token type designed for renewable, long-lived use without a hard upper limit.
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
✓
Use periodic tokens with a short period and allow renewal
Periodic tokens are designed for long-running processes like CI/CD pipelines. They have no maximum TTL and can be renewed indefinitely as long as the renewal occurs before the current token's TTL expires. By using a periodic token with a short period and enabling automatic renewal in the pipeline, the token stays valid without manual intervention, solving the expiration 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.
- ✗
Use batch tokens for better performance
Why it's wrong here
Batch tokens are lightweight, non-renewable tokens with fixed lifetimes; they cannot be renewed, so expiry mid-pipeline persists. They are tempting because they reduce Vault storage and improve performance, and they would be correct for high-volume, short-lived, non-renewable workloads.
- ✓
Use periodic tokens with a short period and allow renewal
Why this is correct
Periodic tokens are exempt from the standard max TTL: they carry no absolute expiry and can be renewed indefinitely, provided each renewal occurs within the period. This satisfies the stem's requirement for unattended pipelines, where long-running jobs outlive fixed-TTL tokens and no operator is present to re-authenticate.
- ✗
Create orphan tokens so they don't expire with the parent
Why it's wrong here
Orphan tokens only remove the parent-child revocation link; they still carry their own TTL and expire on schedule, so pipelines still fail. They are tempting because orphan status sounds like exemption from expiry, and they would be correct when the goal is preventing parent revocation from cascading.
- ✗
Increase the default TTL on the token auth method
Why it's wrong here
Raising the auth method's default TTL only changes the initial lease; tokens still expire once that period elapses, so long pipelines fail again. It is tempting because TTL tuning is a legitimate Vault lever, and it would suffice if pipelines reliably finished inside a fixed window.
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.