Exercise 1: Why a Load Average of 8 Could Be Either Normal or a Problem — Possible Solution
====================================================================

THE MISSING PIECE OF INFORMATION
------------------------------
Per this chapter, "a load average of 8 means something completely
different on a 4-core machine than on a 16-core one - the raw number
is meaningless without knowing how many cores are actually available
to share the work." The required piece of information is the
machine's core count.

WHY CORE COUNT CHANGES THE INTERPRETATION SO MUCH
------------------------------
Per this chapter's own table, dividing load average by core count
tells you what it actually means: well under 1.0 per core is
"comfortably idle," around 1.0 is "fully utilized, but not yet
queueing," and well over 1.0 is "genuinely overloaded." A load average
of 8 divided by 4 cores is about 2.1 per core (genuinely overloaded);
the same load average of 8 divided by 16 cores is only 0.5 per core
(comfortably idle) - two completely opposite conclusions from the
identical raw number.

THE CHAPTER'S OWN WORKED EXAMPLE
------------------------------
Per this chapter, the 4-core example machine's load average of 8.42
works out to "roughly 2.1 per core... a genuine, meaningful overload
signal, not a false alarm" - directly demonstrating why the bare
number 8.42 needed the core count before it could be judged either way.

WHY THIS WORKS AS AN ANSWER
------------------------------
It identifies core count as the specific missing information, explains
using the chapter's own table why dividing by it changes the
conclusion, and applies the chapter's own numeric example rather than
just asserting "context matters" without specifying what context.