VAULT-ASSOCIATE-002 · Question #46
You have manually created some usernames and passwords for a Microsoft SQL database on Azure, and need to store these credentials in Vault. What secrets engine should you use for this?
The correct answer is B. Key/Value secrets engine version 2. To store manually created static credentials for a Microsoft SQL database, the Key/Value (KV) secrets engine version 2 is the most appropriate choice in Vault.
Question
Options
- AMSSQL database secrets engine
- BKey/Value secrets engine version 2
- CAzure secrets engine
- DTransit engine
How the community answered
(19 responses)- A5% (1)
- B89% (17)
- C5% (1)
Why each option
To store manually created static credentials for a Microsoft SQL database, the Key/Value (KV) secrets engine version 2 is the most appropriate choice in Vault.
The MSSQL database secrets engine is used for dynamically generating database credentials, not for storing existing static ones.
The Key/Value (KV) secrets engine, particularly version 2, is designed for storing arbitrary static secrets like manually created usernames and passwords, offering versioning and auditing capabilities.
The Azure secrets engine is used for dynamically generating Azure-specific credentials, not for storing general database credentials.
The Transit engine is used for cryptographic functions like encryption as a service, not for storing secrets directly.
Concept tested: Vault K/V secrets engine for static secrets
Source: https://developer.hashicorp.com/vault/docs/secrets/kv/kv-v2
Topics
Community Discussion
No community discussion yet for this question.