
HashiCorp Certified: Vault Associate (003) checks that you understand Vault, the tool many companies use to store and hand out secrets: passwords, API keys, database credentials and certificates. Instead of putting secrets in code or config files, applications authenticate to Vault and get only what a policy allows, often as short-lived credentials that expire on their own. The exam tests Vault 1.19 and suits DevOps, cloud and security engineers.
This guide follows HashiCorp's official exam page and the 003 review guide: exam facts, all nine objectives, the core ideas in plain words, the commands you need, a 3-week plan and 15 original practice questions.
Quick facts (HashiCorp, November 2026)
| Item | Detail |
|---|---|
| Exam | Vault Associate (003) |
| Format | Online proctored, multiple choice |
| Duration | 1 hour |
| Product version | Vault 1.19 |
| Price | US$70.50 plus local taxes and fees; no free retake |
| Validity | 2 years |
| Language | English |
| Prerequisites | None formally; basic terminal skills, on-premises and cloud architecture, and security basics |
Read the official Vault Associate exam page and the 003 review guide.
The nine exam objectives
| # | Objective | What it covers |
|---|---|---|
| 1 | Authentication methods | Choosing an auth method; human vs system auth; identities and groups; logging in and configuring auth through the API, CLI and UI |
| 2 | Vault policies | Why policies matter; path and capabilities; choosing and writing policies |
| 3 | Vault tokens | Service vs batch tokens; root tokens; accessors; TTL; orphan tokens; creating tokens |
| 4 | Vault leases | Lease IDs; renewing and revoking leases |
| 5 | Secrets engines | Choosing an engine; dynamic vs static secrets; transit; response wrapping; enabling engines and reading secrets through the API, CLI and UI |
| 6 | Encryption as a service | Encrypting and decrypting data; rotating the encryption key |
| 7 | Vault architecture fundamentals | How Vault encrypts data; sealing and unsealing; environment variables |
| 8 | Vault deployment architecture | Self-managed vs HashiCorp-managed clusters; storage backends; Shamir secret sharing; disaster recovery and performance replication |
| 9 | Access management architecture | Vault Agent; Vault Secrets Operator for Kubernetes |
Core ideas in plain words
- Auth method → token → policy: a person or app logs in (userpass, OIDC, AppRole, Kubernetes, AWS and others) and receives a token. Policies attached to the token decide which paths it can use.
- Static vs dynamic secrets: KV stores a secret you put in. Dynamic engines (database, AWS and others) create a fresh credential on request with a lease, and Vault deletes it when the lease ends.
- Leases: every dynamic secret has a lease ID and TTL; you can renew it or revoke it early, including by prefix.
- Transit: Vault encrypts and decrypts data for applications but doesn't store it; keys can be rotated without re-encrypting old data at once.
- Seal and unseal: Vault starts sealed. The root key is split with Shamir's secret sharing (or auto-unseal uses a cloud KMS or HSM), and enough key shares are needed to unseal.
- Response wrapping: Vault returns a single-use wrapping token instead of the secret, so the secret itself never travels through the middle system.
Policy and commands to know
# app-policy.hcl
path "secret/data/app/*" {
capabilities = ["read", "list"]
}
path "database/creds/app-role" {
capabilities = ["read"]
}
export VAULT_ADDR=https://vault.example.com:8200
vault status # sealed or unsealed?
vault operator unseal # enter one key share
vault login -method=userpass username=dev
vault auth enable approle
vault policy write app app-policy.hcl
vault secrets enable -path=secret kv-v2
vault kv put secret/app/config api_url=https://api.example.com
vault kv get secret/app/config
vault secrets enable database # dynamic database credentials
vault read database/creds/app-role # returns a username, password and lease
vault lease renew <lease_id>
vault lease revoke -prefix database/creds/app-role
vault token create -policy=app -ttl=1h
vault token lookup -accessor <accessor>
vault secrets enable transit
vault write -f transit/keys/orders
vault write transit/encrypt/orders plaintext=$(base64 <<< "hello")
vault write -f transit/keys/orders/rotate
Use a local dev server (vault server -dev) only for learning. Never use dev mode or a root token for real workloads.
3-week study plan
| Week | Focus | Lab |
|---|---|---|
| 1 | Objectives 1–4: auth methods, policies, tokens, leases | Run a dev server; enable userpass and AppRole; write two policies and test what each token can and can't read |
| 2 | Objectives 5–6: KV v1 vs v2, database and cloud engines, transit, response wrapping | Generate dynamic PostgreSQL credentials, then revoke them; encrypt, rotate and decrypt with transit |
| 3 | Objectives 7–9: seal and unseal, storage (integrated Raft), replication, HCP Vault, Vault Agent, Vault Secrets Operator; review | Start a non-dev server with Raft storage and unseal it with key shares; inject a secret into a kind pod with Vault Secrets Operator; book the exam |
15 practice questions with answers
These are original questions written for this guide, not exam questions.
1. Which auth method is designed for machines and applications using a role ID and secret ID?
AppRole.
2. What decides what a token can do?
The policies attached to it.
3. Which capability lets a token read a secret?
read.
4. What is the default if no policy grants access to a path?
Access is denied.
5. A job runs thousands of short tasks and needs lightweight tokens that aren't stored. Service or batch tokens?
Batch tokens.
6. When should a root token be used?
Only for initial setup or emergencies, then revoked.
7. What is a token accessor for?
Looking up, renewing or revoking a token without knowing the token value itself.
8. What happens to child tokens when a parent token is revoked?
They are revoked too, unless they are orphan tokens.
9. Why are dynamic secrets safer than static ones?
Each client gets a unique, short-lived credential that Vault revokes automatically, so a leak has limited reach and is traceable.
10. Which secrets engine encrypts data without storing it?
Transit.
11. After rotating a transit key, can data encrypted with the old version still be decrypted?
Yes, as long as the old version is within the allowed minimum decryption version.
12. What does a sealed Vault do with requests?
It can't read its data, so it rejects nearly all requests until it is unsealed.
13. Which algorithm splits the root key into key shares?
Shamir's secret sharing.
14. Which replication type keeps a standby cluster ready for failover?
Disaster recovery replication.
15. Which tool syncs Vault secrets into Kubernetes Secrets?
Vault Secrets Operator.
After Vault Associate
- Pair it with the Terraform Associate (004) guide, which now includes Vault for sensitive data.
- Add Kubernetes security with KCSA and cloud security with AWS Security Specialty.
- Learn it hands-on in our DevSecOps course and Terraform course; see live DevOps and security jobs.
Cloud Soft Solutions in Ameerpet, Hyderabad teaches DevSecOps, Terraform, Kubernetes and cloud security with real-time projects. See the APEX program and all courses.
📞 Call +91 96660 19191 · WhatsApp · Flat No. 513, 5th Floor, Nilagiri Block, Aditya Enclave, Ameerpet, Hyderabad
Frequently Asked Questions
What is the Vault Associate exam?
HashiCorp Certified: Vault Associate (003), a 1-hour online proctored multiple-choice exam on Vault 1.19.
How much does Vault Associate cost?
US$70.50 plus local taxes and fees. A free retake is not included.
How long is Vault Associate valid?
2 years.
How many objectives does Vault Associate 003 have?
Nine: auth methods, policies, tokens, leases, secrets engines, encryption as a service, architecture fundamentals, deployment architecture and access management.
What are dynamic secrets?
Credentials Vault creates on request with a lease and revokes automatically when the lease ends.
Should I take Terraform or Vault Associate first?
Most DevOps learners take Terraform Associate first, then Vault Associate for secrets management.



