200-901 Understanding and Using APIs Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Accept

  Why it's wrong here

  Accept tells the server which response media types the client can handle; it does not describe the request payload. It tempts because it names a media type, and would be correct when negotiating the format of the returned representation, such as requesting application/json from an endpoint.

• ✓

  Content-Type

  Why this is correct

  Content-Type specifies the media type of the request body, such as application/json, so the server knows how to parse the POST payload. Accept instead describes the desired response format, so Content-Type satisfies the requirement to declare the body's format.

• ✗

  Authorization

  Why it's wrong here

  Authorization carries credentials such as a bearer token for authenticating the caller, not the body's media type. Content-Type declares application/json. Authorization is tempting because POST requests to secured APIs usually include it, but it would be the right header only when the API requires proof of identity or permissions.

• ✗

  X-Requested-With

  Why it's wrong here

  X-Requested-With identifies AJAX requests, typically carrying XMLHttpRequest, so it conveys nothing about body media type. Content-Type is the header that declares application/json. X-Requested-With is tempting because frameworks use it to detect asynchronous calls, but it would only be correct when a server must distinguish AJAX from full-page requests.

Go deeper

Related to this question