Exercise 1: Should -Be vs. Should -BeExactly — Possible Solution
====================================================================

WHY Should -Be PASSES
------------------------------
Per this chapter, Should -Be performs a case-insensitive comparison by default, so "HELLO" and "hello" are considered equal despite differing in letter case - the assertion passes.

WHY Should -BeExactly FAILS
------------------------------
Should -BeExactly requires the comparison to match exactly, including case - since "HELLO" and "hello" differ in case, this assertion fails even though the two strings contain the same letters.

THE CONNECTION TO -eq/-ceq
------------------------------
Per this chapter's own central finding, this mirrors Fundamentals 4's -eq/-ceq pattern exactly: -eq is case-insensitive by default, with -ceq as the explicit case-sensitive variant. Should -Be and Should -BeExactly follow the identical structure - case-insensitive by default, with an explicit "exact" opt-in whenever genuine case-sensitivity is actually needed. It's the same underlying PowerShell design choice, just expressed through Pester's own assertion syntax rather than a comparison operator.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains why each assertion passes or fails based on case-sensitivity, and correctly ties this back to Fundamentals 4's own -eq/-ceq pattern as the same underlying design choice recurring in a new context.