Which statement about the PowerShell pipeline is accurate?

Which statement about the PowerShell pipeline is accurate?

• A. The pipeline distributes tasks across multiple servers.
• B. The pipeline passes the output of one command as input to another.
• C. The pipeline runs commands in parallel.
• D. The pipeline converts scripts to executables.

Answer: (B)

The power of the PowerShell pipeline lies in chaining cmdlets so the output from one command feeds directly into the next. Instead of just text, PowerShell passes rich objects between commands, so you can filter, transform, and summarize data in a streamlined flow without creating intermediate files. This means you can take results from a command, narrow them down, reorder them, or pick specific properties all in one clean sequence. Distributing tasks across multiple servers isn’t inherent to the pipeline itself; you’d need explicit remoting or parallel execution techniques to affect remote machines, such as invoking commands on multiple hosts. Similarly, the standard pipeline runs commands one after another in sequence rather than in parallel by default, though there are options to parallelize in certain scenarios. Finally, the pipeline doesn’t convert scripts into executables—that’s a separate capability. Example: Get-Process | Sort-Object CPU -Descending | Select-Object -First 5. Here, each step operates on the objects produced by the previous step, illustrating how the pipeline passes data along and enables multi-step processing in a single command line.

The power of the PowerShell pipeline lies in chaining cmdlets so the output from one command feeds directly into the next. Instead of just text, PowerShell passes rich objects between commands, so you can filter, transform, and summarize data in a streamlined flow without creating intermediate files. This means you can take results from a command, narrow them down, reorder them, or pick specific properties all in one clean sequence.

Distributing tasks across multiple servers isn’t inherent to the pipeline itself; you’d need explicit remoting or parallel execution techniques to affect remote machines, such as invoking commands on multiple hosts. Similarly, the standard pipeline runs commands one after another in sequence rather than in parallel by default, though there are options to parallelize in certain scenarios. Finally, the pipeline doesn’t convert scripts into executables—that’s a separate capability.

Example: Get-Process | Sort-Object CPU -Descending | Select-Object -First 5. Here, each step operates on the objects produced by the previous step, illustrating how the pipeline passes data along and enables multi-step processing in a single command line.