Challenge 2: Build a Request From a Description — Possible Solution
====================================================================

METHOD: POST
(creating a new resource — a user — matches POST, not GET, since this
sends new data to be stored rather than fetching existing data)

URL: https://api.example.com/users
(no query parameters needed — nothing here describes filtering or
selecting existing data; the actual user data belongs in the body)

HEADERS:
  Authorization: Bearer <token>
  Content-Type: application/json
(Authorization carries the bearer token exactly as described; Content-
Type tells the server the body below is JSON, per this chapter's
gotcha about that header being required for the server to parse it
correctly)

BODY (raw, JSON):
{
  "name": "Dana",
  "email": "dana@example.com"
}

WHY THIS WORKS AS AN ANSWER
------------------------------
Every piece of the description maps to exactly one part of the
request: "create a new user" -> POST + body containing the new user's
data; "with name 'Dana' and email...'" -> the two fields in that JSON
body; "authenticating with a bearer token" -> the Authorization header,
not a query parameter (credentials belong in headers, never in a URL,
where they could end up logged or cached).