All Vault instances, or clusters, include two built-in policies that are created automatically. Choose the two policies below and the correct information regarding each policy. (Select two)
Comprehensive and Detailed In-Depth
Vault automatically creates two built-in policies: root and default.
A: The root policy is created at initialization, granting superuser privileges (full access to all paths and operations). It's attached to root tokens and cannot be deleted or modified, per the policies documentation.
C: The default policy is also created automatically, providing basic permissions (e.g., token management). It's attached to all non-root tokens by default, can be modified, but cannot be deleted, as stated in the docs.
B: No admin policy is automatically created; administrative policies must be defined manually.
D: The default policy can be modified, contradicting this option.
Built-in Policies
Your organization operates active/active applications across multiple data centers for high availability. Which Vault feature should be used in the secondary data centers to provide local access to secrets?
Comprehensive and Detailed In-Depth
For active/active setups:
D . Performance replication cluster: 'Should be used in an active/active scenario to ensure applications in both data centers can easily access Vault secrets.'
Incorrect Options:
A: Scales single cluster, not multi-DC.
B, C: Not suited for local access.
Which of the following Vault policies will allow a Vault client to read a secret stored at secrets/applications/app01/api_key?
Comprehensive and Detailed in Depth
This question requires identifying a policy that permits reading the secret at secrets/applications/app01/api_key. Vault policies use paths and capabilities to control access. Let's evaluate:
A: path 'secrets/applications/' { capabilities = ['read'] allowed_parameters = { 'certificate' = [] } }
This policy allows reading at secrets/applications/, but not deeper paths like secrets/applications/app01/api_key. The allowed_parameters restriction is irrelevant for reading secrets. Incorrect.
B: path 'secrets/*' { capabilities = ['list'] }
The list capability allows listing secrets under secrets/, but not reading their contents. Reading requires the read capability. Incorrect.
C: path 'secrets/applications/+/api_*' { capabilities = ['read'] }
The + wildcard matches one segment (e.g., app01), and api_* matches api_key. This policy grants read access to secrets/applications/app01/api_key. Correct.
D: path 'secrets/applications/app01/api_key/*' { capabilities = ['update', 'list', 'read'] }
This policy applies to subpaths under api_key/, not the exact path api_key. It includes read, but the path mismatch makes it incorrect for this specific secret.
Overall Explanation from Vault Docs:
''Wildcards (*, +) allow flexible path matching... read capability is required to retrieve secret data.'' Option C uses globbing to precisely target the required path.
True or False? All Vault policies are deny by default.
Comprehensive and Detailed in Depth
The statement is True. Vault operates on a default-deny model for policies. The HashiCorp Vault documentation states: 'Vault policies implicitly deny all actions that are not explicitly permitted in the Vault policy.' This ensures that access must be explicitly granted, enhancing security.
The docs elaborate: 'By default, a token has no policies attached beyond the default policy (which grants minimal permissions), and any action not explicitly allowed by an attached policy is denied.' This principle underpins Vault's access control, making A correct.
HashiCorp Vault Documentation - Policies Tutorial
What is the correct order that Vault uses to protect data?
Comprehensive and Detailed in Depth
Vault protects data using a layered encryption process: root key --> encryption key --> data. The HashiCorp Vault documentation explains: 'The data stored by Vault is encrypted. Vault needs the encryption key to decrypt it. The key is also stored with the data (in the keyring), but it is encrypted with another key known as the root key. Therefore, to decrypt the data, Vault must decrypt the encryption key, which requires the root key.' This sequence ensures data security through multiple encryption layers.
The docs further clarify: 'Unsealing is the process of accessing this root key. The root key is stored alongside all Vault data but is encrypted by yet another mechanism: the unseal key. To recap: most Vault data is encrypted using the encryption key in the keyring; the keyring is encrypted by the root key; and the root key is encrypted by the unseal key.' Option B includes unseal keys but omits the encryption key's role. C and D misrepresent the order. Thus, A is correct.
HashiCorp Vault Documentation - Seal Concepts
Desmond
6 days agoHorace
14 days agoBrinda
21 days agoViola
28 days agoFiliberto
1 month agoJustine
1 month agoYoko
2 months agoNoemi
2 months agoCory
2 months agoJovita
2 months agoErinn
3 months agoFlorinda
3 months agoKathrine
3 months agoBok
3 months agoGlory
4 months agoLynna
4 months agoLawrence
4 months agoDesmond
4 months agoDewitt
5 months agoAileen
5 months agoMarlon
5 months agoShonda
5 months agoFletcher
5 months agoEloisa
5 months agoEdna
6 months agoAmos
6 months agoDominga
6 months agoEliz
8 months agoCorinne
8 months agoAlaine
8 months agoMalcolm
9 months agoAnnice
9 months agoHubert
10 months agoLizbeth
10 months agoAmie
10 months agoRolland
11 months agoKristeen
12 months agoDella
12 months ago