Exercise 1: Why 429 Is a Fundamentally Different Signal — Possible Solution
====================================================================

WHAT A 429 ACTUALLY MEANS
------------------------------
Per this chapter, "a 429 Too Many Requests is the server explicitly
saying: I'm healthy, I received your request, and I'm deliberately
declining to process it right now." The server successfully received
and evaluated the request - it made a deliberate choice not to serve
it, rather than failing to handle it.

WHY THIS DIFFERS FROM A 5xx OR A TIMEOUT
------------------------------
Per this chapter, this is "a fundamentally different situation from a
5xx (the server struggling) or a timeout (the network or server
genuinely unresponsive)." A 5xx indicates something actually went
wrong while processing the request; a timeout indicates no response
came back at all. A 429 involves neither - the server is functioning
completely normally and specifically chose this outcome as designed
behavior.

WHY CONFUSING THE TWO WASTES TIME
------------------------------
Per this chapter, "recognizing a 429 immediately for what it is avoids
wasting time chasing a 'the service is down' theory when the service
is, in fact, working exactly as designed." Treating a 429 like a 5xx
or timeout would send an investigation looking for a server crash,
resource exhaustion, or network failure - none of which are the actual
cause, since the service is healthy and simply enforcing a limit.

WHY THIS WORKS AS AN ANSWER
------------------------------
It explains what a 429 specifically communicates (a deliberate,
healthy decision, not a failure), contrasts it precisely against the
other two categories, and connects the distinction to why
misidentifying it leads investigation in a genuinely wrong direction.