Exercise 3: A Temporary, Process-Scoped Bypass — Possible Solution
====================================================================

THE COMMANDS
------------------------------
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process
.\trusted-script.ps1

WHY -Scope Process IS THE RIGHT CHOICE
------------------------------
Per this chapter, -Scope Process only affects the current PowerShell window - it evaporates automatically the moment that window closes, leaving the LocalMachine scope's own policy completely untouched. This satisfies the requirement exactly: the trusted script runs this one time, without leaving any permanent, machine-wide change behind.

WHY -Scope LocalMachine WOULD BE THE WRONG CHOICE
------------------------------
Setting -Scope LocalMachine would change the execution policy for the entire machine, for every user and every future PowerShell session, not just the current one - a permanent, broad change made just to run one trusted script a single time. That directly contradicts the requirement of running the script "without permanently changing your machine's execution policy," making Process scope the appropriate, narrowly-targeted choice instead.

WHY THIS WORKS AS AN ANSWER
------------------------------
It provides the correct Set-ExecutionPolicy command with -Scope Process followed by running the script, and correctly explains both why Process scope is temporary and self-contained and why LocalMachine scope would violate the stated requirement of not making a permanent change.