Exercise 2: The Shared Assumption This Course Exists to Question — Possible Solution
====================================================================

THE SPECIFIC ASSUMPTION
------------------------------
Per the chapter's own comparison table, every one of the other seven
courses assumes, in its own way, that the underlying data is
fundamentally intact and recoverable once a problem is found -
netdiag1 assumes "the data behind [a reachable service] is intact,"
appdiag1 assumes "the application's own data store is intact, just
misbehaving," incident1 assumes "there's something recoverable to fix"
once identified. Different wording, same underlying premise: whatever
went wrong, the data itself survived and can be gotten back to a
working state.

WHY THIS COURSE SPECIFICALLY TARGETS THAT ASSUMPTION
------------------------------
Every other course's own diagnostic and process skills - reading logs,
tracing a connection, classifying an incident - only matter if there's
genuinely something left to recover once the diagnosis is done. This
course questions the premise sitting underneath all of them: that the
data survived in a form the organization can actually get back.

WHY IT CAN'T ALWAYS BE TRUSTED
------------------------------
Per this chapter's own central claim, an organization can have backup
jobs running and reporting success for months or years without that
success status ever proving the data inside them is actually
restorable. Unlike the other assumptions, which are usually true and
occasionally false in an obvious way, this one can be silently false
for a long time with no visible symptom at all - until the moment a
restore is actually attempted and fails.

WHY THIS IS THE WORST KIND OF ASSUMPTION TO GET WRONG
------------------------------
Per the chapter's own framing, this specific failure mode "is only
discovered at the exact moment [an organization] can least afford to:
in the middle of an actual disaster" - unlike most of the other
courses' own assumptions, which fail in ways that are at least visible
in advance, an unverified backup's failure is invisible until the
single moment it's needed most.

WHY THIS WORKS AS AN ANSWER
------------------------------
It identifies the shared underlying assumption across the other seven
courses (the data survived and is recoverable), explains why this
course targets exactly that premise, and explains why it's
particularly dangerous - it can be silently wrong for a long time with
no visible symptom until the worst possible moment.