VAULT-ASSOCIATE practice question 4 of 15

Which of the following cannot define the maximum time-to-live (TTL) for a token?

Full set: 57 questions
Answer options
A: By the authentication method t natively provide a method of expiring credentials
B: By the client system f credentials leaking Correct answer
C: By the mount endpoint configuration very password used
D: A parent token TTL e password rotation tools and practices
E: System max TTL
Correct Answer:
B. By the client system f credentials leaking
Explanation

A token's maximum Time-To-Live (TTL) is a configurable property within Vault, determined by a hierarchy of settings. These settings include the system-wide maximum TTL, the auth mount's maximum TTL, the specific role's configuration within an auth method, and the TTL of a parent token (for child tokens). A credential leak on a client system is a security event that the TTL mechanism is designed to mitigate; however, the event itself does not and cannot define the TTL value of a token. The TTL is a proactive configuration, not a reactive state determined by an external system's compromise.

Why Incorrect

A. By the authentication method...: Auth method roles (e.g., an AppRole role) can be configured with a tokenmaxttl that explicitly sets the maximum lifetime for tokens issued for that role.
C. By the mount endpoint configuration...: Each authentication method mount point can be tuned with its own maxleasettl, which overrides the system default for all tokens generated from that specific mount.
D. A parent token TTL...: A child token's lifetime is always capped by its parent's remaining TTL. It cannot exist longer than the token that created it.
E. System max TTL: Vault has a global maxleasettl configuration setting that establishes an absolute maximum lifetime for all tokens and leases across the entire system.

References

1. HashiCorp Vault Official Documentation, "Tokens - Token Time-To-Live (TTL)": This document explains the hierarchy of TTLs. It states, "The TTL of a token is determined by a number of factors: the system setting, the auth mount's setting, and the role's setting... The TTL of a child token is capped by the parent token's TTL." This supports the validity of options A, C, D, and E as mechanisms for defining TTL.

2. HashiCorp Vault Official Documentation, "Configuration - maxleasettl": This section details the system-wide configuration. "This is a system-level setting that is used to ensure leases are revoked in a reasonable amount of time." This confirms option E.

3. HashiCorp Vault Official Documentation, "System Backend (API) - Tune Auth Mount": The API documentation for the /sys/auth/:path/tune endpoint shows the maxleasettl parameter, described as "a mount-specific override of the global maxleasettl." This confirms option C.

4. HashiCorp Vault Official Documentation, "Token Auth Method (API) - Create Role": The API documentation for creating a token role includes the tokenmaxttl parameter, which specifies "The maximum lifetime of the token" for that role. This principle applies to roles in other auth methods and confirms option A.

Scroll to Top