VA-003 Utilize Vault CLI and API Practice Question
An admin wants to list all enabled authentication methods using the Vault API. Which curl command is correct?
⚠ Common exam trap
HashiCorp often tests the exact API endpoint path and HTTP method, so the trap here is confusing the `/v1/sys/auth` endpoint with the non-existent `/v1/sys/auths` or the incorrect `/v1/auth` path, or assuming a POST request is needed when a GET is correct.
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
✓
curl -H "X-Vault-Token: s.abc123" https://vault.example.com:8200/v1/sys/auth
The Vault API endpoint to list all enabled authentication methods is a GET request to `/v1/sys/auth`. This endpoint returns a map of all enabled auth methods, and the command uses the correct HTTP method (GET) and the required `X-Vault-Token` header for authentication.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
curl -H "X-Vault-Token: s.abc123" https://vault.example.com:8200/v1/sys/auths
Why it's wrong here
The endpoint is sys/auth, not sys/auths; the trailing s returns a 404. It is tempting because pluralising matches how other list endpoints read, but Vault's API defines the singular path, so the request fails despite the correct verb and header.
- ✓
curl -H "X-Vault-Token: s.abc123" https://vault.example.com:8200/v1/sys/auth
Why this is correct
Listing enabled auth methods requires a GET to the sys/auth endpoint with a valid X-Vault-Token header. This command supplies the token and targets the correct path, satisfying the requirement to enumerate all enabled authentication methods through the Vault API.
- ✗
curl -X POST -H "X-Vault-Token: s.abc123" https://vault.example.com:8200/v1/sys/auth
Why it's wrong here
POST to sys/auth attempts to mount or configure an auth method, and listing enabled methods requires GET on that same path. It is tempting because sys/auth is the correct endpoint, but the HTTP verb is wrong for a read operation.
- ✗
curl -H "X-Vault-Token: s.abc123" https://vault.example.com:8200/v1/auth
Why it's wrong here
The path /v1/auth does not exist in Vault's API; enabled auth methods are enumerated at sys/auth. It is tempting because the path resembles the auth namespace, but omitting the sys/ prefix returns a 404 rather than the method list.
Go deeper
Related to this question
About these practice questions
This VA-003 question is part of Courseiva's 366-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.