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

The correct flag is -period=24h because it creates a periodic token. A periodic token receives a fixed renewal period, and every renewal uses that period. As long as the token is actively renewed and no explicit maximum TTL is imposed, it can continue to be renewed indefinitely. The -ttl=24h flag only sets the initial TTL; normal token renewal is still constrained by maximum TTL values from the token, mount, auth method, parent token, or system configuration. The -explicit-max-ttl=0 option alone does not create a periodic token. The -orphan flag removes the parent relationship but does not make the token indefinitely renewable. HashiCorp’s token create command documentation shows -period as the periodic-token flag.

================

The Identity secrets engine is the correct solution because it lets Vault consolidate multiple authentication aliases into one entity. A user may authenticate through GitHub, LDAP, Active Directory, or another auth method, but Vault can map those accounts to the same entity. Policies can then be attached to the entity or inherited through identity groups, allowing one consistent access model regardless of which identity provider the user used to log in. OIDC and LDAP are individual authentication methods; they do not, by themselves, unify multiple identity-provider accounts into one Vault identity. Tokens are issued after authentication and carry policies, but they are not the identity-mapping mechanism. HashiCorp documents that Vault Identity ties authentications from different auth methods into one entity with aliases.

================

The command that does not meet the security requirement of not having secrets appear in the shell history is B. vault kv put secret/password value-itsasecret. This command would store the secret value “itsasecret” in the key/value secrets engine at the path secret/password, but it would also expose the secret value in the shell history, which could be accessed by other users or malicious actors. This is not a secure way of storing secrets in Vault.

The other commands are more secure ways of storing secrets in Vault without revealing them in the shell history. A. generate-password | vault kv put secret/password value would use a pipe to pass the output of the generate-password command, which could be a script or a tool that generates a random password, to the vault kv put command, which would store the password in the key/value secrets engine at the path secret/password. The password would not be visible in the shell history, only the commands. C. vault kv put secret/password value=@data.txt would use the @ syntax to read the secret value from a file named data.txt, which could be encrypted or protected by file permissions, and store it in the key/value secrets engine at the path secret/password. The file name would be visible in the shell history, but not the secret value. D. vault kv put secret/password value-SSECRET_VALUE would use the -S syntax to read the secret value from the environment variable SECRET_VALUE, which could be set and unset in the shell session, and store it in the key/value secrets engine at the path secret/password. The environment variable name would be visible in the shell history, but not the secret value.

Batch tokens are the best strategy when many short-lived workloads need to authenticate or interact with Vault at high volume. Unlike service tokens, batch tokens are lightweight encrypted blobs that do not require Vault to persist token state to disk. This reduces storage backend I/O during large-scale startup events, such as 1000+ containers requesting Vault access at the same time. Kubernetes auth and AppRole are authentication methods, but they do not by themselves eliminate token storage overhead. Short-TTL service tokens still require storage writes, and single-use tokens do not solve the backend I/O problem at scale. HashiCorp’s token documentation describes batch tokens as lightweight, scalable, and requiring no storage on disk to track them.

================

Not all storage backends support high availability mode for Vault. Only the storage backends that support locking can enable Vault to run in a multi-server mode where one server is active and the others are standby. Some examples of storage backends that support high availability mode are Consul, Integrated Storage, and ZooKeeper.  Some examples of storage backends that do not support high availability mode are Filesystem, MySQL, and PostgreSQL.  References: https://developer.hashicorp.com/vault/docs/concepts/ha 1 , https://developer.hashicorp.com/vault/docs/configuration/storage 2

The policy shown in the image is:

path “secret/data/webapp1” { capabilities = [“create”, “read”, “update”, “delete”, “list”] }

path “secret/data/super-secret” { capabilities = [“deny”] }

This policy grants or denies access to the key/value v2 secrets engine mounted at secret/ according to the following rules:

The path “secret/data/webapp1” has the capabilities of “create”, “read”, “update”, “delete”, and “list”. This means that the policy allows performing any of these operations on the secrets stored under this path.  The data/ prefix is used to access the actual secret data in the key/value v2 secrets engine 5 .  Therefore, the policy permits the operation of vault kv get secret/webapp1, which reads the secret data at secret/data/webapp1 6 .

The path “secret/data/super-secret” has the capability of “deny”. This means that the policy denies performing any operation on the secrets stored under this path. The policy overrides any other policy that might grant access to this path.  Therefore, the policy does not permit the operations of vault kv delete secret/super-secret and vault kv list secret/super-secret, which delete and list the secret data at secret/data/super-secret respectively 6 .

The policy does not explicitly define any rules for the path “secret/metadata”.  The metadata/ prefix is used to access the metadata of the secrets in the key/value v2 secrets engine, such as the number of versions, the deletion status, the creation time, etc 5 .  By default, if the policy grants any of the capabilities of “create”, “read”, “update”, or “delete” on the data/ path, it also grants the same capabilities on the corresponding metadata/ path 7 .  Therefore, the policy permits the operation of vault kv metadata get secret/webapp1, which reads the metadata of the secret at secret/metadata/webapp1 8 .

The Vault Agent stores its cache in memory, which means that it does not persist the cached tokens and secrets to disk or any other storage backend. This makes the cache more secure and performant, as it avoids exposing the sensitive data to potential attackers or unauthorized access. However, this also means that the cache is volatile and will be lost if the agent process is terminated or restarted. To mitigate this, the agent can optionally use a persistent cache file to restore the tokens and leases from a previous agent process. The persistent cache file is encrypted using a key derived from the agent’s auto-auth token and a nonce, and it is stored in a user-specified location on disk. References:  Caching - Vault Agent | Vault | HashiCorp Developer ,  Vault Agent Persistent Caching | Vault | HashiCorp Developer

The statement is true. HCP Vault Dedicated uses namespaces, and the customer-accessible top-level namespace is admin. This is a critical operational difference from many self-managed Vault examples, where commands often assume the root namespace. In HCP Vault Dedicated, requests must target the admin namespace, either by setting the namespace in the CLI, passing the X-Vault-Namespace: admin API header, or using admin in the API path. If the namespace is omitted, requests may be sent to the root namespace, which is reserved for platform operations and not accessible to the customer. HashiCorp’s HCP Vault Dedicated documentation states that the top-level namespace is admin and that HCP clusters include the admin namespace by default.

================

Rekeying is used when the unseal or recovery key custody model must change. If a keyholder joins or leaves the organization, the existing shares should no longer be trusted as the active quorum, so rekeying creates a new set of key shares and can change the threshold. A compliance requirement to refresh the key material used to reconstruct the root key is also a valid rekey driver. Adding more Vault nodes does not require rekeying because storage clustering and seal key custody are separate concerns. Upgrading editions does not inherently require new key shares. If the root token is lost, the proper operation is root-token generation using a quorum, not rekeying. HashiCorp documents vault operator rekey as the command that generates a new set of unseal keys and can change key shares or threshold.

================

The payload.json file that has the correct contents is C. This file contains a JSON object with a single key, “plaintext”, and a value that is the base64-encoded string of the data to be encrypted.  This is the format that the Vault API expects for the transit encrypt endpoint 1 . The other files are not correct because they either have the wrong key name, the wrong value format, or the wrong JSON syntax.