Exercise 2: Durability vs. Availability, With a Real Scenario — Possible Solution
====================================================================

Durability answers "will this object still exist, unchanged, if I
come back for it later" -- S3's own real 11-nines figure describes
how vanishingly unlikely permanent data loss is, given that S3
automatically maintains redundant copies across multiple real
facilities. Availability answers a genuinely different question: "can
I successfully reach and retrieve this object RIGHT NOW."

An object can be perfectly durable (every redundant copy of it is
intact, and it will never actually be lost) while still being
temporarily unavailable -- for example, during a brief real service
disruption, a network issue on the requesting end, or a short
maintenance window affecting the specific endpoint being used to
request it. In every one of these cases, the object itself is never
at risk of loss; a request for it might simply fail or time out until
the temporary issue clears.

ANSWER: Durability measures the real, long-term safety of the data
itself; availability measures whether you can successfully access it
at a specific moment. A real scenario where they diverge: a genuine,
brief network or service interruption preventing successful requests
for a short period, while every underlying copy of the actual object
remains completely intact and unaffected -- 11-nines durability was
never actually threatened, even though a request might have failed at
that specific moment.

WHY THIS WORKS AS AN ANSWER
------------------------------
This correctly separates "the data is safe" from "the data is
reachable right now" as two independent real properties, rather than
treating "11 nines" as a blanket uptime guarantee -- exactly the
distinction the chapter's own text draws explicitly, since conflating
the two is a common, real misunderstanding of what S3's durability
figure actually promises.