VA-003 Explain Vault architecture Practice Question
Exhibit
storage "file" {
path = "/vault/data"
}
seal "awskms" {
region = "us-west-2"
kms_key_id = "1234abcd-12ab-34cd-56ef-1234567890ab"
}
listener "tcp" {
address = "0.0.0.0:8200"
tls_disable = "false"
tls_cert_file = "/etc/vault/vault.crt"
tls_key_file = "/etc/vault/vault.key"
}
api_addr = "https://vault.example.com:8200"
cluster_addr = "https://vault.example.com:8201"Refer to the exhibit. What seal mechanism is configured for this Vault instance?
⚠ Common exam trap
HashiCorp often tests the distinction between default Shamir sealing and external auto-unseal mechanisms; the trap here is that candidates see a Vault configuration and assume it uses the default Shamir seal, missing the explicit `seal "awskms"` directive that overrides it.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
AWS KMS auto-unseal
The exhibit shows a Vault instance configured with `seal "awskms"` and a `region` and `kms_key_id` specified. This indicates that AWS KMS is used as the auto-unseal mechanism, where Vault delegates the unsealing process to AWS Key Management Service, eliminating the need for manual Shamir key shares.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
AWS KMS auto-unseal
Why this is correct
The exhibit shows a seal stanza of type awskms with a KMS key ID and region, which is the auto-unseal configuration. Vault uses that AWS KMS key to decrypt the root key automatically at startup, removing the need for manual unseal keys.
- ✗
HSM seal via PKCS#11
Why it's wrong here
PKCS#11 requires a physical HSM or network-attached appliance, and the exhibit shows no such seal stanza or library path. It is tempting because PKCS#11 is a genuine Vault seal type, and would be correct if the configuration named a PKCS#11 module and slot for hardware-backed key storage.
- ✗
Shamir seal with default shares
Why it's wrong here
Shamir seal requires operators to supply unseal key shares, and the exhibit shows an automatic cloud KMS seal instead. It is tempting because Shamir is Vault's default seal type, and would be correct if the configuration contained no auto-unseal stanza and the instance prompted for key shares at startup.
- ✗
No seal; Vault is in insecure mode
Why it's wrong here
Vault always requires a seal mechanism; insecure mode does not exist as a supported configuration, so the exhibit cannot show this. It is tempting because Shamir seals can be disabled in dev mode, but production Vault instances still seal on startup and unseal with keys or auto-unseal.
Go deeper
Related to this question
About these practice questions
Courseiva writes every VA-003 question from scratch — 366 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This VA-003 practice question is part of Courseiva's free HashiCorp certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the VA-003 exam.