Why PowerShell is object-oriented - Challenge Your Understanding

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output type of this PowerShell command?

Consider the following PowerShell command:

Get-Process | Select-Object -First 1

What type of object does this command output?

PowerShell

Get-Process | Select-Object -First 1 | Get-Member -MemberType Property

A A string representing the process name

B A plain text table with no object properties

C A numeric value representing process ID

D An object with properties describing the process

💡 Hint

Think about what Get-Process returns and how PowerShell treats output.

PowerShell commands output objects, not just text. Get-Process returns process objects with properties like Id, Name, CPU, etc.

🧠 Conceptual

intermediate

Why does PowerShell treat output as objects?

Why does PowerShell output objects instead of plain text like many other shells?

A Because objects allow easy access to properties and methods for automation

B Because text output is slower to display on screen

C Because PowerShell cannot handle text output

D Because objects use less memory than text

💡 Hint

Think about how automation scripts benefit from structured data.

Objects let scripts access detailed information easily, making automation more powerful and flexible.

🔧 Debug

advanced

Identify the error in this PowerShell pipeline

What error occurs when running this command?

Get-Process | Where-Object { $_.Name -eq 'notepad' } | Select-Object CPU

PowerShell

Get-Process | Where-Object { $_.Name -eq 'notepad' } | Select-Object CPU

A No error; outputs CPU property of notepad processes

B Syntax error due to missing parentheses

C Error: Property 'CPU' does not exist on some objects

D Runtime error because 'notepad' process does not exist

💡 Hint

Check if the CPU property exists on process objects.

The CPU property exists on process objects, so the command runs without error and outputs CPU usage of notepad processes.

🚀 Application

advanced

Extracting object properties in PowerShell

You want to list the names and IDs of all running processes. Which command produces the correct output?

A Get-Process | Format-Table Name, Id

B Get-Process | Select-Object Name, Id

C Get-Process | Where-Object { Name, Id }

D Get-Process | ForEach-Object { $_.Name + $_.Id }

💡 Hint

Select-Object extracts properties as objects; Format-Table formats output but does not produce objects.

Select-Object extracts specified properties as objects, which can be further processed or displayed.

📝 Syntax

expert

What is the output of this PowerShell object method call?

Given this code:

$proc = Get-Process -Id $PID
$proc.ToString()

What is the output?

A The process ID number as a string

B The string 'System.Diagnostics.Process'

C The process name of the current PowerShell session

D An error because ToString() is not a method

💡 Hint

Process class overrides ToString() to return the ProcessName property.

Process objects override the ToString() method to return the process name (e.g., 'pwsh' for PowerShell).