- A
GET /v1/auth/userpass/login/jdoe with header "password: p@ssw0rd"
Why wrong: Incorrect; login requires POST and password in body.
- B
PUT /v1/auth/userpass/login/jdoe with JSON body {"password":"p@ssw0rd"}
Why wrong: Incorrect; login endpoint uses POST, not PUT.
- C
POST /v1/auth/userpass/login/jdoe?password=p@ssw0rd
Why wrong: Incorrect; password should be in request body, not query parameter.
- D
POST /v1/auth/userpass/login/jdoe with JSON body {"password":"p@ssw0rd"}
Correct; standard userpass login API call.
Quick Answer
The correct API endpoint is POST /v1/auth/userpass/login/jdoe with a JSON body of {"password":"p@ssw0rd"}. This is because the userpass auth method in Vault requires a POST request to the login path that includes the username as the final path segment, and the password must be sent as the sole key in the request body—no username is included in the JSON since it is already part of the URL. On the HashiCorp Vault Associate VA-003 exam, this question tests your understanding of authentication API patterns, specifically that userpass login endpoints follow the structure /v1/auth/<mount>/login/<username> and that the password is the only required field in the payload. A common trap is confusing this with the user creation endpoint, which uses a different path and requires additional fields like policies. Remember the memory tip: "Userpass login puts the user in the URL and the password in the payload."
VA-003 Utilize Vault CLI and API Practice Question
This VA-003 practice question tests your understanding of utilize vault cli and api. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A user wants to log in using the userpass auth method with username 'jdoe' and password 'p@ssw0rd'. What is the correct API endpoint and request?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
POST /v1/auth/userpass/login/jdoe with JSON body {"password":"p@ssw0rd"}
The userpass auth method in Vault requires a POST request to the login endpoint with the password provided in the JSON body. Option D correctly uses POST /v1/auth/userpass/login/jdoe with {"password":"p@ssw0rd"}, which matches the Vault API specification for authenticating against a userpass backend.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
GET /v1/auth/userpass/login/jdoe with header "password: p@ssw0rd"
Why it's wrong here
Incorrect; login requires POST and password in body.
- ✗
PUT /v1/auth/userpass/login/jdoe with JSON body {"password":"p@ssw0rd"}
Why it's wrong here
Incorrect; login endpoint uses POST, not PUT.
- ✗
POST /v1/auth/userpass/login/jdoe?password=p@ssw0rd
Why it's wrong here
Incorrect; password should be in request body, not query parameter.
- ✓
POST /v1/auth/userpass/login/jdoe with JSON body {"password":"p@ssw0rd"}
Why this is correct
Correct; standard userpass login API call.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
HashiCorp often tests the misconception that authentication requests can use GET or PUT methods or pass credentials in headers or query parameters, when Vault strictly requires POST with a JSON body for login endpoints.
Detailed technical explanation
How to think about this question
Under the hood, Vault's userpass auth method validates credentials by hashing the provided password and comparing it to the stored hash in the backend. The POST request must include the password in the JSON body to ensure it is transmitted securely over TLS, avoiding exposure in logs or URLs. In real-world scenarios, this endpoint is often used with tools like curl or Vault's CLI, which automatically construct the correct POST request.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the VA-003 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Utilize Vault CLI and API — study guide chapter
Learn the concepts, then practise the questions
- →
Utilize Vault CLI and API practice questions
Targeted practice on this topic area only
- →
All VA-003 questions
514 questions across all exam domains
- →
HashiCorp Vault Associate VA-003 study guide
Full concept coverage aligned to exam objectives
- →
VA-003 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related VA-003 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Compare authentication methods practice questions
Practise VA-003 questions linked to Compare authentication methods.
Assess Vault tokens practice questions
Practise VA-003 questions linked to Assess Vault tokens.
Create Vault policies practice questions
Practise VA-003 questions linked to Create Vault policies.
Manage Vault leases practice questions
Practise VA-003 questions linked to Manage Vault leases.
Compare and configure secrets engines practice questions
Practise VA-003 questions linked to Compare and configure secrets engines.
Utilize Vault CLI and API practice questions
Practise VA-003 questions linked to Utilize Vault CLI and API.
Explain Vault architecture practice questions
Practise VA-003 questions linked to Explain Vault architecture.
Explain encryption as a service practice questions
Practise VA-003 questions linked to Explain encryption as a service.
VA-003 fundamentals practice questions
Practise VA-003 questions linked to VA-003 fundamentals.
VA-003 scenario practice questions
Practise VA-003 questions linked to VA-003 scenario.
VA-003 troubleshooting practice questions
Practise VA-003 questions linked to VA-003 troubleshooting.
Practice this exam
Start a free VA-003 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this VA-003 question test?
Utilize Vault CLI and API — This question tests Utilize Vault CLI and API — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: POST /v1/auth/userpass/login/jdoe with JSON body {"password":"p@ssw0rd"} — The userpass auth method in Vault requires a POST request to the login endpoint with the password provided in the JSON body. Option D correctly uses POST /v1/auth/userpass/login/jdoe with {"password":"p@ssw0rd"}, which matches the Vault API specification for authenticating against a userpass backend.
What should I do if I get this VA-003 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More VA-003 practice questions
- Refer to the exhibit. A developer reports that a token they created using `vault token create -policy=my-policy -ttl=2h`…
- A company uses Vault to manage database credentials for a production PostgreSQL cluster. The application team reports th…
- An administrator runs the commands shown in the exhibit. Later, they run 'vault kv delete kv-v2/secret' and then 'vault…
- A security administrator notices that a Vault client using AppRole authentication is generating a very large number of t…
- Which TWO statements correctly describe differences between AppRole and Kubernetes authentication methods?
- An administrator wants to use Vault's authentication method that allows users to log in with their corporate credentials…
Last reviewed: Jun 30, 2026
This VA-003 practice question is part of Courseiva's free HashiCorp certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the VA-003 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.