Exercise 1: Why Get-WmiObject Doesn't Work in PowerShell 7+ — Possible Solution
====================================================================

THE PROTOCOL DIFFERENCE
------------------------------
Per this chapter, Get-WmiObject uses DCOM, an older protocol, while Get-CimInstance uses WSMan - the exact same WinRM transport Chapter 3's own remoting already relies on.

WHY THIS EXPLAINS THE PS7+ REMOVAL
------------------------------
Per this chapter, Get-WmiObject was fully removed from PowerShell 7+, not merely deprecated-but-still-working - it's genuinely gone. PowerShell 7+'s cross-platform, modern architecture was built around WSMan-based remoting (the same infrastructure CIM uses) rather than continuing to carry forward DCOM-specific plumbing that Get-WmiObject depended on. Get-CimInstance works fine in PowerShell 7+ precisely because it was built on the WSMan/WinRM transport from the start, which fits cleanly into that same modern remoting infrastructure, while DCOM-based Get-WmiObject had no such path forward and was dropped entirely.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly names the two different protocols each cmdlet actually uses (DCOM vs. WSMan/WinRM), and correctly connects Get-CimInstance's continued availability to its use of the same modern transport PowerShell 7+'s remoting is built on, explaining why Get-WmiObject had no such path forward.