Exercise 3: Why Knowing All Four Interfaces Matters — Possible Solution
====================================================================

THE FOUR INTERFACES NAMED IN THIS CHAPTER
------------------------------
Per this chapter's own finding-box, Windows exposes the same underlying
system state through "a modern GUI (Settings), a legacy GUI (Control
Panel), and a scriptable command line (PowerShell...) - and Windows 11
Troubleshooting & Administration adds a fourth, deeper layer still: the
Registry and Group Policy."

WHAT KNOWING ONLY THE NEWEST ONE ACTUALLY LIMITS
------------------------------
A support engineer who only knows Settings can handle the fraction of
tasks Microsoft has fully migrated there - but, per Exercise 1's own
finding, that migration is genuinely incomplete. The moment a real task
lands on one of the still-Control-Panel-only settings, "I only know the
new app" becomes a dead end rather than a minor inconvenience, exactly
as this chapter's own warn-box already illustrated for the taskbar.

WHY EACH OLDER LAYER STILL MATTERS IN PRACTICE
------------------------------
Control Panel remains necessary for exactly the gaps Exercise 1
identified. PowerShell (previewed here, covered in full in Chapter 10)
matters because it's scriptable - a task that needs to run identically
across many machines, or as part of an automated process, isn't
something Settings or Control Panel can do at all, since both are
built for one human clicking through a GUI one machine at a time. The
Registry and Group Policy, reserved for Course 2, go a layer deeper
still - they're often the only place a setting can be forced, audited,
or applied consistently across an entire organization rather than one
machine at a time.

WHY THIS IS REAL DAY-JOB JUDGMENT, NOT TRIVIA
------------------------------
Each interface exists because it solves a problem the others don't -
newer surfaces don't replace older ones so much as add a friendlier
option alongside them for the subset of tasks that have been rebuilt.
Recognizing which layer a given problem actually requires - rather than
defaulting to whichever interface is most familiar - is precisely the
skill this two-course track is built to develop, matching this
chapter's own framing that this is "real support-engineer judgment,
not trivia."

WHY THIS WORKS AS AN ANSWER
------------------------------
It restates all four interfaces the chapter names, explains concretely
what's lost by only knowing the newest one (using Exercise 1's own
finding as evidence), gives a real reason each older layer still
matters rather than treating them as legacy clutter, and ties the
explanation back to the chapter's own explicit framing of this as
practical judgment rather than incidental trivia.