Exercise 3: Why This Is Framed as Reasoning About Restores, Not an Architecture Decision — Possible Solution ==================================================================== WHAT THIS CHAPTER SAYS DIRECTLY ------------------------------ Per this chapter's opening line, "understanding backup types here isn't about choosing one - that's an architecture decision that's usually already made before a ticket ever reaches you." The chapter explicitly separates two different activities: designing a backup scheme, and working with whatever scheme someone else already put in place. WHY A SUPPORT TECHNICIAN ENCOUNTERS THIS DIFFERENTLY THAN A SYSADMIN DOES ------------------------------ A sysadmin designing a backup system chooses full vs. incremental vs. differential based on tradeoffs like storage budget and backup-window length, weighed in advance, before any data loss has happened. A support technician handling a real ticket encounters the scheme only after it's already running, in the middle of trying to recover something specific - there's no opportunity to redesign anything at that moment, only to work correctly with what exists. WHY THE TECHNICIAN STILL NEEDS TO UNDERSTAND THE TYPES, JUST FOR A DIFFERENT PURPOSE ------------------------------ Per this chapter, the actual value of this knowledge on a real ticket is knowing "how many pieces it actually needs, roughly how long it should take, and where a single broken piece could cause the whole thing to fail." None of that requires choosing between the schemes - it requires recognizing which scheme is already in use and reasoning correctly about what a restore under that scheme will actually require. WHY THIS DISTINCTION MATTERS FOR THE WHOLE COURSE, NOT JUST THIS CHAPTER ------------------------------ This mirrors Chapter 1's own "not a sysadmin-build course" framing directly - the entire course teaches verification and response skills for a backup system that already exists, not design skills for building one. Chapter 2's own material is a direct application of that same boundary to backup types specifically. WHY THIS WORKS AS AN ANSWER ------------------------------ It quotes the chapter's own explicit framing, explains the different moment at which a sysadmin and a support technician each encounter backup types, and connects this back to Chapter 1's own scope statement for the whole course.