Courseiva
Assess Vault tokenshardMultiple ChoiceObjective-mapped

Using Explicit Max TTL to Enforce Token Expiration

An administrator wants to ensure that a token created by a user cannot be used after 24 hours, even if the user tries to renew it. What should the administrator do?

Quick Answer

The correct answer is to set an explicit max TTL on the token to 24 hours. This works because the `explicit_max_ttl` parameter in Vault establishes a hard upper boundary on a token’s lifetime that cannot be overridden by any renewal attempts, even if the token’s default TTL or lease duration would otherwise allow extension. On the HashiCorp Vault Associate VA-003 exam, this concept tests your understanding of the difference between a token’s normal TTL (which can be renewed up to the max TTL) and the explicit max TTL (which is a non-renewable ceiling). A common trap is confusing the standard `max_ttl` with `explicit_max_ttl`—remember that only the explicit variant completely blocks renewal beyond its limit. For the exam, think of it as a “hard stop” that enforces token expiration regardless of user actions. Memory tip: “Explicit means exit—once the explicit max TTL is hit, the token exits for good.”

⚠ Common exam trap

Watch out — candidates often confuse TTL (time-to-live, which can be extended via renewal) with explicit max TTL (which sets a hard, non-renewable expiration), leading them to choose periodic or orphan tokens that allow indefinite renewal.

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 explicit max TTL on the token to 24h

Setting an explicit max TTL on the token to 24h ensures that the token's lifetime cannot be extended beyond 24 hours, even if the user attempts to renew it. In Vault, the `explicit_max_ttl` parameter overrides any renewal requests, enforcing a hard upper limit on the token's validity. This directly addresses the requirement that the token cannot be used after 24 hours, regardless of renewal attempts.

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 periodic token with a period of 24h

    Why it's wrong here

    Periodic tokens can be renewed before expiry, extending lifetime.

  • Create an orphan token with a TTL of 24h

    Why it's wrong here

    Orphan tokens can still be renewed if allowed.

  • Use a batch token

    Why it's wrong here

    Batch tokens are non-renewable but their TTL can be set; without explicit max TTL, they can still have a longer TTL.

  • Set explicit max TTL on the token to 24h

    Why this is correct

    Explicit max TTL cannot be exceeded by renewal.

About these practice questions

This VA-003 question is part of Courseiva's 498-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on VA-003

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. 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?

hard
  • A.Use a revocation script that runs periodically
  • B.Set explicit max TTL on the token
  • C.Use a periodic token with a long period
  • D.Set a short TTL on the token and do not allow renewal

Why D: 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.

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.