HCVA0-003 Exam Questions & Answers
HashiCorp Certified: Vault Associate (003) Exam • HashiCorp
100% money-back guarantee
Sample HCVA0-003 Questions
Practice with real exam-style questions, each with the verified correct answer and explanation.
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
num_uses 0
orphan false
path auth/token/create
period 24h
policies [admin default]
renewable true
ttl 23h59m50s
type service
Comprehensive and Detailed in Depth Explanatio n:
A: period indicates a renewable periodic token. Correct.
Overall Explanation from Vault Docs:
''A periodic token has a period... renewable without a max TTL.''
Mike's Cereal Shack uses Vault to encrypt customer data to ensure it is always stored securely. They are developing a new application integration to send new customer data to be encrypted using the following API request:
text
CollapseWrapCopy
$ curl \
--header "X-Vault-Token: hvs.sf4vj1rFV5PvQSV3M9dcv832brxQFsfbXA" \
--request POST \
--data @data.json \
https://vault.mcshack.com:8200/v1/transit/encrypt/customer-data
What would be contained within the data.json file?
Comprehensive and Detailed in Depth Explanatio n:
The data.json file in this API request contains the data to be encrypted by the Transit secrets engine. The HashiCorp Vault documentation states: 'When executing any call to the Vault API, data can be sent using an external file as shown above. In this case, the contents of the file would be cleartext customer data that needs to be encrypted by the transit secrets engine.' Specifically, for the /transit/encrypt/ endpoint, it explains: 'The API expects a JSON payload with a plaintext field containing the base64-encoded data to encrypt.'
The documentation elaborates under 'Encrypt Data': 'The request body must include the plaintext parameter, which is the base64-encoded version of the data you want to encrypt. For example: {'plaintext': 'base64-encoded-data'}.' Here, D (Cleartext customer data to be encrypted) fits this requirement---customer data in cleartext, base64-encoded, sent for encryption. A (Transit config) is managed in Vault, not sent. B (Ciphertext) is the output, not input. C (Encryption key) is stored in Vault, not provided by the client. Thus, D is correct.
HashiCorp Vault Documentation - Transit API: Encrypt Data
Which of the following is not an action associated with the Transit secrets engine when interacting with data?
Comprehensive and Detailed in Depth Explanatio n:
The Transit secrets engine focuses on cryptographic operations, not data storage or modification. The HashiCorp Vault documentation states: 'The transit secrets engine handles cryptographic functions on data in-transit. Vault doesn't store the data sent to the secrets engine. It can also be viewed as 'cryptography as a service' or 'encryption as a service'. The transit secrets engine can also sign and verify data; generate hashes and HMACs of data; and act as a source of random bytes.'
It further notes: 'You can, however, rewrap data when the key has been rotated to ensure data is encrypted with the latest version.' Supported actions include encrypt, decrypt, and rewrap, but update is not a function, as Transit doesn't store or modify data. Thus, D is correct.
HashiCorp Vault Documentation - Transit Secrets Engine
True or False? You can create and update Vault policies using the UI.
Comprehensive and Detailed In-Depth
The Vault UI supports policy management:
A . True: 'You can indeed create and update Vault policies within the UI.'
Incorrect Option:
B . False: Incorrect; UI functionality exists.
Thomas has authenticated to Vault using the API and has received the following response. What data must Thomas parse from the response in order to continue making requests to Vault?
text
CollapseWrapCopy
{
"request_id": "65897160-fd8b-1f87-c24e-fdba14c9728e",
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": null,
"wrap_info": null,
"warnings": null,
"auth": {
"client_token": "hvss.lzrmRe5Y3LMcDRmOttEjWoagd92fD29fxakwej_38djs",
"accessor": "EMX0nv4nr0Y1wXoaN7i0WDW1",
"policies": ["bryan", "default"],
"token_policies": ["bryan", "default"],
"metadata": {"username": "bryan"},
"lease_duration": 2764800,
"renewable": true,
"entity_id": "40e203e8-818e-b6ad-4cb3-0befdbf9b598",
"token_type": "service",
"orphan": true
}
}
Comprehensive and Detailed In-Depth
To continue API requests:
C . client_token: 'When you authenticate to Vault using the API, the response will include the client_token, which is required for subsequent responses.' This token, found at .auth.client_token, must be included in the X-Vault-Token header.
Incorrect Options:
A . accessor: Used for token management, not requests.
B . request_id: Tracks the request, not for auth.
D . entity_id: Identifies the entity, not for requests.
Get access to all 285 verified questions with detailed answers.
Unlock All HCVA0-003 Questions