nerdexam
HashiCorp

VAULT-ASSOCIATE-002 · Question #14

To make an authenticated request via the Vault HTTP API, which header would you use?

The correct answer is A. The X-Vault-Token HTTP Header. Authenticated requests to the Vault HTTP API require including the X-Vault-Token HTTP header, which carries the client's authentication token.

Submitted by chen.hong· Apr 18, 2026Operate Vault

Question

To make an authenticated request via the Vault HTTP API, which header would you use?

Options

  • AThe X-Vault-Token HTTP Header
  • BThe HTTP Header
  • CThe Content-Type HTTP Header
  • DThe X-Vault-Namespace HTTP Header

How the community answered

(25 responses)
  • A
    88% (22)
  • B
    8% (2)
  • D
    4% (1)

Why each option

Authenticated requests to the Vault HTTP API require including the `X-Vault-Token` HTTP header, which carries the client's authentication token.

AThe X-Vault-Token HTTP HeaderCorrect

For authenticated requests to the Vault HTTP API, clients must include their Vault token in the `X-Vault-Token` HTTP header to prove their identity and authorize their actions against Vault.

BThe HTTP Header

The 'HTTP Header' is too generic and not a specific header name for authentication.

CThe Content-Type HTTP Header

The `Content-Type` HTTP Header specifies the media type of the resource being sent (e.g., application/json) but is not used for authentication.

DThe X-Vault-Namespace HTTP Header

The `X-Vault-Namespace` HTTP Header is used to specify the namespace for the request in Vault Enterprise, not for authentication.

Concept tested: Vault HTTP API authentication, X-Vault-Token

Source: https://developer.hashicorp.com/vault/api-docs#authentication

Topics

#Vault API#Authentication#HTTP Headers#Tokens

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full VAULT-ASSOCIATE-002 Practice