Exercise 3: Why an Ansible Playbook Fix Beats a Manual SSH Fix — Possible Solution ==================================================================== Explanation: Both approaches genuinely DO solve the immediate problem -- if a config file needs a value changed, SSHing in and editing it by hand fixes that server, right now, just as effectively as running a playbook would. The real difference cloud1-11's own "fix the config, not just the console" lesson is about isn't whether the fix works in the moment -- it's about what happens to that fix afterward, and whether anyone else can see it happened at all. A manual SSH fix leaves no record anywhere except that one server's own current state -- there's no history of WHO changed it, WHEN, or WHY, and no way for a teammate to know the change ever happened short of noticing the file itself looks different. Per cloud1-11's own configuration-drift material, this fix is also fragile in a very specific way: if that server is ever rebuilt, replaced, or if a config-management run happens to re-apply an OLDER version of that same file from source control, the manual fix is silently overwritten with no warning, and the original problem quietly comes back -- exactly the "manual fix reverted" pattern the site's own IaC material warns about. Making the same fix inside an Ansible playbook instead means the change lives in version control, reviewable the same way any other code change is, with a real commit history explaining who changed what and why. And because the playbook is now the actual source of truth for that configuration, running it again -- on this server, on a replacement server, on every server in the fleet -- reliably applies the SAME fix everywhere, rather than depending on someone remembering to repeat the same manual SSH session by hand on every other affected machine. WHY THIS WORKS AS AN ANSWER ------------------------------ This acknowledges that both approaches genuinely fix the immediate problem, then focuses the real distinction on the "not just the console" lesson's actual concern -- durability, visibility, and repeatability of the fix -- rather than claiming the manual fix doesn't work at all.