Exercise 3: Why the Slow-Query Warning Wasn't the Full Answer — Possible Solution
====================================================================

WHY IT WAS TEMPTING TO TREAT AS COMPLETE
------------------------------
Per this chapter's own warning box, "the slow-query warning in Step 3
was tempting to treat as the full answer on its own - 'the database is
slow, case closed.'" It was a real, accurate finding - the database
genuinely was slow during those windows, and the warning genuinely
confirmed that.

WHY IT WAS STILL AN INCOMPLETE DIAGNOSIS
------------------------------
Per this chapter, it's true but incomplete: "without Step 4's system-
level check, the actual root cause (a misconfigured cron schedule)
would have stayed hidden." The database slowness was a real symptom,
but not the root cause - it was itself caused by the hourly cron job
driving up system load, which the error log alone never showed.

WHAT WOULD HAVE GONE WRONG IF THIS WERE TREATED AS FINAL
------------------------------
Per this chapter, "any fix attempted at the database layer alone would
likely have missed the real trigger entirely" - for example, tuning or
optimizing the database query itself would not have addressed the
actual problem (the cron job firing hourly instead of nightly), and
the slowness would likely have recurred on the same schedule regardless
of any database-level changes made.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that the slow-query warning was accurate but
represented a symptom rather than the root cause, and correctly
identifies the real risk of stopping there - fixing the wrong layer
and missing the actual trigger the system-level log alone revealed.