PowerShell Genie

Inspect PowerShell processes in PowerShell

Exercise 2 min read Windows PowerShell 5.1 and PowerShell 7

Documentation: Microsoft Learn

Write a pipeline, run it against the sample data, and check your result.

An example to inspect

Preview the example. Sign in for the full lesson and activities.

Get-Process -Name 'pw*' | Sort-Object CPU -Descending

Target

Return processes whose Name matches pw*, sorted by CPU descending.

Expected result

Windows PowerShell

Try the task

Show a worked solution
Reveal one approach
1PS> Get-Process -Name 'pw*' | Sort-Object CPU -Descending

Try it in the lab

Write your pipeline below and run it against the fictional sample data, then check your result against the expected answer.

Interactive simulation · fictional data

PowerShell skills

Process objects · Sorting · Wildcard matching · Descending order

Build the answer in three decisions

Read the pipeline from left to right. Each stage receives objects from the stage before it.

Collect

Get-Process -Name 'pw*'

Start with 5 fictional process objects. Keep them as objects so later stages can inspect their properties.

Shape

Sort-Object CPU -Descending

Apply the condition or ordering required by the task. Apply a wildcard at the source, then sort.

Verify

Check order and returned names

The fixture should return pwsh. Order matters for this exercise.

Reason through the pipeline

The source stage returns 5 process objects. Then the pipeline applies Sort-Object CPU -Descending without converting the objects to display text. That keeps the Name property available for the checker and for any later pipeline stage.

Why common attempts fail

Do not select the first rows before sorting when the task asks for a highest, lowest, first, or reverse-ordered result.

What the checker accepts

The evaluator runs the supported subset against the same fictional fixture. It expects pwsh. The returned order is part of the answer. Equivalent supported syntax is accepted.

Verify another attempt

First run Get-Process -Name 'pw*' by itself and inspect the fixture. Then add one stage at a time and compare how many objects remain. This isolates the stage that changes the result and makes the final pipeline easier to explain and debug.

Primary documentation

PowerShell pipeline behavior

Next exercise
Genie guideInspect PowerShell processes in PowerShell

Write a pipeline, run it against the sample data, and check your result.