Exercise 2: 404 vs. 500 — Which One Actually Matters — Possible Solution
====================================================================

WHICH ONE IS MORE LIKELY A GENUINE SERVER-SIDE PROBLEM
------------------------------
Per this chapter, the 500 status is the one worth real investigation,
not the 404.

WHY, ACCORDING TO THIS CHAPTER'S OWN CATEGORIES
------------------------------
Per this chapter's status code table, 4xx codes (including 404) are
"client error - the request itself was the problem," while 5xx codes
(including 500) are "server error - the server failed to handle a
valid request." A 404 typically means the client asked for something
that doesn't exist - not that the server malfunctioned in any way.
The chapter states directly: "a spike in 404s often means a broken
link or a bot scanning for pages that don't exist - rarely a real
system problem."

WHY 500 IS DIFFERENT
------------------------------
Per this chapter, a 5xx code means the server itself failed to handle
what was otherwise a legitimate request - something actually broke on
the server's own side, not in what the client asked for. The chapter
explicitly ties a "spike in 5xx codes" to "the kind of signal Chapters
6 and 7 build a full diagnostic process around" - marking it as the
category that genuinely warrants investigation.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly identifies 500 as the status worth investigating,
correctly applies this chapter's own 4xx-vs-5xx category distinction
(client-side problem vs. server-side failure) to explain why, rather
than treating both codes as equally concerning simply because both
represent "an error."