Exercise 2: Why Execution Policy Isn't a Security Boundary — Possible Solution
====================================================================

WHY IT'S DESCRIBED THIS WAY
------------------------------
Per this chapter, execution policy exists to prevent ACCIDENTAL script execution - like double-clicking an unfamiliar .ps1 file, or a script quietly running inside something else without the user noticing. It was never designed to stop someone who is deliberately trying to run code on a machine they already have access to, because it is trivially easy to bypass on purpose. A real security boundary would hold up against a determined bypass attempt; execution policy simply doesn't, by design.

A CONCRETE BYPASS FROM THIS CHAPTER
------------------------------
Per this chapter, any of the following bypasses execution policy entirely, because none of them count as "running a script file": pasting a script's contents directly into an interactive PowerShell prompt, running powershell.exe -EncodedCommand, or piping text into Invoke-Expression. Any one of these is a valid, concrete example.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that execution policy targets accidental execution rather than deliberate circumvention, and names a specific, chapter-grounded bypass technique (pasting into the console, -EncodedCommand, or Invoke-Expression) that skips execution policy entirely rather than just asserting it's bypassable without evidence.