Exercise 1: The Two Problems Aggregation Solves — Possible Solution
====================================================================

PROBLEM ONE: SCALE
------------------------------
Per this chapter, "checking one server's logs by hand is fine. Checking
the same thing across dozens or hundreds of servers, one at a time,
isn't - the time cost alone makes it impractical during an active
incident." As the number of servers grows, manually SSH-ing into each
one and searching its logs individually takes proportionally longer,
until it's no longer realistic to do during a live investigation.

PROBLEM TWO: EPHEMERALITY
------------------------------
Per this chapter, "in containerized and cloud environments, individual
containers or instances are routinely destroyed and replaced rather
than kept running indefinitely. A log that only exists on a container
that no longer exists is a log that's gone permanently." Even with
unlimited time to check every server, a server/container that has
already been destroyed can no longer be checked at all - the evidence
is simply gone, regardless of how much time is available.

WHY "JUST SSH INTO EACH SERVER" FAILS BOTH
------------------------------
Per this chapter, SSH-ing into each server assumes both that there
are few enough servers to check individually in reasonable time, and
that every server being checked still exists to SSH into. Scale
breaks the first assumption; ephemerality breaks the second - and
either one alone is enough to make the manual approach stop working.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly names and explains both distinct problems (scale and
ephemerality) using this chapter's own language, and correctly
explains why manual per-server checking fails against each one
separately, not just in combination.