Vault Associate study plan
Vault Associate · Give each week a clear focus.
8 weeks · About 7 hours per week
Compare authentication methods & Explain Vault architecture
Compare token, userpass, LDAP, GitHub, and AppRole authentication methods and write a one-line note on when each is the right fit
Enable two different auth methods on a local dev Vault server and complete a successful login against each
Trace a single
vault kv getrequest through CLI, HTTP API, core, barrier, and storage backend, and write down where authorization happensIdentify which Vault components are unavailable while the seal is engaged and explain what an operator must supply to unseal
Distinguish auth methods from token stores and state which one issues the client token in each flow
Your checkpoint
A one-page architecture diagram of the request path plus a comparison table of five auth methods with the exact CLI login command for each, and proof of two working logins
Create Vault policies & Manage tokens
Write HCL policies that grant least privilege on a KV path, separating read from create/update capabilities
Attach policies to tokens and demonstrate that a request to an unauthorized path returns a 403 permission denied error
Create service tokens and batch tokens, then contrast their renewal, revocation, and storage behavior
Set explicit TTL and max_ttl on a token and demonstrate both renewal and revocation from the CLI
Explain the difference between a token ID and a token accessor, and revoke a token by using only its accessor
Your checkpoint
A policy set of three HCL files (admin, app-read, ops-rotate) with captured CLI output showing one allowed and one denied request for each policy
Manage tokens & Access secrets
Create token roles that fix TTL, period, and policy sets, then issue tokens from each role and verify the resulting TTLs
Use response wrapping to deliver a secret to a consumer and unwrap it before the wrapping TTL expires
Read, write, version, soft-delete, and undelete a KV v2 secret using both CLI and HTTP API calls
Map KV v1 API paths to their KV v2 equivalents, explaining the /data/ and /metadata/ path segments
Consume a secret from an environment variable populated at runtime so that no credential is written into a file
Your checkpoint
A captured demo in which a wrapped token is issued, unwrapped, and used to read a KV v2 secret, including the CLI transcript and the secret version history
Access secrets & Configure secrets engines
Enable a KV v2 secrets engine at a custom mount path and move an existing secret from a v1 mount to it
Enable the transit secrets engine and perform an encrypt, a decrypt, and a key rotation, confirming old ciphertext still decrypts
Configure a database secrets engine against a local database and generate dynamic credentials from a role
Classify three sample secrets as static, dynamic, or leased and state which lease fields apply to each
Your checkpoint
Lab notes showing dynamic database credentials generated, used, and revoked, including the lease ID and the revocation output
Configure secrets engines
Configure a PKI secrets engine with a root and an intermediate CA and issue a short-lived certificate from a role
Configure a cloud secrets engine role and generate dynamic cloud credentials, or reproduce the flow against a mock endpoint if no cloud account is available
Set default_lease_ttl and max_lease_ttl on a mount and observe how each changes the TTL of issued leases
Tune an existing mount's configuration and verify the change without recreating stored data
Explain which secrets engine types generate leases and which return static data with no lease
Your checkpoint
An annotated command log proving two additional engines (PKI plus one cloud or database engine) are configured and issuing credentials with the intended TTLs
Secure and operate a Vault deployment
Enable a file audit device and confirm that a request appears in the audit log with sensitive values HMAC'd rather than in plaintext
Walk through seal and unseal with Shamir key shares and describe what changes operationally during a rekey
Write and execute a backup and restore procedure against a dev instance's storage backend
Explain the purpose of the barrier, the root key, and the unseal keys, and state which one never leaves Vault
Describe the access requirements for the Vault listener, storage backend, and audit device in a production deployment
Your checkpoint
An operations runbook covering audit device enablement, backup and restore, and seal/unseal, with command output proving each step succeeded
Manage tokens & Manage Vault leases
Trace the full lifecycle of a leased credential from issuance through renewal to expiry, naming the TTL that governs each stage
List active leases with the sys/leases lookup endpoint and revoke a single lease by its lease ID
Revoke a lease prefix and confirm the dependent tokens and credentials are also invalidated
Diagnose a token that fails to renew and identify whether TTL, max_ttl, or a periodic token setting is the cause
Explain what happens to a client's secret when its token is revoked versus when the lease expires naturally
Your checkpoint
A troubleshooting write-up with CLI evidence for three scenarios: a successful renewal, a renewal rejected by max_ttl, and a revocation cascade from a revoked token
Compare authentication methods & Create Vault policies & Manage tokens & Access secrets & Configure secrets engines & Explain Vault architecture & Manage Vault leases & Secure and operate a Vault deployment
Complete two full-length timed practice exams and score every miss against the domain it belongs to
Re-derive from memory the policy grammar for path, capabilities, and parameter constraints without consulting notes
Re-run the weakest three lab exercises from weeks 1 through 7 until each succeeds on the first attempt
Explain aloud, in under two minutes each, how authentication, authorization, lease management, and sealing fit together
Confirm readiness by scoring at least 85 percent on the final practice exam with no domain below 70 percent
Your checkpoint
A scored practice exam log with per-domain accuracy, plus a one-page remediation list identifying every remaining weak area and the drill that fixes it
Milestones
Week 2: Demonstrate from a clean dev server: write a policy, create a token bound to it, prove one allowed request and one 403 denial, and revoke the token by accessor
Week 4: Complete an end-to-end flow unaided: enable a secrets engine, write a least-privilege policy, issue a scoped token, and retrieve a secret; score at least 80 percent on a 30-question self-test over domains 1 through 4
Week 6: Produce audit log evidence of a hashed sensitive value, restore a backup into a fresh dev instance, and revoke a lease prefix with visible dependent invalidation
Week 8: Score at least 85 percent overall on a timed mock exam with no single domain below 70 percent, and close every item on the remediation list