Exercise 1: Why Receive-Job Returns Nothing the Second Time — Possible Solution
====================================================================

WHY THE SECOND CALL RETURNS NOTHING
------------------------------
Per this chapter, Receive-Job drains the job's own output buffer by default - the first call retrieves whatever output the job produced AND removes it from that buffer at the same time. By the time a second Receive-Job call runs against the same job, there's nothing left in the buffer to return, because the first call already consumed and cleared it. This isn't the job losing its output somewhere - it's Receive-Job's own default behavior of treating each read as a one-time consumption of what's there.

THE FIX
------------------------------
Adding -Keep to the Receive-Job call, per this chapter, leaves the output sitting in the buffer rather than clearing it out - Receive-Job $job -Keep can be called multiple times and will return the same output each time, since nothing gets removed.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that Receive-Job's default behavior drains the output buffer on read (not that the job itself loses data), and correctly names -Keep as the parameter that prevents that drain, allowing repeated reads.