Exercise 1: The Clearest Signal a Complaint Is Network-Related — Possible Solution
====================================================================

THE SIGNAL, PER THIS CHAPTER
------------------------------
Per this chapter, "the single clearest signal that a symptom is
network-related rather than a local resource problem: CPU, memory, and
disk all check out clean using Chapters 2 through 5's own tools, and
the complaint persists anyway."

WHY THIS SPECIFIC COMBINATION POINTS TO NETWORK
------------------------------
Per this chapter, "a machine with plenty of spare CPU, healthy memory,
and fast disk I/O that's still 'slow' from a user's point of view is
very likely waiting on something outside itself - the network path to
it, or the network path from it to something it depends on." If none
of the three local resource categories this course has already covered
explain the symptom, the remaining explanation - by elimination - is
something outside the machine itself, which is where network
diagnosis comes in.

WHY THIS ISN'T THE SAME AS "WE COULDN'T FIND ANYTHING LOCAL"
------------------------------
This isn't a vague shrug of "nothing local looks wrong, so who knows" -
it's a positive, specific diagnostic conclusion built the same way
Chapters 2-5 taught: checking real evidence (CPU load per core, memory
availability, disk latency) and ruling each one out specifically,
rather than assuming network by default.

WHY THIS WORKS AS AN ANSWER
------------------------------
It states the exact chapter-given combination (all three local
resources checked and clean, complaint still present) and explains the
elimination logic behind why that combination specifically points to
network causes, rather than treating "nothing found locally" as an
automatic default answer.