Exercise 1: Why a Morning-After top Check Can Show Nothing Unusual — Possible Solution
====================================================================

WHAT top's DEFAULT VIEW ACTUALLY SHOWS
------------------------------
Per this chapter's warn-box, "top's default view shows a single
moment." Whatever top displays reflects only the exact instant it was
run - it has no memory of anything that happened before that moment.

WHY A REAL OVERNIGHT SPIKE WOULDN'T APPEAR THE NEXT MORNING
------------------------------
Per this chapter, "a process that spiked CPU heavily for a short burst
and finished (or dropped back down) before anyone happened to look
won't appear as a top consumer in a snapshot taken afterward - even
though it was the actual cause of a preceding slowdown." If the spike
occurred overnight and the responsible process has since finished or
returned to normal activity by the time someone checks the following
morning, there is nothing left in a live snapshot to reveal that it
ever happened.

THE PARALLEL TO CHAPTER 7
------------------------------
Per this chapter, this is "the exact same underlying problem as
Chapter 7's own averaging gotcha, applied to process attribution
instead of a dashboard graph: a brief, severe event can be invisible
to a check that only looks at 'right now.'" Both a dashboard average
and a live top snapshot summarize or represent only a limited slice of
time, and both can fail to show a real event that happened outside
that slice.

WHY THIS WORKS AS AN ANSWER
------------------------------
It explains specifically what a single top snapshot does and doesn't
capture, connects that limitation to why an overnight spike wouldn't
still be visible the next morning, and draws the chapter's own
explicit parallel to Chapter 7's averaging problem rather than treating
the two as unrelated.