Why PowerShell automates admin tasks - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to list all running processes.

PowerShell

Get-Process | Where-Object { $_.CPU -gt [1] }

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

Anull

B100

C-1

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using -1 is invalid as CPU time cannot be negative; 100 excludes low-CPU ones; null causes errors.

The code filters processes with CPU greater than 0. Since CPU time is always ≥ 0, this lists all running processes except those with exactly 0 CPU time.

2fill in blank

medium

Complete the code to stop a service named 'Spooler'.

PowerShell

Stop-Service -Name [1]

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

AServiceSpool

BSpooler

CPrinter

DPrintSpooler

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect or partial service names causes errors.

'Spooler' is the correct service name to stop the print spooler service.

3fill in blank

hard

Complete the code to get the current date and time.

PowerShell

$now = Get-Date[1]

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

A{}

B[]

C()

D<>

Attempts:

3 left

💡 Hint

Common Mistakes

Using [] {} or <> causes syntax errors.

Empty parentheses explicitly invoke the Get-Date cmdlet.

4fill in blank

hard

Fill both blanks to filter services that are running and display their names.

PowerShell

Get-Service | Where-Object { $_.Status -eq [1] } | Select-Object [2]

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

A'Running'

B'Stopped'

CName

DStatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong status or selecting wrong properties shows incorrect results.

Filtering services with status 'Running' and selecting their 'Name' shows active service names.

5fill in blank

hard

Fill both blanks to create a hashtable of process names and their IDs for processes using more than 50 CPU seconds.

PowerShell

$processes = @{}; Get-Process | Where-Object { $_.CPU -gt 50 } | ForEach-Object { $processes[[1]] = [2] }

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

A$_.ProcessName

B$_.Id

Cprocess

Dproc

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong variable names or properties causes errors or empty results.

The hashtable maps each process name to its ID for processes with CPU time over 50 seconds.

Practice

1. Why do system administrators use PowerShell to automate tasks?

easy

A. Because it requires no learning

B. Because it only works on one computer

C. To make computers slower

D. To save time and reduce manual errors

Solution

1. Step 1: Understand the purpose of automation

   Automation helps reduce repetitive manual work and mistakes.

2. Step 2: Identify PowerShell benefits

   PowerShell automates tasks to save time and reduce errors, making admin work easier.

3. Final Answer:

   To save time and reduce manual errors -> Option D

4. Quick Check:

   Automation = Save time and reduce errors [OK]

Hint: Automation saves time and avoids mistakes [OK]

Common Mistakes:

• Thinking automation makes computers slower
• Believing PowerShell requires no learning
• Assuming it only works on one computer

2. Which of the following is the correct way to run a PowerShell cmdlet to list files in a folder?

easy

A. Get-ChildItem

B. List-Files

C. Show-Folder

D. GetFiles

Solution

1. Step 1: Recall common PowerShell cmdlets

   PowerShell uses cmdlets like Get-ChildItem to list files and folders.

2. Step 2: Identify the correct cmdlet

   Get-ChildItem is the standard cmdlet to list directory contents.

3. Final Answer:

   Get-ChildItem -> Option A

4. Quick Check:

   List files cmdlet = Get-ChildItem [OK]

Hint: Remember cmdlets use Verb-Noun format [OK]

Common Mistakes:

• Using non-existent cmdlets like List-Files
• Confusing cmdlet names with other commands
• Omitting the dash between verb and noun

3. What will this PowerShell script output?

1..3 | ForEach-Object { "Task $_ completed" }

medium

A. 1 2 3

B. Task $_ completed

C. Task 1 completed Task 2 completed Task 3 completed

D. Error: $_ not defined

Solution

1. Step 1: Understand the range operator and pipeline

   1..3 creates numbers 1, 2, 3 and pipes them one by one.

2. Step 2: Evaluate ForEach-Object with string interpolation

   For each number, it outputs "Task <number> completed" using $_ as current item.

3. Final Answer:

   Task 1 completed Task 2 completed Task 3 completed -> Option C

4. Quick Check:

   Loop with $_ outputs tasks 1 to 3 [OK]

Hint: $_ holds current item in pipeline loops [OK]

Common Mistakes:

• Thinking $_ is undefined outside loops
• Expecting numbers only without text
• Confusing output as a single string without spaces

4. Identify the error in this PowerShell script:

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

medium

A. Missing closing brace '}'

B. No error, script is correct

C. Incorrect operator '-eq'

D. Wrong cmdlet name 'Get-Process'

Solution

1. Step 1: Check syntax of Where-Object filter

   The script uses correct syntax with braces and -eq operator to filter processes.

2. Step 2: Verify cmdlet names and operators

   Get-Process and Where-Object are valid cmdlets; -eq is correct for equality check.

3. Final Answer:

   No error, script is correct -> Option B

4. Quick Check:

   Script syntax and cmdlets are valid [OK]

Hint: Check braces and cmdlet names carefully [OK]

Common Mistakes:

• Assuming missing brace when it is present
• Confusing -eq with other operators
• Thinking cmdlet names are case-sensitive

5. You want to automate restarting a service on multiple computers using PowerShell. Which approach best achieves this?

hard

A. Write a script using Invoke-Command to run Restart-Service remotely on each computer

B. Manually log into each computer and restart the service

C. Use Get-Process to find the service and kill it

D. Run Restart-Service locally without specifying computers

Solution

1. Step 1: Understand remote automation with PowerShell

   Invoke-Command runs commands on remote computers, ideal for multi-computer tasks.

2. Step 2: Identify correct cmdlet for restarting services remotely

   Restart-Service restarts a service; combined with Invoke-Command it runs remotely on each target.

3. Final Answer:

   Write a script using Invoke-Command to run Restart-Service remotely on each computer -> Option A

4. Quick Check:

   Remote automation uses Invoke-Command + Restart-Service [OK]

Hint: Use Invoke-Command for remote task automation [OK]

Common Mistakes:

• Restarting services manually on each machine
• Using Get-Process instead of Restart-Service
• Running Restart-Service only locally without targets