HashiCorp Vault Associate (003) (VLT-VA003): 5 Practice Questions on Authentication methods

5 questions, one domain: Authentication methods from the HashiCorp Vault Associate (003) (VLT-VA003) exam. Pick your answer, then check it against the explanation.

VLT-VA003 Authentication methods: 5 practice questions

HashiCorp Vault Associate (003) (VLT-VA003) · Authentication methods · 5 questions with answers and explanations

🧭 Reading Authentication methods questions

Auth method items pair a type of client with an identity source and ask which method fits, or why a login fails. People with directory accounts, Kubernetes workloads and shared logins all appear. The right answer follows how Vault turns verified credentials into a token with identity and policies; wrong options often pick a method built for a different kind of client.

Three things to look for

• Start with who is logging in. Humans with existing accounts and machine workloads lead to different method families.
• When a Kubernetes login fails in one namespace only, compare the namespaces and service accounts bound to the role with the ones in use.
• Shared credentials hide who did what in audit logs. Give each person a login and share permissions through groups instead.

Question 1 of 5

Pods in the namespace demo fail to log in with the Kubernetes method, while the same service account works in namespace default. The role has bound_service_account_namespaces=default. What fixes it?

AAdd demo to the role's bound service account namespaces, or write a role that lists it
BRe-enable the auth method with -path=demo so that the namespace becomes its mount
CSet disable_local_ca_jwt on every pod so Vault ignores the namespace
DGive the pods a RoleID, since namespaces other than default need AppRole
Show answer

✅ Answer: A

Difficulty: advanced · Topic: Vault, Kubernetes

Role binding in Kubernetes auth
A Kubernetes auth role limits which service accounts may use it:
• bound_service_account_names: names of the service accounts (or *).
• bound_service_account_namespaces: namespaces the accounts must be in.
Vault accepts the login only if the JWT's service account matches both. A pod in another namespace is rejected even with the same name, so you either extend the role or write a separate role for the new namespace.
vault write auth/kubernetes/role/demo bound_service_account_names=myapp bound_service_account_namespaces=demo token_policies=app

Why each option works or fails
• ✓ A. Extend the namespace binding (correct): the failure comes from the role's namespace constraint, so the role must allow the second namespace.
• ✗ B. Mount per namespace: the mount path is unrelated to Kubernetes namespaces; roles hold the bindings.
• ✗ C. disable_local_ca_jwt: this option controls how Vault trusts the cluster CA and reviewer token and does not relax the namespace binding.
• ✗ D. Switch to AppRole: nothing in Kubernetes auth limits it to the default namespace; the role's namespace binding is the cause.

Question 2 of 5

A platform team wants developers to log in to Vault from the CLI and the UI with the accounts they already use in their corporate Active Directory. Which auth method fits best?

ALDAP, which checks passwords against the existing directory and maps its groups to policies
BUserpass, because it can import usernames and passwords from an external directory on a schedule
CAppRole, because each developer receives a RoleID and SecretID that match the directory account
DTLS certificates, because directory users sign in with a client certificate
Show answer

✅ Answer: A

Difficulty: applied · Topic: Vault

Matching the method to the identity source
The best auth method is usually the one that reuses an identity system that already exists.
• LDAP authenticates users with a directory username and password and lets Vault map LDAP users and groups to policies through its users/ and groups/ paths. No second set of passwords is created.
• Userpass keeps its own username and password list in Vault; it cannot read from an external source.
• AppRole is aimed at machines and automated workflows, not at people.
• Cert authenticates TLS client certificates that you have configured as trusted.

Why each option works or fails
• ✓ A. LDAP (correct): it integrates Vault with the existing directory so people use the credentials they already have, and group membership drives the policies they receive.
• ✗ B. Userpass import: userpass is configured directly through its users/ path and cannot read usernames or passwords from an external source.
• ✗ C. AppRole for developers: AppRole is oriented to automated workflows and is less useful for human operators; it has no link to directory accounts.
• ✗ D. TLS certificates: certificate auth trusts certificates or CAs configured in Vault, and does not look up directory accounts.

Question 3 of 5

Which TWO auth methods report the login username as the alias name for the entity Vault creates? (Select TWO)

ATLS certificates
BKubernetes
CUserpass
DAppRole
ELDAP
Show answer

✅ Answer: C, E

Difficulty: applied · Topic: Vault

What becomes the alias name
Each auth method reports a name for the entity alias, which together with the mount accessor identifies the alias.
• LDAP, userpass, Okta, RADIUS: the username.
• AppRole: the role ID.
• TLS certificate: the subject CommonName.
• Kubernetes: the service account UID by default, or the name with alias_name_source.
• GitHub: the user login name.
Knowing this explains why every process that logs in with the same AppRole shares one entity.

Why each option works or fails
• ✗ A. TLS certificates: the alias name is the subject CommonName of the client certificate, not a typed username.
• ✗ B. Kubernetes: the alias name is the service account UID by default, with the account name as an option.
• ✓ C. Userpass (correct): the alias name is the username entered at login.
• ✗ D. AppRole: the alias name is the role ID, so all logins for one role map to one alias.
• ✓ E. LDAP (correct): the alias name is the directory username.

Question 4 of 5

A new engineer asks what Vault does when a client presents credentials to an auth method such as userpass or LDAP. Which statement is accurate?

AThe auth method verifies the credentials, then Vault applies its policies to later requests using the original username each time
BThe auth method verifies the credentials, then Vault issues a token that carries the identity and the policies mapped at login
CThe auth method verifies the credentials, then Vault returns the secrets the caller is permitted to read in the same response
DThe auth method stores the credentials in the barrier, then Vault issues a lease that the client must renew to stay logged in
Show answer

✅ Answer: B

Difficulty: applied · Topic: Vault

What an auth method does
Before a client can do anything in Vault it must authenticate. An auth method is the component that performs that authentication and assigns an identity and a set of policies to the caller. Many auth methods delegate the actual decision to an external system (GitHub, LDAP, Kubernetes, a cloud provider); others, such as userpass, hold the credentials themselves.

The result is a token
On success Vault generates a token. Conceptually it is like a session ID on a website: the client sends it with every later request, and the policies attached to it at login decide what is allowed.
• The CLI attaches the token automatically after vault login.
• With the API the client must send the token itself, for example in the X-Vault-Token header.
• Secrets are not returned by login; they are read afterwards with the token.

Why each option works or fails
• ✗ A. Policies by username on each request: later requests are authorized from the token, not by re-checking the username. The username is not sent again after login.
• ✓ B. Token with identity and policies (correct): authentication verifies who the caller is, and the output is a token carrying the policies mapped at login time. Every later request is authorized from that token.
• ✗ C. Secrets in the login response: login returns only a token and its metadata. Reading secrets is a separate request that the token's policies must allow.
• ✗ D. Credentials stored with a lease to renew: the credential check is not a lease on the credentials; the token Vault returns has a TTL, and the client renews or re-authenticates when it expires. The auth method does not copy the credentials into a renewable lease.

Question 5 of 5

An audit review finds that five operators log in with the same userpass account. Which problem does this create, and what is the better design?

AThe shared account's policies are merged with each person's group policies, which grants extra access
BAudit entries name one entity for all five, so actions cannot be tied to a person; give each their own login
CVault allows one token per userpass account, so four people are locked out; raise a limit
DUserpass tokens cannot be audited, so enable the file audit device with a higher log level
Show answer

✅ Answer: B

Difficulty: advanced · Topic: Vault

Identity and the audit trail
When a client authenticates (with any method except the token method), Vault creates or reuses an entity and ties its ID to the issued token. When that token is used, the entity ID is audit logged, which gives a trail of actions by specific users.
If five people log in as one user, all of their actions map to a single entity, so the log cannot say who did what.
• Give each operator their own identity: LDAP, OIDC, or at least individual userpass entries.
• Use groups to give shared permissions to a set of entities, rather than shared credentials.

Why each option works or fails
• ✗ A. Merged group policies: a shared account has no per-person group membership, so nothing is merged; the problem is attribution.
• ✓ B. One entity for five people (correct): audit attribution is lost; individual logins plus group policies keep both attribution and shared permissions.
• ✗ C. One token per account: Vault does not limit userpass accounts to a single token.
• ✗ D. Userpass not audited: logins and requests are audited like any other; the audit log is limited by who the entity is, not by the method.

🎯 Key ideas from this set

• Kubernetes roles accept only the service account names and namespaces they list.
• For people who already have directory accounts, use LDAP so Vault reuses them instead of keeping a second password list.
• Directory and password methods use the username as alias name, while AppRole uses the role ID and cert uses the CommonName.
• An auth method verifies the caller and Vault answers with a token that holds the identity and policies for later requests.
• Individual logins keep the entity in audit logs meaningful; share permissions through groups, not credentials.

📊 Set profile

Exam: VLT-VA003 · 50 questions · 60 minutes
This set: 3 applied, 2 advanced · 2 troubleshooting, 1 comparison, 1 concept check, 1 scenario · 1 with more than one answer
Topics: Vault, Kubernetes

🔗 Related practice sets

• All VLT-VA003 practice sets
• Every exam on this blog

📚 Beyond this set

More VLT-VA003 questions: https://hyunhp.github.io/cert-bank/#exam=VLT-VA003
Study guide: https://hyunhp.github.io/cert-bank/study.html#exam=VLT-VA003

These are original practice questions, not real exam questions, and cert-bank is not affiliated with any certification vendor.

Original practice questions written for this blog, not exam dumps.

Comments