Exercise 3: foreach vs. ForEach-Object — Possible Solution
====================================================================

THE PRACTICAL DIFFERENCE
------------------------------
foreach ($p in Get-Process) {...} is a language statement - per this chapter, it fully evaluates Get-Process into a complete, in-memory collection FIRST, and only then begins looping over that already-finished collection. Get-Process | ForEach-Object {...} is a pipeline stage - it processes each process object as soon as that individual object is produced, one at a time, without ever holding the entire result set in memory simultaneously.

A CONCRETE SITUATION WHERE THIS ACTUALLY MATTERS
------------------------------
Per this chapter, the difference is invisible on a small result set like a typical process list, but becomes genuinely significant on something large - for example, running Get-ChildItem recursively across a massive directory tree with millions of files. Using foreach ($f in Get-ChildItem -Recurse) {...} would have to enumerate and hold every single file object in memory before the loop body could even start running once. Using Get-ChildItem -Recurse | ForEach-Object {...} instead would begin processing the very first file immediately, and would never need to hold more than a small number of file objects in memory at any one time - a real, practical difference in both memory usage and how soon results start appearing.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that foreach evaluates the full collection into memory before looping while ForEach-Object streams one object at a time, and gives a concrete, large-scale scenario (a massive recursive directory listing) where that memory/streaming difference would have a real, noticeable practical impact rather than being invisible.