HCVA0-003 Practice Questions

Comprehensive and Detailed In-Depth Explanation:

Vault supports multiple auth methods by default. The Vault documentation states:

" Auth methods are the components in Vault that perform authentication and are responsible for assigning identity and a set of policies to a user. Available auth methods include AppRole, JWT/OIDC, Kubernetes, LDAP, and more. "

— Vault Auth Methods

B : Kubernetes is supported:

" Kubernetes authentication method in Vault allows Kubernetes service accounts to authenticate with Vault. "

— Vault Auth: Kubernetes

D : LDAP is supported:

" LDAP authentication method allows users to authenticate against an LDAP directory. "

— Vault Auth: LDAP

E : AppRole is supported:

" AppRole authentication method in Vault allows machines or applications to authenticate with Vault. "

— Vault Auth: AppRole

F : JWT is supported:

" JWT authentication method in Vault allows users to authenticate using JSON Web Tokens (JWT). "

— Vault Auth: JWT

A : SSH is a secrets engine, not an auth method.

C : VMware is not a default auth method.

Comprehensive and Detailed In-Depth Explanation:

To store static credentials in Vault’s KV secrets engine via CLI, the vault kv put command is used.

A : vault kv put kv/training/certification/vault @secrets.txt writes data from a file (secrets.txt) to the path kv/training/certification/vault. The @ syntax reads key-value pairs from the file, a valid method per the KV docs.

D : vault kv put -mount=secret creds passcode=my-long-passcode specifies the mount (secret/) and stores passcode=my-long-passcode at secret/creds, a correct inline syntax.

B : vault kv write isn’t a valid command; put is the correct verb. The key=value syntax is right but needs put.

C : vault kv create isn’t a command; put is used to create or update secrets.

The KV CLI docs confirm vault kv put as the standard method, supporting both file input and inline key-value pairs.

Comprehensive and Detailed In-Depth Explanation:

After authenticating with the Kubernetes auth method, Vault returns a token that must be included in subsequent API requests to retrieve dynamic credentials. The Vault documentation specifies two valid HTTP headers for this purpose:

" Once authenticated, most Vault operations require a client token to be set either via the X-Vault-Token header or via the Authorization header using the Bearer type. For example:

X-Vault-Token: < token >

Authorization: Bearer < token > " — Vault API Documentation: Authentication

A : X-Vault-Token: < token > is the primary Vault-specific header for token authentication:

" The X-Vault-Token header is used to specify the token when requesting dynamic credentials from Vault. This header is commonly used to authenticate and authorize requests to Vault services. "

— Vault API Documentation

D : Authorization: Bearer < token > is a standard HTTP authentication header supported by Vault:

" The Authorization header with the Bearer token format is another common way to specify the token when requesting dynamic credentials from Vault. This header is widely used for authentication purposes in HTTP requests. "

— Vault API Documentation

B : Token: < token > is not a recognized Vault header.

C : Authentication: < token > is not a standard or supported header in Vault; the correct header is Authorization.

These headers ensure the token is passed securely to Vault for authorizing credential requests.