Exercise 2: What Mock Get-Content Actually Does — Possible Solution
====================================================================

WHAT IT DOES
------------------------------
Per this chapter, Mock replaces a real cmdlet's actual behavior for the duration of the test - Mock Get-Content { return '{"setting": "value"}' } means that any call to Get-Content made during that test (including calls made internally by the function under test, like Get-ConfigValue) doesn't touch a real file on disk at all. Instead, it returns the fixed, fake value specified in the mock's own script block, regardless of what path was actually requested.

WHY THIS MATTERS FOR NOT DEPENDING ON A REAL FILE
------------------------------
Per this chapter, this is what actually makes a test trustworthy - Get-ConfigValue can be tested without any real config file existing anywhere on disk, and without the test's outcome depending on that file's real contents staying the same over time or existing on whatever machine happens to run the test. Without mocking, the test would fail not just when Get-ConfigValue's own logic is wrong, but also whenever the real file is missing, has different contents, or isn't accessible for an unrelated reason - none of which should actually cause a test of Get-ConfigValue's logic to fail.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that Mock intercepts and replaces the real cmdlet's behavior with a controlled, fake result, and correctly explains why this isolation is what makes the test reliably fail only for the right reason (broken logic) rather than for unrelated environmental reasons.