You are using Vault CLI and enable the database secrets engine on the default path of database/. However, the DevOps team wants to enable another database secrets engine for testing but receives an error stating the path is already in use. How can you enable a second database secrets engine using the CLI?
Comprehensive and Detailed In-Depth
Vault mounts secrets engines at unique paths, and only one engine can occupy a given path (e.g., database/). To enable a second database secrets engine, you must specify a different path using the -path flag: vault secrets enable -path=database2 database mounts a new instance at database2/. The type (database) defines the engine, and -path customizes its location, avoiding conflicts.
A: Incorrect syntax; lacks -path and misplaces database2/.
B: -force doesn't create a new path; it overwrites an existing engine, which isn't the goal.
D: Omits -path and engine type, making it invalid.
The secrets engine tutorial confirms -path is required for multiple instances of the same engine type.
Secrets Engines Tutorial
Secrets Enable Command
Marylou
4 days agoFelicia
9 days agoNadine
14 days agoDick
19 days agoJordan
24 days agoNadine
29 days agoDick
1 month agoJordan
1 month agoDick
1 month agoJordan
2 months agoWilburn
2 months agoZona
2 months agoGearldine
2 months agoKristel
2 months agoMarkus
3 months agoValentin
3 months agoNobuko
3 months agoTeri
3 months agoNida
3 months ago