Exercise 1: Why the Surviving Backup Was Still Tested, Not Trusted Immediately — Possible Solution ==================================================================== WHY SURVIVING THE ATTACK ISN'T THE SAME AS BEING USABLE ------------------------------ The immutable backup surviving proves only that it wasn't deleted or encrypted by the ransomware - the retention lock did exactly the job Chapter 8 described. It says nothing about whether the backup itself is actually restorable, which per Chapter 1's own central claim is a completely separate question from whether a copy simply exists. Surviving an attack and being genuinely usable are two different properties, verified by two different means. WHY THIS COULD HAVE FAILED EVEN THOUGH IT SURVIVED ------------------------------ Per this capstone's own account, the restore did in fact hit a real snag - an unrecognized-format error, caused by the backup software having moved on since the copy was created. Had the team simply assumed the surviving backup would work and used it directly during the real emergency, without first confirming it, they would have discovered this problem at the worst possible moment rather than having a chance to diagnose and resolve it calmly. WHY THIS IS EXACTLY THE DISCIPLINE CHAPTER 5 BUILT ------------------------------ Per this capstone, the team "applies the same discipline Chapter 5 built for routine testing - actually restoring it to a real, isolated environment and confirming the result is genuinely usable, not just present." Chapter 5's entire argument was that only an actual attempted restore proves usability - a rule that doesn't stop applying just because the backup in question happens to be the last one standing after an attack. If anything, the stakes of skipping that verification are higher here, not lower. WHY SKIPPING THIS STEP WOULD HAVE BEEN A NATURAL BUT DANGEROUS SHORTCUT ------------------------------ Under the pressure of an active ransomware incident, the instinct to treat "it's the only copy left" as equivalent to "it must work" is understandable - but per this course's own recurring theme, that substitutes hope for verification at exactly the moment verification matters most. WHY THIS WORKS AS AN ANSWER ------------------------------ It explains why surviving an attack doesn't prove usability, points to the actual format-error snag this capstone describes as evidence that the concern was real rather than hypothetical, and connects the verification step directly back to Chapter 5's own discipline.