Exercise 1: Why Access and Authorization Are Different Things — Possible Solution ==================================================================== WHAT THIS CHAPTER SAYS ------------------------------ Per this chapter, before acting you should confirm "who actually owns this system, what are you authorized to do on it (read-only diagnosis? specific fixes? anything at all?), and is there a change-approval process that applies here. This is a genuinely different question from 'do I have access' - having access and being authorized for a specific action are not the same thing." WHY TECHNICAL ACCESS DOESN'T IMPLY PERMISSION ------------------------------ Having a working login or an SSH key that lets you connect to a system only confirms that the technical mechanism for reaching it works - it says nothing about what actions the owning team actually wants or expects you to take once you're there. A support engineer might be granted access specifically to diagnose (read logs, check metrics) without that access implying permission to also make changes, restart services, or apply fixes. A CONCRETE WAY THE TWO CAN DIVERGE ------------------------------ An engineer could technically have full admin rights on a system (able to run any command) while only being authorized, by the actual owning team's own expectations or process, to perform read-only diagnosis - technical capability exceeding actual permission is a completely realistic, common situation, not a hypothetical edge case. WHY THIS DISTINCTION MATTERS PRACTICALLY ------------------------------ Confirming authorization separately from access is what prevents an engineer from doing something technically possible but not actually sanctioned - exactly the gap this chapter opens with, and the reason it treats "can I do this" and "am I allowed to do this" as two separate questions that both need answering before acting. WHY THIS WORKS AS AN ANSWER ------------------------------ It states the chapter's own explicit distinction, explains why technical access doesn't imply permission, and gives a concrete example of the two diverging in practice.