Exercise 1: Transient Spike vs. Sustained Trend — Possible Solution
====================================================================

THE CHAPTER'S OWN DEFINING DISTINCTION
------------------------------
Per this chapter, "a genuine sustained trend looks different from a
transient spike in one specific way: it doesn't fully return to where
it started." A transient spike, however dramatic while it's happening,
comes back down to its previous normal level once the triggering
event ends. A sustained trend does not return to that same starting
point.

EXAMPLES OF EACH, PER THIS CHAPTER
------------------------------
Transient: "application startup..., a scheduled batch job, a genuine
burst of real traffic..., and... garbage collection pauses" - all
resolve on their own once the triggering event (startup completing, the
batch job finishing, the traffic burst passing, GC finishing a cycle)
is over. Sustained: "organic growth (more real users, more real data...)
or a resource leak (a bug causing gradual, unbounded consumption that's
never actually released, even during quiet periods when load is low)."

WHY "RETURNS TO WHERE IT STARTED" IS THE ACTUAL TEST
------------------------------
The test isn't how big or dramatic a spike looks at its peak - a
transient spike can be just as tall as the early stage of a real trend.
What separates them is what happens afterward: does the metric settle
back to its previous baseline, or does it settle at a new, higher
baseline than before.

WHY THIS WORKS AS AN ANSWER
------------------------------
It states the chapter's own specific defining test (return to
starting point or not) rather than a vague size-based distinction, and
supports it with the chapter's own named examples of each category.