Which statement best describes PowerShell's object-based pipeline design?

Which statement best describes PowerShell's object-based pipeline design?

• A. Commands pass plain text between each other.
• B. Commands pass binary data between each other.
• C. Commands pass objects between each other, enabling rich data transfer.
• D. Commands cannot be chained.

Answer: (C)

PowerShell is built around sending actual objects from one command to the next, not just text. Each cmdlet emits objects that carry properties and possible methods, and the next cmdlet in the chain can inspect those properties, filter or transform data, and pass along richer information. This object-based pipeline lets you do powerful data operations without parsing plain text, since you can act on the structured data directly. For example, Get-Process emits process objects with properties like Name, Id, and CPU; piping to Where-Object or Select-Object lets you filter or pick properties without losing the data’s structure, and you can send the result into Export-Csv or Format-Table for nicely formatted output.

PowerShell is built around sending actual objects from one command to the next, not just text. Each cmdlet emits objects that carry properties and possible methods, and the next cmdlet in the chain can inspect those properties, filter or transform data, and pass along richer information. This object-based pipeline lets you do powerful data operations without parsing plain text, since you can act on the structured data directly. For example, Get-Process emits process objects with properties like Name, Id, and CPU; piping to Where-Object or Select-Object lets you filter or pick properties without losing the data’s structure, and you can send the result into Export-Csv or Format-Table for nicely formatted output.