What is a key characteristic of PowerShell output compared to many shells?

What is a key characteristic of PowerShell output compared to many shells?

• A. It outputs only strings.
• B. It outputs binary data.
• C. It is object-based rather than text-based.
• D. It outputs only numeric values.

Answer: (C)

PowerShell treats output as objects, not just text. Each command emits objects that have properties and possibly methods, and these objects flow through the pipeline to the next command. This lets you directly access properties, filter by them, and format the final display without parsing lines of text. For example, Get-Process returns process objects; you can pipe them to Where-Object to filter by CPU usage and then to Select-Object to pick specific properties. The host formats the last view, but the data moving through the pipeline remains structured. In many shells, you deal with text streams, which means you often have to write text-parsing logic to extract values. That's why PowerShell output is characterized as object-based rather than text-based.

PowerShell treats output as objects, not just text. Each command emits objects that have properties and possibly methods, and these objects flow through the pipeline to the next command. This lets you directly access properties, filter by them, and format the final display without parsing lines of text. For example, Get-Process returns process objects; you can pipe them to Where-Object to filter by CPU usage and then to Select-Object to pick specific properties. The host formats the last view, but the data moving through the pipeline remains structured. In many shells, you deal with text streams, which means you often have to write text-parsing logic to extract values. That's why PowerShell output is characterized as object-based rather than text-based.