Pass the HashiCorp Security Automation Certification HCVA0-003 Questions and answers with ExamsMirror

A dynamic secret is generated by Vault when requested and is normally tied to a lease, TTL, and revocation lifecycle. This is different from a static KV secret, which is manually stored and later retrieved from Vault. Dynamic secrets are commonly used for databases, cloud providers, SSH, and similar systems because Vault can create short-lived credentials and revoke them automatically when the lease expires. Option A describes KV v2 static versioned storage, not dynamic generation. Option C describes a password rotation policy, not Vault’s dynamic secret model. Option D incorrectly suggests secrets update encryption algorithms. HashiCorp’s database secrets engine documentation states that Vault dynamically generates database credentials, and Vault lease documentation explains that dynamic secrets are managed through lease IDs and TTLs.

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

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 endpoint 1 2 .

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 hierarchy 3 .

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 revoked 4 .

The Vault CLI command to query information about the token the client is currently using is vault token lookup. This command displays information about the token or accessor provided as an argument, or the locally authenticated token if no argument is given. The information includes the token ID, accessor, policies, TTL, creation time, and metadata. This command can be useful for debugging and auditing purposes, as well as for renewing or revoking tokens. References:  token lookup - Command | Vault | HashiCorp Developer ,  Tokens | Vault | HashiCorp Developer

Vault authentication produces a client token, and non-root tokens normally have a time-to-live. If the token is not renewed before its TTL expires, Vault revokes the token and its associated leases, forcing the user to authenticate again. In this scenario, the repeated eight-hour login cycle indicates that the LDAP-authenticated token has an eight-hour effective TTL or auth lease. The issue is not caused by entering the wrong token repeatedly, because that is not how Vault normally handles LDAP login expiration. Revoking the root token would not directly force all LDAP users to reauthenticate every eight hours. A changed LDAP password could cause failed authentication, but it would not explain a predictable reauthentication interval. HashiCorp documents that auth identities have leases and non-root tokens stop functioning after their TTL expires.

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

The transit secrets engine is not a good solution for binaries of this size, because it is designed to handle cryptographic functions on data in-transit, not data at-rest. The transit secrets engine does not store any data sent to it, so it would require sending the entire 2GB blob to Vault for encryption or decryption, which would be inefficient and impractical. A better solution would be to use the transit secrets engine to generate a data key, which is a high-entropy key that can be used to encrypt or decrypt data locally. The data key can be returned in plaintext or wrapped by another key, depending on the use case. This way, the transit secrets engine only handles the encryption or decryption of the data key, not the data itself, and the data can be stored in any primary data store. References:  Transit - Secrets Engines | Vault | HashiCorp Developer ,  Encryption as a service: transit secrets engine | Vault | HashiCorp Developer

The vault lease operations that use a lease_id as an argument are renew and revoke. The renew operation allows a client to extend the validity of a lease associated with a secret or a token. The revoke operation allows a client to terminate a lease immediately and invalidate the secret or the token. Both operations require a lease_id as an argument to identify the lease to be renewed or revoked. The lease_id can be obtained from the response of reading a secret or creating a token, or from the vault lease list command. The other operations, revoke-prefix, create, and describe, do not use a lease_id as an argument. The revoke-prefix operation allows a client to revoke all secrets or tokens generated under a given prefix. The create operation allows a client to create a new lease for a secret. The describe operation allows a client to view information about a lease, such as its TTL, policies, and metadata. References:  Lease, Renew, and Revoke | Vault | HashiCorp Developer ,  vault lease - 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

The vault lease renew command increments the lease time from the current time, not the end of the lease. This means that the user can request a specific amount of time they want remaining on the lease, termed the increment. This is not an increment at the end of the current TTL; it is an increment from the current time. For example, vault lease renew -increment=3600 my-lease-id would request that the TTL of the lease be adjusted to 1 hour (3600 seconds) from now. Having the increment be rooted at the current time instead of the end of the lease makes it easy for users to reduce the length of leases if they don’t actually need credentials for the full possible lease period, allowing those credentials to expire sooner and resources to be cleaned up earlier. The requested increment is completely advisory.  The backend in charge of the secret can choose to completely ignore it 1 .  References :

Lease, Renew, and Revoke | Vault | HashiCorp Developer

An identity group is a collection of entities that share some common attributes. An identity group can have one or more policies attached to it, which are inherited by all the members of the group. An identity group can also have subgroups, which can further refine the policies and attributes for a subset of entities.

One of the use cases of an identity group is to consistently apply the same set of policies to a collection of entities. For example, an organization may have different teams or departments, such as engineering, sales, or marketing. Each team may have its own identity group, with policies that grant access to the secrets and resources that are relevant to their work. By creating an identity group for each team, the organization can ensure that the entities belonging to each team have the same level of access and permissions, regardless of which authentication method they use to log in to Vault. References:  Identity: entities and groups | Vault | HashiCorp Developer ,  vault_identity_group | Resources | hashicorp/vault | Terraform | Terraform Registry

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.

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