HCVA0-003 Exam Questions Get Updated [2026] with Correct Answers [Q127-Q144]

Comprehensive and Detailed in Depth Explanation:
When writing a Vault policy, the valid capabilities are predefined, andmodifyis not among them. The HashiCorp Vault documentation states: “When writing a policy in Vault, permissions which can be applied to paths include create, read, update, delete, list, deny, and sudo.” These capabilities dictate what actions a token can perform on a path.
The docs elaborate: “Capabilities are specific permissions assigned to paths in a policy. For example, create allows creating new resources, update modifies existing ones, delete removes them, list retrieves listings, and read accesses data.”Modifyis not a recognized capability; it’s likely a misnomer for update. Thus, B is the correct answer.
Reference:
HashiCorp Vault Documentation – Policies: Capabilities

To create a new user named “sally” with password “h0wN0wB4r0wnC0w” and the power-users policy, you would use the Vault userpass auth method mounted at auth/userpass. You would use the following command:
“vault write auth/userpass/users/sally password=h0wN0wB4r0wnC0w policies=power-users”. This command would create a new user named “sally” with the specified password and policy. References:
* [Userpass Auth Method | Vault | HashiCorp Developer]
* [Create Vault policies | Vault | HashiCorp Developer]

Comprehensive and Detailed in Depth Explanation:
* A:Soft-deletes data, not metadata.Incorrect.
* B:Destroys a version, not the path. Incorrect.
* C:Deletes all metadata and versions, removing the path. Correct.
* D:Invalid syntax. Incorrect.
Overall Explanation from Vault Docs:
“kv metadata delete deletes all versions and metadata for the key, permanently removing it.” Reference:https://developer.hashicorp.com/vault/docs/secrets/kv/kv-v2#key-metadata

Comprehensive and Detailed In-Depth Explanation:
In HashiCorp Vault, the default TTL (Time To Live) for tokens, when not explicitly specified, is 768 hours
, equivalent to 32 days . This applies to both the initial TTL and the maximum TTL unless overridden.
* Default Configuration : The documentation states: ” When no specific TTL is provided, a generated token will inherit the default TTL which is 768 hours (32 days). ” This long default ensures usability in many scenarios while allowing customization.
* Customization Option : Operators can adjust this using commands like vault write sys/mounts/auth
/token/tune default_lease_ttl=1h max_lease_ttl=24h, but without such tuning, 768 hours applies.
* Incorrect Options :
* A. 24 hours : Too short for Vault’s default; it’s a common custom setting instead.
* B. 15 minutes : Far too brief and not aligned with Vault’s defaults.
* D. 60 minutes : Another common custom value, not the default.
This default balances usability with security, encouraging explicit configuration for shorter-lived tokens when needed.
Reference: https://developer.hashicorp.com/vault/docs/concepts/tokens

Response wrapping is a feature that allows Vault to take the response it would have sent to a client and instead insert it into the cubbyhole of a single-use token, returning that token instead. The client can then unwrap the token and retrieve the original response. Response wrapping has several benefits, such as providing cover, malfeasance detection, and lifetime limitation for the secret data. One of the benefits is to ensure that only a single party can ever unwrap the token and see what’s inside, as the token can be used only once and cannot be unwrapped by anyone else, even the root user or the creator of the token. This provides a way to securely distribute secrets to the intended recipients and detect any tampering or interception along the way 5 .
The other options are not benefits of response wrapping:
* Log every use of a secret: Response wrapping does not log every use of a secret, as the secret is not directly exposed to the client or the network. However, Vault does log the creation and deletion of the response-wrapping token, and the client can use the audit device to log the unwrapping operation 6 .
* Load balance secret generation across a Vault cluster: Response wrapping does not load balance secret generation across a Vault cluster, as the secret is generated by the Vault server that receives the request and the response-wrapping token is bound to that server. However, Vault does support high availability and replication modes that can distribute the load and improve the performance of the cluster 7 .
* Provide error recovery to a secret so it is not corrupted in transit: Response wrapping does not provide error recovery to a secret so it is not corrupted in transit, as the secret is encrypted and stored in the cubbyhole of the token and cannot be modified or corrupted by anyone. However, if the token is lost or expired, the secret cannot be recovered either, so the client should have a backup or retry mechanism to handle such cases.: 5 (https://developer.hashicorp.com/vault/docs/concepts/response-wrapping), 6 (https://developer.hashicorp.
com/vault/docs/secrets), 7 (https://developer.hashicorp.com/vault/docs/secrets), (https://developer.hashicorp.
com/vault/tutorials/secrets-management/cubbyhole-response-wrapping)

The correct answer is A because the lease ID is the unique identifier for the credential. Thelease ID is used to revoke the credential using the vault lease revoke command. This command will invalidate the credential immediately and prevent any further renewals. It will also delete the access key and secret key from AWS, rendering them useless1. The access key and secret key are not sufficient to revoke the credential, as they are not recognized by Vault. The lease ID is composed of the path of the secrets engine, the role name, and a random UUID. In this case, the path is aws/creds, the role name is s3-access, and the UUID is f3e92392-7d9c-
99c8-c921-57Sd62fe89d8.
:
lease revoke – Command | Vault | HashiCorp Developer

The statement is true. When an auth method is disabled, all users authenticated via that method lose access.
This is because the tokens issued by the auth method are automatically revoked when the auth method is disabled. This prevents the users from performing any operation in Vault using the revoked tokens. To regain access, the users have to authenticate again using a different auth method that is enabled and has the appropriate policies attached. References: Auth Methods | Vault | HashiCorp Developer, auth disable – Command | Vault | HashiCorp Developer

Comprehensive and Detailed In-Depth Explanation:
When using the Transit secrets engine, Vault encrypts data and returns ciphertext (e.g., vault:v1: < ciphertext
> ). Upon decryption (e.g., vault write transit/decrypt/ < key_name > ciphertext= < value > ), Vault returns the plaintext as a Base64-encoded string. This is because the Transit engine supports arbitrary data, including binary files (e.g., PDFs, images), and Base64 encoding ensures safe transport within JSON payloads. If the decrypted output (e.g., Zml2ZSBzdGFyIHByYWN0aWNlIGV4YW1zIGJ5IGJyeWFuIGtyYXVzZW4=) isn’t legible, it’s not an error-it’s Base64 encoded. Decoding it (e.g., using a Base64 decoder) reveals the original plaintext (e.g., ” five star practice exams by bryan krausen ” ).
Option A (incorrect key) would cause a decryption failure, not illegible plaintext. Option B (incorrect key version) is irrelevant, as Vault automatically uses the correct version based on the ciphertext’s vault:v# prefix, and changing it manually wouldn’t produce Base64 output. Option D (database encryption) isn’t indicated in the scenario and would also cause a failure, not Base64 output. The Transit documentation explicitly states that plaintext is returned Base64-encoded, requiring the user to decode it.
References:
Transit Secrets Engine Docs
Transit Usage Section

The command shown in the image is:
vault token create -policy=approle -orphan -period=60h
This command creates a new token with the following characteristics:
* It has the policy “approle” attached to it, which grants or denies access to certain paths and operations in Vault according to the policy rules. The policy can be defined by using the vault policy write command or the sys/policy API endpoint12.
* It is an orphan token, which means it has no parent token and it will not be revoked when its parent token is revoked. Orphan tokens can be useful for creating long-lived tokens that are not affected by the token hierarchy3.
* It has a period of 60 hours, which means it has a renewable TTL of 60 hours. This means that the token can be renewed indefinitely as long as it does not go past the 60-hour mark from the last renewal time.
The token’s TTL will be reset to 60 hours upon each renewal. Periodic tokens are useful for creating tokens that have a fixed lifetime and can be easily revoked4.: [1]1, [2]2, 3(https://developer.hashicorp.com/vault/docs/secrets/kv), 4(https://developer.hashicorp.com/vault
/docs/secrets/kv)

The statement is false. A root token can create orphan tokens, but it is not the only possible method. Vault’s token API includes the /auth/token/create-orphan endpoint, and HashiCorp explicitly notes that a root token is not required when using that endpoint. The no_parent option is restricted and normally requires root or sudo- level authority, but the existence of a non-root orphan-token creation path makes the absolute statement incorrect. This is a common Vault exam trap: root tokens are highly privileged, but Vault also allows controlled delegation through specific endpoints and capabilities. Therefore, saying orphan tokens can only be created with the root token is too strict and inaccurate. The correct exam answer is False.

Comprehensive and Detailed In-Depth Explanation:
The Transit secrets engine in Vault is designed for encryption as a service, allowing applications to encrypt data without managing keys locally. After enabling the engine, two critical steps are required before encryption can begin: creating an encryption key and defining a policy to allow its use.
Option C: You must create an encryption key using a command like vault write -f transit/keys/ < key_name >
. This key is stored in Vault and used for encryption/decryption operations. Without it, no encryption can occur, as the Transit engine relies on named keys to perform cryptographic operations.
Option D: A policy must be written to grant the application permissions to use the key, such as path ” transit
/encrypt/ < key_name > ” { capabilities = [ ” update ” ] } and path ” transit/decrypt/ < key_name > ” { capabilities = [ ” update ” ] }. Vault’s access control ensures that only authorized entities can perform encryption, making this step essential.
Option A (exporting the key) contradicts Vault’s security model, as keys should remain in Vault, not be exported to application servers. Option B (enabling the Transit API) is unnecessary, as enabling the engine automatically exposes its API endpoints. The official Transit documentation confirms that key creation and policy configuration are the next steps post-enablement.
References:
Transit Secrets Engine Tutorial
Transit Secrets Engine Docs

Comprehensive and Detailed in Depth Explanation:
HCP Vault Dedicated is a managed cloud service offering specific benefits over self-managed Vault. The HashiCorp Vault documentation outlines its advantages: “Vault Enterprise running on the HashiCorp Cloud Platform (HCP) enables users to secure, store, and tightly control access to tokens, passwords, certificates, and encryption keys within one unified cloud-based platform.” It lists the following benefits relevant to the options:
* B (Helps reduce operational overhead for organizations with push-button deployment and fully managed upgrades): The documentation states, “Reduce operational overhead: Push-button deployment, fully managed upgrades, and backups mean organizations canfocus on adoption and integration instead of operational overhead.” This reflects HCP Vault Dedicated’s managed nature, automating deployment and maintenance tasks.
* C (Increases reliability and ease of use so you can onboard applications and teams easily): It notes,
“Ease of use: HCP Vault Dedicated is built around making cloud security automation simple. Get up and running quickly so that you can onboard applications and teams easily,” and “Reliability:
HashiCorp has experience supporting thousands of commercial Vault Enterprise clusters and HCP Vault Dedicated brings that expertise directly to users.” This simplifies onboarding and ensures dependable operation.
* D (Increases security across clouds and machines through a single interface): The docs confirm,
“Increase security across clouds and machines: Secure your infrastructure across all your environments through a single interface and globally control and restrict access to sensitive data and systems,” highlighting centralized security management.
However,A (Provides 100% feature parity compared to Vault self-managed clusters)is false. The documentation clarifies under “Feature Parity”: “HCP Vault Dedicated does not provide 100% feature parity compared to Vault self-managed clusters. While it offers many of the same features and capabilities, there may be some differences or limitations in functionality between the two deployment options.” Thus, B, C, and D are true.
Reference:
HashiCorp Vault Documentation – What is HCP Vault: Feature Parity

Comprehensive and Detailed in Depth Explanation:
For human interaction with Vault,OIDC(OpenID Connect) is the best choice. The HashiCorp Vault documentation states: “Out of the selections provided, OIDC is the best choice since OIDC authentication uses the user’s web browser to complete the authentication request. This is not well suited for machine-to- machine authentication.” OIDC leverages identity providers (e.g., AzureAD, Google) for user-friendly authentication via browser-based flows.
The docs add: “The other options of Kubernetes, AppRole, and TLS are more geared towards application
/machine/system authentication since they aren’t human-friendly.”Kubernetessuits cluster workloads, AppRoleis for machines, andTLSsecures communication, not human logins. Thus, D (OIDC) is correct.
Reference:
HashiCorp Vault Documentation – Authentication Methods

Comprehensive and Detailed In-Depth Explanation:
A token accessor allows:
* A, B, D, E: “This accessor can only be used to perform limited actions: Look up a token’s properties, Look up a token’s capabilities on a path, Renew the token, Revoke the token.” The calling token needs permissions.
* Incorrect Option:
* C: “Not including the actual token ID.”
Reference:https://developer.hashicorp.com/vault/docs/concepts/tokens#token-accessors

Comprehensive and Detailed in Depth Explanation:
The command initializes Vault, splitting the master key into 3 shares (threshold 2) and encrypting each with PGP keys for Jane, John, and Student01. Let’s analyze:
* Option A: The admin never sees all the unseal keys and cannot unseal Vault by themselvesWith – pgp-keys, Vault encrypts each share with a user’s public PGP key. The admin (initializer) sees only encrypted outputs (e.g., Key 1: <encrypted>), not plaintext keys. Since 2 shares are needed and no single entity gets all, the admin can’t unseal alone. Correct.Vault Docs Insight:”The initializer receives encrypted keys… never sees all plaintext keys, enhancing security.” (Directly stated.)
* Option B: All three users, Jane/John/Student01, will receive all unseal keys and canunseal Vault Each user gets one encrypted share (e.g., Jane gets Key 1, John Key 2). No user receives all shares- only one, decryptable with their private key. Unsealing requires collaboration (2 of 3), so this is false.
Incorrect.Vault Docs Insight:”Each PGP key encrypts one share… No single user gets all keys.” (Distribution is per-user.)
* Option C: The admin will receive the unseal keys and be able to unseal Vault themselvesWithout PGP, the admin gets plaintext keys. With -pgp-keys, they get encrypted keys they can’t decrypt (lacking private keys). Threshold=2 means collaboration is required. Incorrect.Vault Docs Insight:”Using PGP keys ensures the initializer cannot unseal alone…” (Security feature.)
* Option D: The keys will be returned encryptedThe -pgp-keys flag encrypts each share with the corresponding public key. Output shows encrypted blobs (e.g., base64-encoded PGP ciphertext), not plaintext. Correct.Vault Docs Insight:”Vault will generate the unseal keys and encrypt them using the given PGP keys…” (Explicit behavior.)
* Option E: Each individual can only decrypt their own unseal key using their private PGP key Each share is encrypted with one user’s public key (e.g., Jane’s key encrypts Key 1). Only Jane’s private key decrypts it. This ensures secure distribution. Correct.Vault Docs Insight:”Only the owner of the corresponding private key can decrypt the value…” (PGP security.) Detailed Mechanics:
Command: vault operator init -key-shares=3 -key-threshold=2 -pgp-keys=”jane.pgp,john.pgp,student01.pgp”.
Vault generates 3 shares via Shamir’s Secret Sharing, encrypts each (Key 1 with jane.pgp, etc.), and outputs encrypted strings. Unsealing requires 2 decrypted shares combined via vault operator unseal. PGP ensures the admin can’t access plaintext, enforcing split knowledge.
Real-World Example:
Output: Key 1: <encrypted-jane>, Key 2: <encrypted-john>, Key 3: <encrypted-student01>. Jane decrypts Key 1 with gpg -d, John decrypts Key 2. They submit via UI or CLI to unseal.
Overall Explanation from Vault Docs:
“Vault can optionally be initialized using PGP keys. In this mode, Vault will generate the unseal keys and immediately encrypt them using the given users’ public PGP keys. Only the owner of the corresponding private key is able to decrypt the value… The initializer never sees all plaintext keys and cannot unseal Vault alone.” This enhances security by distributing trust.
Reference:https://developer.hashicorp.com/vault/docs/commands/operator/init#pgp-keys

The statement is false. The Vault encryption key is not stored in Vault’s backend storage, but rather in Vault’s memory. The Vault encryption key is the key that is used to encrypt and decrypt the data that is stored in Vault’s backend storage, such as secrets, tokens, policies, etc. The Vault encryption key is derived from the master key, which is generated when Vault is initialized. The master key is split into unseal keys using Shamir’s secret sharing algorithm, and the unseal keys are distributed to trusted operators. To start Vault, a quorum of unseal keys is required to reconstruct the master key and derive theencryption key. The encryption key is then kept in memory and used to protect the data in Vault’s backend storage. The encryption key is never written to disk or exposed via the API. References: Seal/Unseal | Vault | HashiCorp Developer, Key Rotation | Vault | HashiCorp Developer

Comprehensive and Detailed In-Depth Explanation:
Unsealing involves:
* C. Reconstructing the root key: “Unsealing is the process of obtaining the plaintext root key necessary to read the decryption key to decrypt the data, allowing access to the Vault.” The unseal keys reconstruct this root key via Shamir’s Secret Sharing.
* Incorrect Options:
* A: Recovery keys are separate.
* B: Keys aren’t exported during unseal.
* D: Data decryption is a result, not the action.
Reference:https://developer.hashicorp.com/vault/docs/concepts/seal#seal-unseal

Comprehensive and Detailed in Depth Explanation:
KV v2 supports versioning. Let’s evaluate:
* A:destroy removes a specific version permanently. Correct.
* B:destroy targets specified versions, not all. Incorrect.
* C:delete soft-deletes the current version. Correct.
* D:metadata delete removes all versions and metadata. Correct.
Overall Explanation from Vault Docs:
“kv delete soft-deletes… kv destroy permanently removes versions… kv metadata delete wipes everything.” Reference:https://developer.hashicorp.com/vault/docs/secrets/kv/kv-v2