Why PowerShell exists - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to display the PowerShell version.

PowerShell

Write-Output $PSVersionTable.PSVersion[1]

Drag options to blanks, or click blank then click option'

A.Minor

B.Revision

C.Build

D.Major

Attempts:

3 left

💡 Hint

Common Mistakes

Using .Minor or .Build instead of .Major

Forgetting the dot before the property name

The $PSVersionTable.PSVersion.Major property shows the major version number of PowerShell.

2fill in blank

medium

Complete the code to get the list of running processes in PowerShell.

PowerShell

Get-[1]

Drag options to blanks, or click blank then click option'

AProcess

BServices

CJobs

DEvents

Attempts:

3 left

💡 Hint

Common Mistakes

Using Get-Services instead of Get-Process

Confusing Jobs or Events with processes

Get-Process is the correct cmdlet to list running processes.

3fill in blank

hard

Fix the error in the code to list all files in a folder.

PowerShell

Get-ChildItem -Path [1]

Drag options to blanks, or click blank then click option'

AC:\Users\Public\

BC:/Users/Public

CC:\Users\Public

DC:/Users/Public/

Attempts:

3 left

💡 Hint

Common Mistakes

Using forward slashes instead of backslashes

Adding a trailing slash which can cause issues

In PowerShell, backslashes \ are used for Windows paths. The path should not end with a slash for this command.

4fill in blank

hard

Fill both blanks to create a hashtable with keys and values.

PowerShell

$info = @{ [1] = 'PowerShell'; [2] = 7 }

Drag options to blanks, or click blank then click option'

AName

BVersion

CPower

DLevel

Attempts:

3 left

💡 Hint

Common Mistakes

Using unrelated keys like Power or Level

Mixing up keys and values

The keys Name and Version describe the hashtable content clearly.

5fill in blank

hard

Fill all three blanks to filter processes with CPU usage greater than 100.

PowerShell

$highCPU = Get-Process | Where-Object { $_.[1] [2] [3] }

Drag options to blanks, or click blank then click option'

ACPU

B>

C100

DName

Attempts:

3 left

💡 Hint

Common Mistakes

Using Name instead of CPU

Using wrong comparison operators

Using strings instead of numbers

The property CPU is compared with > to the number 100 to filter processes using more CPU time.