VA-003 Assess Vault tokens Practice Question
An application uses a Vault token with a policy that grants read access to secrets. The security team wants to ensure that if the application is compromised, the token cannot be used after a certain time even if the attacker has the token. What is the best approach?
⚠ Common exam trap
HashiCorp often tests the distinction between TTL and renewal behavior; the trap here is that candidates confuse 'max TTL' (which still allows renewal) with 'short TTL + no renewal' (which enforces absolute expiry), leading them to incorrectly select Option B.
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
✓
Set a short TTL on the token and do not allow renewal
Setting a short TTL on the token and disallowing renewal ensures that the token automatically expires after a fixed, short duration. Even if an attacker compromises the token, they cannot extend its lifetime, limiting the window of exposure. This directly meets the security requirement of preventing token use beyond a certain time without relying on external revocation mechanisms.
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 a revocation script that runs periodically
Why it's wrong here
A periodic revocation script leaves a window in which a stolen token remains valid until the next run, so it cannot guarantee expiry at a set time. It is tempting because it removes tokens, and would be correct for cleaning up orphaned tokens rather than enforcing a hard lifetime.
- ✗
Set explicit max TTL on the token
Why it's wrong here
Setting an explicit max TTL caps the token's total lifetime, but Vault still honours the token until that expiry, so a compromised token remains usable throughout the window. Max TTL suits bounding long-running batch jobs. The scenario requires immediate revocation on compromise, which token revocation or short TTLs with renewal achieve.
- ✗
Use a periodic token with a long period
Why it's wrong here
A periodic token renews indefinitely, so a stolen token stays valid as long as renewal succeeds, defeating the time limit. It suits long-running services needing continuous access. The scenario requires a bounded lifetime, which only a token with an explicit TTL and no renewal provides.
- ✓
Set a short TTL on the token and do not allow renewal
Why this is correct
A short TTL with renewal disabled forces Vault to revoke the token automatically once it expires, so a stolen token becomes useless after that window regardless of attacker possession. This directly satisfies the requirement that compromise cannot extend token usability.
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.