VAULT-ASSOCIATE-002 · Question #19
You are performing a high number of authentications in a short amount of time. You're experiencing slow throughput for token generation. How would you solve this problem?
The correct answer is B. Implement batch tokens. When facing slow throughput for token generation during high authentication rates, implementing batch tokens can significantly improve performance by reducing the number of costly root token operations.
Question
Options
- AIncrease the time-to-live on service tokens
- BImplement batch tokens
- CEstablish a rate limit quota
- DReduce the number of policies attached to the tokens
How the community answered
(26 responses)- A15% (4)
- B77% (20)
- C4% (1)
- D4% (1)
Why each option
When facing slow throughput for token generation during high authentication rates, implementing batch tokens can significantly improve performance by reducing the number of costly root token operations.
Increasing token TTLs would reduce the frequency of renewals, but not directly solve slow throughput for initial token *generation* during high authentication rates.
Batch tokens in Vault are designed for high-throughput, short-lived operations where individual token creation would otherwise strain the Vault server. They operate as internal tokens that bypass much of the normal token generation overhead, improving performance for high authentication volumes.
Establishing a rate limit quota would restrict the number of operations, which might alleviate strain but directly counters the goal of high authentication *throughput*.
Reducing the number of policies attached to tokens might slightly reduce the processing overhead, but it's not the primary solution for fundamental token generation throughput issues during high load, especially compared to batch tokens.
Concept tested: Vault token types, performance optimization, batch tokens
Source: https://developer.hashicorp.com/vault/docs/concepts/tokens#batch-tokens
Topics
Community Discussion
No community discussion yet for this question.