AnswerA, D
ExplanationComprehensive and Detailed in Depth
Vault tokens have two key time attributes: TTL (Time-To-Live) and Max TTL (Maximum Time-To-Live), governing their lifecycle. Let's dissect each option:
Option A: The TTL defines when the token will expire and be revoked
The TTL is the current lifespan of a token before it expires. For example, a token with a TTL of 24h (vault token create -ttl=24h) expires 24 hours from creation unless renewed. Upon expiry, Vault revokes it automatically. This is a fundamental property of TTL, making this statement accurate. Correct.
Vault Docs Insight: ''The TTL defines when the token will expire... if it reaches its TTL, it will be revoked by Vault.'' (Core definition.)
Option B: The TTL defines when another token will be generated
TTL governs expiration, not token generation. New tokens are created explicitly (e.g., vault token create) or via auth methods, not automatically by TTL. This misunderstands TTL's role---it's about expiry, not regeneration. Incorrect.
Vault Docs Insight: ''TTL is the duration until expiration... New tokens are not generated by TTL.'' (No generation link.)
Option C: The Max TTL defines the timeframe for which a token cannot be used
This is backwards. Max TTL sets the upper limit a token can exist through renewals, not a period of inactivity or unusability. A token with a Max TTL of 72h can be renewed up to 72 hours from creation, after which it's revoked. This option inverts the concept. Incorrect.
Vault Docs Insight: ''Max TTL defines the maximum timeframe for which the token can be renewed... not a usage restriction.'' (Opposite meaning.)
Option D: The Max TTL defines the maximum timeframe for which a token can be renewed
Max TTL caps the total lifespan of a token, including renewals. For example, a token with TTL=24h and Max TTL=72h (vault token create -ttl=24h -explicit-max-ttl=72h) can be renewed twice (24h + 24h + 24h = 72h) before hitting the limit. Beyond 72h, renewal fails, and it expires. This is the precise definition of Max TTL. Correct.
Vault Docs Insight: ''The Max TTL defines the maximum timeframe for which the token can be renewed... Once reached, it cannot be renewed further.'' (Exact match.)
Detailed Mechanics:
TTL is dynamic, decreasing as time passes (e.g., vault token lookup shows ttl: 23h59m50s after 10 seconds). Renewal (vault token renew) resets TTL to its original value (e.g., 24h), but only up to Max TTL from creation. System defaults (768h/32 days) apply unless overridden. Periodic tokens (-period=24h) renew indefinitely within their period, ignoring Max TTL unless explicitly set.
Real-World Example:
Create: vault token create -ttl=1h -explicit-max-ttl=3h. After 1h, TTL=0, renewable. Renew at 2h total, TTL=1h again. At 3h total, Max TTL hits---revoked. Contrast with TTL-only: vault token create -ttl=1h, renewable up to system Max TTL (768h).
Overall Explanation from Vault Docs:
''The TTL defines when the token will expire... If it reaches its TTL, it will be immediately revoked by Vault. The Max TTL defines the maximum timeframe for which the token can be renewed... Once the Max TTL is reached, the token cannot be renewed any longer and will be revoked.'' These attributes ensure controlled token lifecycles.
MENU
