Take the first three service names in PowerShell
Documentation: Microsoft Learn
Write a pipeline, run it against the sample data, and check your result.
An example to inspect
Read the example, then complete the activity below. All lessons are public. Sign-in is optional for progress sync.
Get-Service | Sort-Object Name | Select-Object -First 3Target
Sort service names alphabetically, then return the first three.
Expected result
BITS, Dnscache, EventLog
Try the task
Show a worked solution
Reveal one approach
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.
Follow the objects
Run the command to inspect each stage.
PowerShell skills
Service objects · Sorting · Selection · Top-N results
Build the answer in three decisions
Read the pipeline from left to right. Each stage receives objects from the stage before it.
Collect
Get-Service
Start with 7 fictional service objects. Keep them as objects so later stages can inspect their properties.
Shape
Sort-Object Name
Apply the condition or ordering required by the task. Sort before limiting.
Verify
Check order and returned names
The fixture should return BITS, Dnscache, EventLog. Order matters for this exercise.
Reason through the pipeline
The source stage returns 7 service objects. Then the pipeline applies Sort-Object Name, Select-Object -First 3 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. Use Select-Object after the important filtering or ordering work; selecting too early can discard properties needed by later stages.
What the checker accepts
The evaluator runs the supported subset against the same fictional fixture. It expects BITS, Dnscache, EventLog. The returned order is part of the answer. Equivalent supported syntax is accepted.
Verify another attempt
First run Get-Service 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.
