Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. HashiCorp
  5. HCVA0-003

HashiCorp HCVA0-003 Exam
HashiCorp Certified: Vault Associate (003) (Page 10 )

Updated On: 9-Feb-2026
Page 10 of 58
PDF with 285 Questions

True or False? Once you create a KV v1 secrets engine and place data in it, there is no way to modify the mount to include the features of a KV v2 secrets engine.

  1. True
  2. False

Answer(s): B

Explanation:

Comprehensive and Detailed in Depth
A: Incorrect; KV v1 can be upgraded to v2.
B: Correct; vault kv enable-versioning upgrades it.
Overall Explanation from Vault Docs:
"kv enable-versioning turns on versioning for an existing KV v1 engine at its path."


Reference:

https://developer.hashicorp.com/vault/docs/secrets/kv/kv-v2#upgrading-from-version-1



Given the following screenshot, how many secrets engines have been enabled by a Vault user?

  1. 2
  2. 3
  3. 4
  4. 5

Answer(s): B

Explanation:

Comprehensive and Detailed in Depth cubbyhole is default; kv and transit are user-enabled. Total: 3.
Overall Explanation from Vault Docs:
"cubbyhole is enabled by default... User-enabled engines add to this."


Reference:

https://developer.hashicorp.com/vault/docs/secrets/cubbyhole



When configuring Vault replication and monitoring its status, you keep seeing something called 'WALs'.
What are WALs?

  1. Warning of allocated logs
  2. Write along logging
  3. Write-ahead logs
  4. Wake after LAN

Answer(s): C

Explanation:

Comprehensive and Detailed in Depth
C: WALs (Write-Ahead Logs) ensure data consistency in replication. Correct.
Overall Explanation from Vault Docs:
"Replication uses Write-Ahead Logs (WALs) for log shipping between clusters..."


Reference:

https://developer.hashicorp.com/vault/docs/internals/replication



A Jenkins server is using the following token to access Vault. Based on the lookup shown below, what type of token is this?
$ vault token lookup hvs.FGP1A77Hxa1Sp6Pkp1yURcZB

Key Value
--- -----
accessor RnH8jtgrxBrYanizlyJ7Y8R
creation_time 1604604512
creation_ttl 24h display_name token entity_id n/a expire_time 2025-11-06T14:28:32.8891566-05:00
explicit_max_ttl 0s id hvs.FGP1A77Hxa1Sp6KRau5eNB
issue_time 2025-11-06T14:28:32.8891566-05:00
meta <nil>
num_uses 0
orphan false path auth/token/create period 24h policies [admin default]
renewable true ttl 23h59m50s type service

  1. Periodic token
  2. Batch token
  3. Orphaned token
  4. Secondary token

Answer(s): A

Explanation:

Comprehensive and Detailed in Depth

A: period indicates a renewable periodic token. Correct.
Overall Explanation from Vault Docs:
"A periodic token has a period... renewable without a max TTL."


Reference:

https://developer.hashicorp.com/vault/docs/concepts/tokens#token-time-to-live- periodic-tokens-and-explicit-max-ttls



After encrypting data using the Transit secrets engine, you've received the following output.
Which of the following is true based on the output displayed below? Key: ciphertext Value:
vault:v2:45f9zW6cglbrzCjI0yCyC6DBYtSBSxnMgUn9B5aHcGEit71xefPEmmjMbrk3

  1. The original encryption key has been rotated at least once
  2. The data is stored in Vault using a KV v2 secrets engine
  3. This is the second version of the encrypted data
  4. Similar to the KV secrets engine, the Transit secrets engine was enabled using the transit v2 option

Answer(s): A

Explanation:

Comprehensive and Detailed in Depth
A: v2 shows the key was rotated once. Correct.
B: Transit doesn't store data. Incorrect.
C: v2 is the key version, not data version. Incorrect.
D: No transit v2 option exists. Incorrect.
Overall Explanation from Vault Docs:
"Ciphertext is prepended with the key version (e.g., v2)... Indicates rotation."


Reference:

https://developer.hashicorp.com/vault/tutorials/encryption-as-a-service/eaas- transit#rotate-the-encryption-key






Post your Comments and Discuss HashiCorp HCVA0-003 exam prep with other Community members:

Join the HCVA0-003 Discussion