VAULT-ASSOCIATE practice question 1 of 15

To give a role the ability to display or output all of the end points under the /secrets/apps/* end point it would need to have which capability set?

Full set: 57 questions
Answer options
A: update
B: read
C: sudo
D: list Correct answer
E: None of the above
Correct Answer:
D. list
Explanation

The list capability is required to view the available keys or sub-paths under a specific path prefix in Vault. The question asks for the ability to "display or output all of the end points" under /secrets/apps/, which directly corresponds to the list operation (e.g., vault list secret/apps). This capability allows a client to discover what secrets are available for reading without granting permission to access the secret content itself, adhering to the principle of least privilege.

Why Incorrect

A. update: This capability allows for writing or replacing data at a given path, not for listing available endpoints.
B. read: This capability allows for retrieving the actual secret data at a specific path, but not for discovering which paths exist.
C. sudo: This is a highly privileged capability used for accessing protected system paths (like /sys) and is not the standard or correct permission for listing secrets.
E. None of the above: This is incorrect as the list capability is the specific and correct answer for the described action. ---

References

1. HashiCorp Vault Official Documentation, "Policies": Under the "Capabilities" section, the documentation explicitly states: "list - Allows listing values at a given path. Some backends use this to list existing keys." This directly maps to the requirement in the question.

Source: HashiCorp, Vault Documentation, "Policies", Section: Capabilities. https://developer.hashicorp.com/vault/docs/concepts/policies#capabilities

2. HashiCorp Vault Official Documentation, "Policy Syntax": This page provides examples and clarifies that to perform a list operation on a path (e.g., secret/), the policy must grant the list capability on that path.

Source: HashiCorp, Vault Documentation, "Policy Syntax", Section: Paths. https://developer.hashicorp.com/vault/docs/concepts/policies#paths

3. HashiCorp Learn, "Vault Policies" Tutorial: In the "Write a policy" section, the tutorial demonstrates creating a policy for an application. It distinguishes between read (to get a secret's value) and list (to see what secrets are available under a path), reinforcing their distinct functions.

Source: HashiCorp Learn, "Vault Policies", Section: Write a policy. https://developer.hashicorp.com/vault/tutorials/policies/policies#write-a-policy

Scroll to Top