20+ practice questions focused on Create Vault policies — one of the most tested topics on the HashiCorp Vault Associate VA-003 exam. Each question includes a detailed explanation so you learn why the right answer is correct.
Start Create Vault policies PracticeA company wants to grant developers the ability to read and write secrets under the path 'secret/dev/*', but only they should be able to delete their own secrets. Which policy design best meets this requirement?
Explanation: It grants full CRUDL access to 'secret/dev/*' for reading and writing, but then restricts delete to only the path 'secret/dev/{{identity.entity.name}}/*', which uses the entity's name to ensure developers can only delete secrets under their own sub-path. This leverages Vault's identity entity name templating to enforce per-developer delete scoping.
Which TWO of the following are valid capabilities that can be specified in a Vault policy?
Explanation: In HashiCorp Vault policies, capabilities are the specific actions a token can perform on a path, and the valid set includes create, read, update, delete, list, patch, sudo, and deny. Option A (create) is correct because it allows a client to create new entries at a given path, such as generating a new secret version or writing a new key where none existed. Option E (update) is correct because it permits modifying existing data at a path, and Vault distinguishes it from create so policies can allow updates without permitting initial creation. Option B (write) is not a Vault capability keyword; it is a legacy/HTTP-style verb that Vault maps internally to create and update, so it cannot be specified directly in a policy. Option C (sudo) is a real Vault capability but it is not one of the two marked correct here, and option D (rename) is not a Vault capability at all, as Vault has no rename operation on paths.
A DevOps team is managing secrets for a microservices application using Vault. They have created a policy named 'app-policy' that grants read access to secrets under the path 'secret/data/app/*'. The policy is assigned to an AppRole role. When a service authenticates with the role ID and secret ID, it receives a token but is unable to read secrets from 'secret/data/app/db-creds'. The token's identity metadata shows the policies associated with the token include 'default' and 'app-policy'. The Vault server logs show no errors. The service can successfully read other secrets from the same path, like 'secret/data/app/config'. What is the most likely cause of the issue?
Explanation: The most likely cause is that the secret 'secret/data/app/db-creds' does not exist in Vault. The token has the 'app-policy' policy attached, which grants read access to 'secret/data/app/*', and the service can successfully read other secrets under that path (e.g., 'secret/data/app/config'). The absence of Vault server errors indicates that the policy is correctly evaluated and the path is valid, but a read on a non-existent secret returns a 404 (or a permission-denied-like response) without logging an error. The token's metadata confirms the policy is present, ruling out policy assignment issues.
A security team wants to ensure that all Vault policies for applications follow the principle of least privilege. They have a policy 'app-kv' that grants read access to secrets under 'secret/data/app/*'. An auditor finds that a developer can also read secrets under 'secret/data/team/*'. The policy currently uses a path-based glob. Which change should the team make to restrict access to only the app path?
Explanation: The essential fix is to change the path to the exact glob 'secret/data/app/*' so that it only matches secrets under that directory. In Vault, policies are additive and only allow capabilities; there is no 'deny' capability, but the path change itself restricts access to the intended path. Other options are incorrect: A uses '+' which matches a single segment and 'list' does not grant read; C incorrectly applies a deny policy which is invalid; D removes the glob, which only allows listing the directory, not reading secrets within it.
A DevOps team is writing a Vault policy for a CI/CD pipeline that needs to authenticate using AppRole, read specific secrets, and write dynamic database credentials. Which THREE capabilities should be included in the policy to meet these requirements? (Choose three.)
Explanation: The only capability required for the described tasks is 'read'. Reading specific secrets from KV v2 or generating dynamic database credentials (via database/creds/<role-name>) both use the 'read' operation. AppRole authentication is handled before the policy applies; the policy itself does not need to grant capabilities for the login process.
+15 more Create Vault policies questions available
Practice all Create Vault policies questions1. Baseline your knowledge
Start with 10 questions to gauge your current understanding of Create Vault policies. This tells you whether you need a concept refresher or just practice.
2. Review every explanation
For each question — right or wrong — read the full explanation. Understanding why an answer is correct is more valuable than knowing the answer itself.
3. Focus on exam traps
Create Vault policies questions on the VA-003 frequently use trap wording. Look for subtle differences in answers that test your precision, not just general knowledge.
4. Reach 80% consistently
Do repeated sessions until you score 80%+ three times in a row. Then move to mixed-mode practice to test cross-topic recall under realistic conditions.
The exact number varies per candidate. Create Vault policies is tested as part of the HashiCorp Vault Associate VA-003 blueprint. Practicing with targeted Create Vault policies questions ensures you can handle any format or difficulty that appears.
Yes. Courseiva provides free VA-003 practice questions across all exam topics and domains. The platform includes topic-based practice, mock exams, missed-question review, bookmarked questions, and readiness tracking — no account required.
Difficulty is subjective, but Create Vault policies is a high-priority exam concept tested in multiple ways — direct recall, scenario analysis, and command-output interpretation. Consistent practice is the best way to build confidence.
Launch a full Create Vault policies practice session with instant scoring and detailed explanations.
Start Create Vault policies Practice →