Exercise 3: Explicit FunctionsToExport vs. Wildcard — Possible Solution
====================================================================

WHY THE EXPLICIT LIST IS FASTER
------------------------------
Per this chapter's own central finding, a manifest with an explicit FunctionsToExport list is pure, static metadata - PowerShell can read exactly what a module exports directly out of the .psd1 file itself, without ever having to load or run a single line of the module's actual code. FunctionsToExport = '*' throws that advantage away entirely: since the manifest no longer states a concrete list, PowerShell has no choice but to actually load the module and introspect its contents to discover what it exports, every single time module auto-discovery needs an answer.

WHY THIS MATTERS AT SYSTEM SCALE
------------------------------
Per this chapter, this cost isn't confined to just one module - multiplied across every module on a system that uses a wildcard export, it measurably slows down the module auto-loading behavior Fundamentals 11 described as "most modules just auto-load, no explicit Import-Module needed." That convenience only stays fast system-wide because well-behaved modules declare their exports explicitly as static metadata, rather than forcing PowerShell to actually load and inspect the code just to find out what's available.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that an explicit list lets PowerShell read exports without loading the module, correctly contrasts this with the wildcard forcing an actual load-and-introspect step, and correctly connects the difference to real, system-wide auto-discovery performance rather than treating it as a purely stylistic choice.