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

To make an authenticated request via the Vault HTTP API, you need to use the X-Vault-Token HTTP Header or the Authorization HTTP Header using the Bearer < token > scheme. The token is a string that represents your identity and permissions in Vault. You can obtain a token by using an authentication method, such as userpass, approle, aws, etc. The token can also be a root token, which has unlimited access to Vault, or a wrapped token, which is a response-wrapping token that can be used to unwrap the actual token. The token must be sent with every request to Vault that requires authentication, except for the unauthenticated endpoints, such as sys/init, sys/seal-status, sys/unseal, etc.  The token is used by Vault to verify your identity and enforce the policies that grant or deny access to various paths and operations. References: https://developer.hashicorp.com/vault/api-docs 3 , https://developer.hashicorp.com/vault/docs/concepts/tokens 4 , https://developer.hashicorp.com/vault/docs/concepts/auth 5

Vault’s default API listener port is 8200. This is the port used by Vault clients, the Vault CLI through VAULT_ADDR, and direct API calls when the listener is configured on the default address. Port 8201 is normally associated with Vault cluster communication, not the public client REST API. Port 443 is a standard HTTPS port, but it is not Vault’s default listener port unless an operator places Vault behind a proxy or custom listener configuration. Port 8500 is commonly associated with Consul’s HTTP API, not Vault. HashiCorp’s TCP listener documentation shows Vault listening at 127.0.0.1:8200, and the dev server documentation also confirms TCP port 8200 as the default listener port.

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

Sealing Vault is an administrative operation performed against the /sys/seal endpoint or by using the equivalent operator command. It does not require Shamir unseal keys, because those are used to unseal Vault, not to seal it. It also does not require the root key to be manually supplied. A quorum or threshold of key holders is needed for unsealing in Shamir mode, but sealing is a different action. The best answer is a single operator with sufficient root-level privilege, meaning a token with the root policy or the required sudo capability on the seal path. HashiCorp’s /sys/seal API documentation states that sealing requires a token with the root policy or sudo capability on the path.

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

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

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.

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

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

This is a templated ACL policy using {{identity.entity.id}}. The template dynamically resolves to the authenticated entity’s unique Vault identity ID. Because the paths are under secret/data/ and secret/metadata/, this is written for a KV version 2 secrets engine, where data and metadata are addressed separately. The policy grants each entity create, update, read, and delete permissions under its own data path, plus list permission under its own metadata path. That means every user or client mapped to a Vault entity receives access to a folder matching its entity ID, without requiring a manually written policy for each person. This is not a special system entity folder; it is identity-based path templating. HashiCorp documents ACL templating for user-specific KV paths.

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

Vault authentication methods are enabled with the vault auth enable command. Since the required authentication method is AppRole, the correct command is vault auth enable approle. AppRole is designed for machine and application authentication, where a workload authenticates using a RoleID and SecretID pattern. Option B is invalid modern Vault syntax; vault mount is not the command used to enable auth methods. Option C is also incorrect because mount enable is not the proper command structure. Option D is incomplete and does not specify the auth command group. HashiCorp’s AppRole and operations quick-start documentation show AppRole being enabled with vault auth enable approle, which directly matches option A.

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

When unsealing Vault, each Shamir unseal key should be entered by different administrators each connecting from different computers. This is because the Shamir unseal keys are split into shares that are distributed to trusted operators, and no single operator should have access to more than one share. This way, the unseal process requires the cooperation of a quorum of key holders, and enhances the security and availability of Vault. The unseal keys can be entered via multiple mechanisms from multiple client machines, and the process is stateful. The order of the keys does not matter, as long as the threshold number of keys is reached. The unseal keys should not be entered at the command line in one single command, as this would expose them to the history and compromise the security.  The unseal keys should not be encrypted with each administrator’s PGP key, as this would prevent Vault from decrypting them and reconstructing the master key.  References: https://developer.hashicorp.com/vault/docs/concepts/seal 3 , https://developer.hashicorp.com/vault/docs/commands/operator/unseal

AppRole is the correct choice for the on-premises CI/CD targets because it is designed for machine and application authentication. AWS auth is appropriate for AWS workloads because Vault can validate AWS identity metadata, but it does not naturally authenticate vSphere-based on-premises workloads. GitHub auth is mainly user/team oriented and tied to GitHub identity, not a generic CI/CD machine identity pattern. Userpass requires a username and password and is generally unsuitable for automated pipelines because it encourages static credential handling. AppRole uses a RoleID and SecretID model, allowing controlled authentication for services, automation, and pipelines that do not have a native cloud identity provider. HashiCorp’s AppRole documentation describes it as an auth method for machines and apps.

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