Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.

AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by Hashicorp
Exam Format
Registration
Validity
Skills this practice test covers
- Choose an auth method for a use case and log in through the CLI, API and UI.
- Read and write Vault policies, from path patterns to capabilities such as deny.
- Choose between service and batch tokens, and predict when a token expires or is revoked.
- Renew and revoke the leases that come with dynamic secrets.
- Encrypt data with the transit secrets engine and rotate its key.
- Compare storage backends, auto-unseal and the two kinds of Enterprise replication.
Explore related topics
Vault-Associate-003 exam content
9 domains · 22 topics · 180 questions
Authentication methods16 questions
Every client must prove who it is before Vault gives it a token. Candidates choose an auth method for a use case, tell human methods from machine methods, and use entities and groups to tie several logins to one identity.
Skills tested
- Choose between methods such as LDAP, OIDC, AppRole and Kubernetes for a given client.
- Explain why applications use machine methods such as AppRole instead of human logins.
- Link aliases to one entity and grant shared access through groups.
- Enable, configure and log in with an auth method through the CLI, API and UI.
Questions by topic
- 1b: Choose an authentication method based on use case9
- 1d: Define the purpose of identities and groups7
Vault policies25 questions
Policies decide what a token may do on each path. Candidates read policy syntax, from glob patterns and the + wildcard to capabilities such as read, list and deny, and choose the smallest policy that meets a need.
Skills tested
- Read path rules that use a glob or a + segment.
- Pick the capabilities a task needs, from create and update to list and deny.
- Write a least-privilege policy and apply it through the UI and CLI.
Questions by topic
- 2c: Describe Vault policy syntax: capabilities10
- 2b: Describe Vault policy syntax: path7
- 2d: Choose a Vault policy based on requirements8
Vault tokens24 questions
Tokens carry every Vault session. Candidates choose between service and batch tokens, explain root tokens, token accessors and time-to-live, and know what happens to child and orphan tokens when a parent is revoked.
Skills tested
- Choose a service or a batch token for a workload.
- Explain when a root token is needed and why it should be revoked after use.
- Use a token accessor to look up or revoke a token without knowing the token itself.
- Predict when a token expires from its TTL and its max TTL.
Questions by topic
- 3b: Describe root token uses and lifecycle8
- 3c: Explain the purpose of token accessors8
- 3a: Choose between service and batch tokens based on use case8
Vault leases7 questions
Dynamic secrets come with a lease that limits how long they live. Candidates explain the lease ID, renew a lease before it ends, and revoke leases when access must stop.
Skills tested
- Find the lease ID that Vault returns with a dynamic secret.
- Renew a lease without going past its maximum TTL.
- Revoke a lease so that the credential behind it stops working.
Questions by topic
- 4c: Describe how to revoke leases7
Secrets engines33 questions
This domain covers the engines that store or generate secrets. Candidates compare static and dynamic secrets, use the transit engine and response wrapping, and enable engines and read secrets through the CLI, API and UI.
Skills tested
- Choose between the KV, database and transit secrets engines for a use case.
- Explain why short-lived dynamic credentials are safer than static passwords.
- Wrap a response so that a secret travels inside a single-use token.
- Enable a secrets engine at a path and read its secrets through the CLI, API and UI.
Questions by topic
- 5e: Describe the use of response wrapping7
- 5h: Access Vault secrets using the CLI, API, and UI9
- 5c: Describe the uses of transit secrets engine9
- 5a: Choose a secrets engine based on use case8
Encryption as a Service10 questions
The transit secrets engine encrypts data for applications without storing it. Candidates encrypt and decrypt data and rotate the encryption key while older ciphertext stays readable.
Skills tested
- Encrypt and decrypt data with the transit engine, encoding the plaintext in base64 first.
- Rotate a transit key and set the minimum decryption version.
Questions by topic
- 6b: Rotate the encryption key10
Vault architecture fundamentals15 questions
This domain covers what happens inside a Vault server. Candidates describe how the barrier encrypts all stored data, how sealing and unsealing work, and which environment variables the CLI reads.
Skills tested
- Describe how the keyring and the barrier protect everything Vault writes to storage.
- Unseal Vault with key shares and compare that with auto-unseal.
- Set VAULT_ADDR and VAULT_TOKEN so that the CLI reaches the right server.
Questions by topic
- 7b: Explain how to seal and unseal Vault7
- 7a: Describe how Vault encrypts data8
Vault deployment architecture33 questions
Candidates compare clusters that a team runs itself with HCP Vault Dedicated clusters that HashiCorp runs. They also choose a storage backend, explain Shamir secret sharing, and tell the two kinds of Enterprise replication apart.
Skills tested
- Compare self-managed clusters with HCP Vault Dedicated for a given team.
- Choose integrated storage or an external storage backend such as Consul.
- Explain how Shamir secret sharing splits the root key into key shares.
- Tell disaster recovery replication from performance replication.
Questions by topic
- 8e: Differentiate between self-managed and HashiCorp-managed Vault clusters9
- 8a: Explain cluster strategy for self-managed and HashiCorp-managed Vault clusters9
- 8d: Explain the uses of disaster recovery and performance replication7
- 8b: Explain the uses of storage backends8
Access management architecture17 questions
This domain covers how applications get secrets without calling Vault themselves. Candidates describe Vault Agent, with auto-auth, caching and templates, and the Vault Secrets Operator, which syncs Vault secrets into Kubernetes secrets.
Skills tested
- Describe how Vault Agent logs in with auto-auth and renders secrets through templates.
- Explain how the Vault Secrets Operator uses custom resources to sync secrets into Kubernetes.
Questions by topic
- 9b: Describe the Vault Secrets Operator8
- 9a: Describe the Vault Agent9
Requirements
- No formal prerequisites: anyone can book the exam.
- Recommended: basic terminal skills and a basic understanding of on-premises and cloud architecture.
- Recommended: a basic grasp of security and some time with Vault in production or a demo setup.
About the Vault-Associate-003 exam
Vault-Associate-003 tests whether an engineer can keep secrets in HashiCorp Vault, issue short-lived credentials and decide who may read them. Its nine domains run from authentication methods, policies, tokens and leases to secrets engines, then to how Vault encrypts and seals data and how its clusters are deployed. Several objectives ask for the same task in the CLI, the API and the UI. Passing earns the HashiCorp Certified: Vault Associate certification, which lasts two years.
Secrets engines and Vault deployment architecture get the most questions in the PlanetCert practice test. The explanations show how tokens, leases and policies behave, for example why an orphan token survives when the token that created it is revoked, or why deny overrides every other capability. Study Mode suits the policy questions, where one path pattern or one capability changes the answer. Brainy AI Assistant can compare service and batch tokens, or explain how performance replication differs from disaster recovery replication.
How to earn the certification
- Earns
- HashiCorp Certified: Vault AssociateAssociate
The certification lasts two years.
- After
- Vault-Operations-Professional HashiCorp Certified: Vault Operations Professional
The professional-level Vault exam and the next step in HashiCorp's Vault track.
- Vault-Operations-Professional HashiCorp Certified: Vault Operations Professional
How to prepare for Vault-Associate-003
- 1
Run Vault on a laptop
Start a dev server, set VAULT_ADDR and VAULT_TOKEN, and do each task in the CLI, the API and the UI. Then start a second server with integrated storage to practise sealing and unsealing with key shares.
- 2
Test each policy with a fresh token
Write policies that use globs and the + wildcard, attach each one to a new token, and check what the token can read. Policy questions often turn on one path or one capability.
- 3
Follow tokens through their lifecycle
Create service and batch tokens, child and orphan tokens, and tokens with short TTLs. Revoke a parent and note which tokens survive.
- 4
Generate, renew and revoke secrets
Enable a database secrets engine, read a credential, then renew and revoke its lease. Encrypt data with the transit engine, rotate the key and decrypt the older ciphertext.
- 5
Time the full practice test last
Use Study Mode on the Vault-Associate-003 practice test for the weakest domains, then take full runs in Timed Mode. Ask Brainy AI Assistant why each wrong option fails, for example on replication types.
Start a timed Vault-Associate-003run
HashiCorp's Vault Associate (003) learning path covers every objective with tutorials, and its exam content list links each objective to the Vault 1.16 documentation.
Who Vault-Associate-003 is for
- Platform and DevOps engineers who replace hard-coded credentials with secrets from Vault.
- Security engineers who decide which people and applications may read each secret.
- Engineers who run applications on Kubernetes and sync secrets with the Vault Secrets Operator.
- Cloud engineers taking the first step in HashiCorp's Vault track.
Typical job titles: DevOps engineer · Platform engineer · Security engineer · Cloud engineer · Site reliability engineer
Vault-Associate-003 glossary
20 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- AppRole
- An auth method for machines and applications, which log in with a role ID and a secret ID.
- Auto-unseal
- A way to unseal Vault with a trusted key service, such as a cloud key management service, instead of entering key shares by hand.
- Barrier
- Vault's encryption layer, which encrypts all data before it leaves Vault for the storage backend.
- Batch tokens
- Lightweight tokens that Vault does not store and that cannot be renewed, suited to short jobs that run in large numbers.
- Cubbyhole
- A private storage area for each token that no other token can read. Response wrapping uses it.
- Dynamic secrets
- Credentials that Vault creates on request, such as a database login, and destroys when their lease ends.
- Entity
- Vault's record of one user or machine, which links the aliases from different auth methods to a single identity.
- HCP Vault Dedicated
- HashiCorp's managed Vault service, in which HashiCorp runs the clusters for the customer.
- Integrated storage
- Vault's built-in storage backend, which keeps a copy of the data on each cluster node through the Raft protocol.
- Lease ID
- The identifier Vault returns with a dynamic secret, used to renew or revoke that secret's lease.
- Orphan tokens
- Tokens with no parent, so they are not revoked when the token that created them is revoked.
- Performance replication
- Enterprise replication that copies data to secondary clusters, which can then answer client requests close to their users.
- Response wrapping
- Putting a response inside a single-use token, so that a secret can be passed on safely and unwrapped only once.
- Root token
- A token with full access to everything in Vault, meant for setup and emergencies and revoked after use.
- Shamir secret sharing
- The method that splits Vault's root key into key shares, a set number of which must be entered to unseal Vault.
- Time-to-live
- The period for which a token or lease stays valid. Vault revokes it when the time runs out, unless it is renewed.
- Token accessors
- Values that refer to a token, used to look it up, renew it or revoke it without seeing the token itself.
- Transit secrets engine
- A secrets engine that encrypts and decrypts data sent to it without storing that data, so applications never hold the key.
- Vault Agent
- A client daemon that logs in to Vault for an application, keeps its token current, and can cache or render secrets.
- Vault Secrets Operator
- A Kubernetes operator that reads secrets from Vault and syncs them into native Kubernetes secrets.
Related practice tests
- CA-003HashiCorp Certified: Consul Associate (003)
- Terraform AssociateTerraform Associate (003)
- terraform-associate-003HashiCorp Certified: Terraform Associate (003)
- TA-004HashiCorp Certified: Terraform Associate (004)
- VA-003HashiCorp Certified: Vault Associate (003)