VA-003 Assess Vault tokens Practice Question
Your company uses Vault to manage secrets for a fleet of microservices running on Kubernetes. Each microservice has a service account that authenticates to Vault using the Kubernetes auth method and receives a token with a policy granting access to its secrets. Recently, the team noticed that some tokens are being revoked prematurely, causing services to lose access to secrets. The tokens are created with a TTL of 24 hours and are set to be renewable. The Vault servers are configured with a default max_ttl of 24 hours. The tokens are renewed by the client libraries every 12 hours. Despite this, tokens are sometimes invalid before 24 hours. What should the team do to prevent this issue?
⚠ Common exam trap
HashiCorp often tests the distinction between TTL and max_ttl, and the trap here is that candidates assume renewing a token resets its entire lifetime, not realizing that max_ttl imposes a hard cap on total token duration.
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
✓
Increase the max_ttl on the token role to 48 hours to allow renewal beyond 24 hours.
The tokens are being revoked prematurely due to the Vault server's default max_ttl of 24 hours. Even though the token TTL is 24 hours and the client renews every 12 hours, the max_ttl caps the total lifetime of the token, including renewals. By increasing the max_ttl on the token role to 48 hours, the token can be renewed beyond the initial 24-hour window, preventing premature invalidation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set the token's num_uses to a high number to prevent premature revocation.
Why it's wrong here
num_uses limits the number of uses, not the lifetime; it does not address the TTL issue.
- ✗
Change the tokens to periodic tokens so they never expire.
Why it's wrong here
Periodic tokens are not appropriate for microservices that need short-lived tokens; they also have a max_ttl.
- ✗
Decrease the token TTL to 12 hours so that renewal happens before the max_ttl is reached.
Why it's wrong here
Decreasing TTL would cause tokens to expire sooner, not solve the problem.
- ✓
Increase the max_ttl on the token role to 48 hours to allow renewal beyond 24 hours.
Why this is correct
By increasing max_ttl, tokens can be renewed and remain valid for a longer period, preventing premature expiration.
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.