Why cmdlets are the building blocks in PowerShell - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why are cmdlets considered the building blocks in PowerShell?

Choose the best explanation for why cmdlets are called the building blocks of PowerShell.

A Cmdlets are small, single-function commands that can be combined to perform complex tasks.

B Cmdlets are graphical tools used to design PowerShell scripts visually.

C Cmdlets are large programs that replace the need for scripting in PowerShell.

D Cmdlets are only used for managing files and cannot be combined.

💡 Hint

Think about how small commands can be combined to do bigger jobs.

Cmdlets are simple commands designed to do one job well. By combining them, you can automate complex tasks easily, making them the building blocks of PowerShell.

💻 Command Output

intermediate

Output of a simple cmdlet pipeline

What is the output of this PowerShell command? Get-Process | Where-Object {$_.CPU -gt 100} | Select-Object -Property Name, CPU

PowerShell

Get-Process | Where-Object {$_.CPU -gt 100} | Select-Object -Property Name, CPU

A No output because the command is incomplete.

B An error saying 'CPU property not found'.

C A list of all processes without filtering.

D A list of process names and their CPU usage where CPU is greater than 100.

💡 Hint

Look at how the pipeline filters and selects properties.

The command gets all processes, filters those with CPU usage over 100, then shows only their Name and CPU properties.

📝 Syntax

advanced

Identify the correct syntax for creating a custom cmdlet function

Which option shows the correct syntax to define a simple PowerShell function that acts like a cmdlet?

A def Get-Greeting(Name): return "Hello, Name!"

B function Get-Greeting { param($Name) "Hello, $Name!" }

C function Get-Greeting($Name) { echo "Hello, $Name!" }

D func Get-Greeting { param Name; Write-Output "Hello, Name!" }

💡 Hint

PowerShell functions use the 'function' keyword and 'param' block.

Option B correctly defines a PowerShell function with a parameter and returns a string using double quotes for variable expansion.

🔧 Debug

advanced

Why does this cmdlet pipeline fail?

This PowerShell command fails with an error. What is the cause? Get-Service | Where-Object {$_.Status = 'Running'}

PowerShell

Get-Service | Where-Object {$_.Status = 'Running'}

A Get-Service does not return objects with a Status property.

B Where-Object cannot be used in pipelines.

C The '=' operator is used instead of '-eq' for comparison.

D The command is missing a closing parenthesis.

💡 Hint

Check the operator used inside the script block for comparison.

In PowerShell, '=' is for assignment, while '-eq' is for comparison. Using '=' causes an error in the filter.

🚀 Application

expert

How many cmdlets are involved in this script?

Consider this PowerShell script: $files = Get-ChildItem -Path C:\Logs -Filter *.log $recent = $files | Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-7) } $recent | Sort-Object LastWriteTime | Select-Object -First 5 | ForEach-Object { Write-Output $_.Name } How many distinct cmdlets are used in this script?

PowerShell

$files = Get-ChildItem -Path C:\Logs -Filter *.log
$recent = $files | Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-7) }
$recent | Sort-Object LastWriteTime | Select-Object -First 5 | ForEach-Object { Write-Output $_.Name }

A 7

B 6

C 5

D 4

💡 Hint

Count each unique cmdlet name used in the script.

The distinct cmdlets used are Get-ChildItem, Where-Object, Get-Date, Sort-Object, Select-Object, ForEach-Object, and Write-Output. Total: 7.