Compared to service tokens, batch tokens are ideal for what type of action?
A.
Generating dynamic credentials
B.
Renewing other tokens
C.
For daily batch jobs requesting secrets from Vault
D.
Short-lived, high-volume, or “ephemeral” tasks
The Answer Is:
D
This question includes an explanation.
Explanation:
Comprehensive and Detailed in Depth Explanation:
Batch tokens are designed for specific, transient use cases. The HashiCorp Vault documentation states: "Batch tokens are lightweight and scalable and include just enough information to be used with Vault. They are generally used for ephemeral, high-performance workloads, such as encrypting data." This makes them ideal forshort-lived, high-volume, or ‘ephemeral’ tasks (D).
The docs contrast: "Unlike service tokens, which are renewable and suited for long-lived processes, batch tokens have a fixed TTL and cannot be renewed." Options likegenerating dynamic credentials (A)anddaily batch jobs (C)align more with service tokens, whilerenewing tokens (B)isn’t a batch token function. Thus, D is correct.