VAULT-ASSOCIATE-002 · Question #38
What is a secret in the context of Vault?
The correct answer is C. Anything stored or returned that contains confidential material. In the context of Vault, a secret is broadly defined as any sensitive information, whether stored persistently or dynamically generated and returned, that requires secure management.
Question
Options
- AHTTP session token that provides authorization to Vault
- BThreshold of keys required to unseal the Vault
- CAnything stored or returned that contains confidential material
- DEngine responsible for logging all requests and responses
How the community answered
(38 responses)- B3% (1)
- C92% (35)
- D5% (2)
Why each option
In the context of Vault, a secret is broadly defined as any sensitive information, whether stored persistently or dynamically generated and returned, that requires secure management.
An HTTP session token is a credential used for authorization but represents only one type of secret, not the overarching definition of what Vault considers a 'secret'.
The threshold of keys required to unseal Vault refers to the `key shares` and `threshold` mechanism, which is part of Vault's security model, not the definition of a 'secret'.
In Vault, the term 'secret' refers to any sensitive data that Vault manages, protects, and grants access to, which can include credentials, API keys, encryption keys, or other confidential material, either stored persistently or generated on demand.
An engine responsible for logging requests and responses is an audit device, which is a component of Vault for logging activity, not the definition of a 'secret'.
Concept tested: Definition of a Vault secret
Source: https://developer.hashicorp.com/vault/docs/concepts/secrets
Topics
Community Discussion
No community discussion yet for this question.