VAULT-ASSOCIATE-002 · Question #102
Which is not true of Vault tokens?
The correct answer is D. Vault tokens are required for every Vault call. It is not true that Vault tokens are required for absolutely every Vault call, as some operational commands and health checks do not necessitate a token for execution.
Question
Options
- AVault tokens are the core method for authentication in Vault
- BVault tokens are generated by every authentication method login
- CVault tokens map to information including polices the token holder has, TTL and max usage,
- DVault tokens are required for every Vault call
How the community answered
(48 responses)- A2% (1)
- B6% (3)
- C2% (1)
- D90% (43)
Why each option
It is not true that Vault tokens are required for absolutely every Vault call, as some operational commands and health checks do not necessitate a token for execution.
Vault tokens are indeed the core method for authentication in Vault, serving as the primary identity for clients and applications interacting with the system.
Every successful authentication method login in Vault, whether via AppRole, Kubernetes, LDAP, or userpass, generates a Vault token for the authenticated entity to use for subsequent API calls.
Vault tokens map to comprehensive information including the policies that define the token holder's access, its time-to-live (TTL), maximum usage limits, and other metadata important for its lifecycle and capabilities.
False. While Vault tokens are the core method for authenticating most API and CLI operations that access secrets or policies, certain operational commands like `vault status`, `vault operator init`, and `vault operator unseal` do not require an authenticated token to be present.
Concept tested: Vault token characteristics and usage
Source: https://developer.hashicorp.com/vault/docs/concepts/tokens#token-details
Topics
Community Discussion
No community discussion yet for this question.