Challenge 3: Diagnose From Status Alone — Possible Solution
====================================================================

(a) 404 — "Not Found." Before opening the body at all, this already
says the problem is almost certainly the URL itself (a wrong path, a
typo, a resource ID that doesn't exist) rather than anything wrong
with the request's headers or body. Look at the URL first.

(b) 401 — "Unauthorized." This says the request never got far enough
to even be evaluated against the actual data — authentication itself
failed or is missing. Look at the Authorization header first (missing
token, expired token, wrong format like forgetting the "Bearer "
prefix) before suspecting anything about the body or business logic.

(c) 500 — "Internal Server Error." This says the problem is on the
SERVER's side, not a mistake in how the request was built — the
server accepted the request but broke while trying to handle it. This
is the one case where the client-side request itself is probably not
the place to keep looking; the next step is checking server logs, not
re-reading the request for a mistake that likely isn't there.