cert-bank

Exams

VLT-VA003 HashiCorp Vault Associate (003)

Vendor
HashiCorp
Level
Associate
Questions
50
Time
60 min
Domains
9
In the bank
313

Practice 313 questionsTake a timed mock examDay-by-day study plan

Guides for this exam

The exam at a glance

LevelAssociate
Questions50
Time60 minutes (about 1.2 minutes per question)
Passing markNot published by the vendor

Domains and weights

The vendor does not publish domain weights for this exam, so the shares below are equal by assumption. Treat every domain as roughly the same size.

DomainWeightPractice questions here
D1 · Authentication methods11.1%36
D2 · Vault policies11.1%35
D3 · Vault tokens11.1%36
D4 · Vault leases11.1%34
D5 · Secrets engines11.1%36
D6 · Encryption as a Service11.1%34
D7 · Vault architecture fundamentals11.1%34
D8 · Vault deployment architecture11.1%34
D9 · Access management architecture11.1%34

57 of the 313 practice questions (18%) ask for more than one answer.

D1 · Authentication methods 11.1%

Auth method items pair a type of client with an identity source and ask which method fits, or why a login fails. People with directory accounts, Kubernetes workloads and shared logins all appear. The right answer follows how Vault turns verified credentials into a token with identity and policies; wrong options often pick a method built for a different kind of client.

What to watch for

Tasks in the official exam guide (6)
  • 1.1 Define the purpose of authentication methods
  • 1.2 Choose an authentication method based on use case
  • 1.3 Explain human vs. system authentication methods
  • 1.4 Define the purpose of identities and groups
  • 1.5 Authenticate to Vault using the API, CLI, and UI
  • 1.6 Configure authentication methods using the API, CLI, and UI

D2 · Vault policies 11.1%

Policy questions are mostly about reading HCL path stanzas correctly. A stem shows a path, a capability list or a template and asks what a request is allowed to do, or which policy grants just enough. Because Vault denies by default, the details decide the answer: exact versus glob paths, the KV v2 data/ segment, and how deny interacts with everything else.

What to watch for

Tasks in the official exam guide (5)
  • 2.1 Explain the value of Vault policies
  • 2.2 Describe Vault policy syntax: path
  • 2.3 Describe Vault policy syntax: capabilities
  • 2.4 Choose a Vault policy based on requirements
  • 2.5 Configure Vault policies using the UI and CLI

D3 · Vault tokens 11.1%

Token scenarios ask which token type or setting matches a workload, why a token request is refused, or how long a token can survive. Root token handling, accessors, periods and maximum TTLs come up often. The distractors usually treat renewal as unlimited or ignore which actions need extra privileges on the token create path.

What to watch for

Tasks in the official exam guide (6)
  • 3.1 Choose between service and batch tokens
  • 3.2 Describe root token uses and lifecycle
  • 3.3 Explain the purpose of token accessors
  • 3.4 Explain the impact of time-to-live
  • 3.5 Explain orphaned tokens
  • 3.6 Describe how to create tokens based on need

D4 · Vault leases 11.1%

Lease questions check what each lease operation does and who may run it. Some ask for the matching CLI or HTTP call, others ask why bulk revocation is denied or why leases exist at all. Right answers separate inspecting a lease from changing it, and recognise which endpoints are privileged.

What to watch for

Tasks in the official exam guide (3)
  • 4.1 Explain the purpose of a lease ID
  • 4.2 Describe how to renew leases
  • 4.3 Describe how to revoke leases

D5 · Secrets engines 11.1%

Secrets engine items ask which engine matches a need and how to use it correctly. Typical needs are encrypting data an application stores itself, issuing short-lived certificates, creating database users on demand, or reading KV v2 data with generic commands. The distractors are often real engines used for the wrong pattern, or commands that ignore the real API path.

What to watch for

Tasks in the official exam guide (8)
  • 5.1 Choose a secrets engine based on use case
  • 5.2 Compare dynamic and static secrets and their use cases
  • 5.3 Describe the uses of the transit secrets engine
  • 5.4 Describe the purpose of secrets engines
  • 5.5 Describe the use of response wrapping
  • 5.6 Explain the value of short-lived, dynamically generated secrets
  • 5.7 Enable secrets engines using the CLI, API, and UI
  • 5.8 Access Vault secrets using the CLI, API, and UI

D6 · Encryption as a Service 11.1%

Encryption as a Service centres on the transit engine. Stems show encrypt, decrypt or key configuration commands and ask what is wrong, what the output means, or what a key setting allows. Small details carry the answer: base64 encoding on the way in and out, which named key produced a ciphertext, and the difference between encryption and decryption version limits.

What to watch for

Tasks in the official exam guide (2)
  • 6.1 Encrypt and decrypt secrets
  • 6.2 Rotate the encryption key

D7 · Vault architecture fundamentals 11.1%

Architecture fundamentals cover what happens from first start to sealed data at rest. Questions ask about the initialize and unseal steps, the default behavior of operator init, what the security barrier does, how the key chain fits together, and which client settings are safe. Wrong options tend to mix up the order of keys or treat test shortcuts as production practice.

What to watch for

Tasks in the official exam guide (3)
  • 7.1 Describe how Vault encrypts data
  • 7.2 Explain how to seal and unseal Vault
  • 7.3 Configure environment variables

D8 · Vault deployment architecture 11.1%

Deployment questions weigh cluster design choices: seal types, rekeying, replication effects, storage layout and node counts. Most present a proposal or operational pain point and ask what the change really achieves. Answers that sound safer, such as adding a node or a standby for throughput, are often wrong once quorum and HA behavior are taken into account.

What to watch for

Tasks in the official exam guide (5)
  • 8.1 Explain cluster strategy for self-managed and HashiCorp-managed Vault clusters
  • 8.2 Explain the uses of storage backends
  • 8.3 Explain the uses of Shamir secret sharing and unsealing
  • 8.4 Explain the uses of disaster recovery and performance replication
  • 8.5 Differentiate self-managed and HashiCorp-managed Vault clusters

D9 · Access management architecture 11.1%

Access management architecture is about getting secrets to applications. Scenarios involve Kubernetes pods, VSO resources, Vault Agent caching and applications that cannot reload secrets. You decide which delivery pattern or setting fits, or why secrets come back stale. Distractors usually mix up Kubernetes-only tools with host-based ones, or miss how Agent settings and environment variables interact.

What to watch for

Tasks in the official exam guide (2)
  • 9.1 Describe the Vault Agent
  • 9.2 Describe the Vault Secrets Operator

A study order that works

The 15-day study plan for VLT-VA003 takes the domains in this order. Each day has a short reading, key terms and a quiz from the bank.

  1. Days 1–2: D1 · Authentication methods
  2. Days 3–4: D2 · Vault policies
  3. Days 5–6: D3 · Vault tokens
  4. Day 7: D4 · Vault leases
  5. Days 8–9: D5 · Secrets engines
  6. Day 10: D6 · Encryption as a Service
  7. Day 11: D7 · Vault architecture fundamentals
  8. Days 12–13: D8 · Vault deployment architecture
  9. Day 14: D9 · Access management architecture
  10. Day 15: Final Review: Exam Format, the Nine Objectives, Commonly Confused Pairs and Test-Day Plan

Recent changes to these questions

About these questions

Every question is original, written from the public exam guide and checked against the vendor's own documentation. None comes from a real exam. Each one has an explanation of why the answer is right and why the other options are wrong. How the questions are written.