VAULT-ASSOCIATE-002 · Question #34
Which statement describes the results of this command: $ vault secrets enable transit?
The correct answer is A. Enables the transit secrets engine at transit path. Executing vault secrets enable transit successfully enables the Transit secrets engine, mounting it at its default path, which is /transit.
Question
Options
- AEnables the transit secrets engine at transit path
- BRequires a root token to execute the command successfully
- CEnables the transit secrets engine at secret path
- DFails due to missing -path parameter
- EFails because the transit secrets engine is enabled by default
How the community answered
(51 responses)- A86% (44)
- B8% (4)
- D2% (1)
- E4% (2)
Why each option
Executing `vault secrets enable transit` successfully enables the Transit secrets engine, mounting it at its default path, which is `/transit`.
When the `vault secrets enable <type>` command is executed without specifying the `-path` parameter, Vault defaults the mount path for the secrets engine to its type name, thus enabling the `transit` secrets engine at the `/transit` path.
Enabling a secrets engine generally requires appropriate permissions, which may be granted through a policy with `sudo` capability on `sys/mounts/transit/*`, not necessarily requiring a root token.
The default path for the `transit` secrets engine when enabled without a specific path is `/transit`, not `/secret`, which is typically used for the KV secrets engine.
The `-path` parameter is optional for the `vault secrets enable` command; if omitted, the secrets engine is mounted at a path corresponding to its type.
The Transit secrets engine is not enabled by default in a new Vault instance; it must be explicitly enabled using the `vault secrets enable transit` command.
Concept tested: Enabling Vault secrets engines
Source: https://developer.hashicorp.com/vault/docs/commands/secrets/enable
Topics
Community Discussion
No community discussion yet for this question.