Exercise 2: High Load + High wa — Why That's Not a CPU Problem — Possible Solution
====================================================================

WHAT wa SPECIFICALLY MEASURES
------------------------------
Per this chapter, wa ("iowait") means "the CPU is idle, but specifically
because it's waiting on a disk (or other I/O) operation to finish, not
because there's no work." A high wa figure means the CPU has nothing
to actively process right now precisely because it's stuck waiting on
something else to respond.

WHY A HIGH LOAD AVERAGE PLUS HIGH wa ISN'T A CPU PROBLEM
------------------------------
Per this chapter's finding-box, "on Linux, a process waiting on disk
I/O... counts toward load average too... a high load average doesn't
necessarily mean the CPU is the bottleneck at all." A high load average
combined with high wa specifically confirms that the processes counted
in the load average are mostly waiting on I/O, not competing for
actual CPU execution time - the CPU itself may be sitting comparatively
idle underneath a high load number.

WHERE THE REAL EVIDENCE WOULD ACTUALLY BE
------------------------------
Per this chapter's tip-box, "if a system shows a high load average
alongside a high wa figure, the CPU itself usually isn't the actual
bottleneck... the real evidence lives in disk I/O metrics instead" -
pointing directly to Chapter 4's own disk I/O material rather than
searching for a CPU-hungry process that isn't actually the cause.

WHY THIS WORKS AS AN ANSWER
------------------------------
It defines wa accurately, explains specifically why it changes the
interpretation of an otherwise-alarming load average using the
chapter's own load-average-includes-I/O-waits finding, and correctly
redirects the investigation to disk I/O rather than continuing to
search inside CPU-specific metrics.