Practice - 5 Tasks

Answer the questions below

1fill in blank

easy

Complete the code to display the most recent error stored in the $Error automatic variable.

PowerShell

Write-Output $Error[1]

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

A[1]

B.Count

C[0]

D.Clear()

Attempts:

3 left

💡 Hint

Common Mistakes

Using .Count instead of an index to access an error.

Using [1] which accesses the second error, not the most recent.

Trying to clear errors instead of displaying them.

✗ Incorrect

The $Error variable stores errors in a collection, with the most recent error at index 0. Using $Error[0] accesses the latest error.

2fill in blank

medium

Complete the code to clear all errors from the $Error automatic variable.

PowerShell

$Error[1]()

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

A.Remove

B.Clear

C.Reset

D.Delete

Attempts:

3 left

💡 Hint

Common Mistakes

Using .Remove() which requires an argument and removes a specific item.

Using .Reset() or .Delete() which are not valid methods for $Error.

✗ Incorrect

The .Clear() method empties the $Error collection, removing all stored errors.

3fill in blank

hard

Fix the error in the code to display the error message of the most recent error.

PowerShell

Write-Output $Error[1].Exception.Message

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

A[0]

B.Count

C[1]

D.Clear()

Attempts:

3 left

💡 Hint

Common Mistakes

Using .Count which is a number, not an error object.

Using [1] which accesses the second error, not the most recent.

Trying to call .Clear() which clears errors instead of displaying.

✗ Incorrect

To get the message of the most recent error, access $Error[0].Exception.Message. Using [0] gets the latest error object.

4fill in blank

hard

Fill both blanks to check if there are any errors and display the count.

PowerShell

if ($Error[1] -gt 0) { Write-Output "Errors: $($Error[2])" }

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

A.Count

B[0]

C.Length

D[1]

Attempts:

3 left

💡 Hint

Common Mistakes

Using [0] or [1] which access specific errors, not the count.

Using .Length which is similar but .Count is preferred for collections.

✗ Incorrect

The .Count property gives the number of errors in $Error. Using it in both places checks if errors exist and shows how many.

5fill in blank

hard

Fill all three blanks to create a filtered list of error messages containing the word 'timeout'.

PowerShell

$timeoutErrors = $Error | Where-Object { $_.Exception.Message[1] '*timeout*' } | ForEach-Object { $_.Exception.[2] } | Sort-Object [3]

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

A-like

BMessage

CException.Message

DLength

Attempts:

3 left

💡 Hint

Common Mistakes

Using Exception.Message which is nested and invalid here.

Using -eq instead of -like which looks for exact matches.

Sorting by Exception.Message which is not a direct property.

✗ Incorrect

Use -like to filter messages containing 'timeout'. Extract the Message property from $_.Exception, then sort by Length to order by message size.

Practice

(1/5)

1. What does the PowerShell automatic variable $Error store?

easy

A. A list of recent errors encountered during the session

B. All successful command outputs

C. User input history

D. System environment variables

Solution

Step 1: Understand the purpose of $Error
$Error automatically collects errors that occur during the PowerShell session.
Step 2: Differentiate from other variables
It does not store outputs, inputs, or environment variables, only errors.
Final Answer:
A list of recent errors encountered during the session -> Option A
Quick Check:
$Error stores errors [OK]

Hint: Remember: $Error always holds recent errors [OK]

Common Mistakes:

Thinking $Error stores command outputs
Confusing $Error with environment variables
Assuming $Error stores user inputs

2. Which of the following is the correct way to clear all errors stored in $Error?

easy

A. Clear-Error

B. $Error = $null

C. $Error.Clear()

D. Remove-Variable $Error

Solution

Step 1: Identify the method to clear errors
$Error is an automatic variable with a method Clear() to empty its contents.
Step 2: Evaluate other options
Assigning $null or removing the variable does not properly clear the error collection; Clear-Error is not a valid cmdlet.
Final Answer:
$Error.Clear() -> Option C
Quick Check:
Use $Error.Clear() to clear errors [OK]

Hint: Use $Error.Clear() to empty errors quickly [OK]

Common Mistakes:

Trying to assign $null to $Error
Using non-existent cmdlets like Clear-Error
Removing $Error variable instead of clearing

3. Given this PowerShell code:

Try { Get-Item 'C:\nonexistentfile.txt' } Catch { Write-Host 'Error caught' }
$latestError = $Error[0]
Write-Output $latestError.Exception.Message

What will be the output?

medium

A. Error caught

B. Cannot find path 'C:\nonexistentfile.txt' because it does not exist.

C. No errors found

D. Get-Item : The term 'Get-Item' is not recognized

Solution

Step 1: Understand the Try-Catch block behavior
The command tries to get a file that does not exist, causing an error caught by Catch, which writes 'Error caught'.
Step 2: Analyze $Error[0] and output
$Error[0] holds the most recent error object. Accessing Exception.Message outputs the detailed error message about the missing file.
Final Answer:
Cannot find path 'C:\nonexistentfile.txt' because it does not exist. -> Option B
Quick Check:
$Error[0].Exception.Message shows error details [OK]

Hint: Remember $Error[0] is newest error object [OK]

Common Mistakes:

Confusing Write-Host output with $Error content
Expecting 'Error caught' from Write-Host as output
Assuming no error is stored in $Error

4. You run this code:

Get-Item 'C:\missingfile.txt'
Write-Output $Error[0]

But the output is empty. What is the likely reason?

medium

A. The error was cleared before accessing $Error

B. Get-Item succeeded, so no error was recorded

C. $Error variable is not available in this session

D. You must use $Errors instead of $Error

Solution

Step 1: Check if error occurred
Since the file is missing, Get-Item should cause an error and populate $Error.
Step 2: Consider why $Error[0] is empty
If $Error was cleared (e.g., by $Error.Clear()) before accessing, it will be empty despite the error.
Final Answer:
The error was cleared before accessing $Error -> Option A
Quick Check:
Clearing $Error empties error list [OK]

Hint: Check if $Error was cleared before reading it [OK]

Common Mistakes:

Assuming $Error is empty if no error occurred
Confusing $Error with $Errors variable
Thinking $Error is unavailable in session

5. You want to write a script that tries to get a file, and if it fails, clears the error list and logs the error message only once. Which code snippet correctly uses $Error to achieve this?

hard

Try { Get-Item 'C:\file.txt' } Catch { $Error.Clear(); Write-Output $Error[0].Exception.Message }

Try { Get-Item 'C:\file.txt' } Catch { Write-Output $Error.Clear(); Write-Output $Error[0].Exception.Message }

Get-Item 'C:\file.txt' -ErrorAction SilentlyContinue; Write-Output $Error[0].Exception.Message; $Error.Clear()

Try { Get-Item 'C:\file.txt' } Catch { $msg = $Error[0].Exception.Message; $Error.Clear(); Write-Output $msg }

Solution

Step 1: Identify correct error handling and clearing order
```
Try { Get-Item 'C:\file.txt' } Catch { $msg = $Error[0].Exception.Message; $Error.Clear(); Write-Output $msg }
```
captures the error message from $Error[0], then clears the error list, then outputs the message.

Step 2: Check other options for mistakes

Try { Get-Item 'C:\file.txt' } Catch { Write-Output $Error.Clear(); Write-Output $Error[0].Exception.Message }

clears errors before reading message (wrong order).

Get-Item 'C:\file.txt' -ErrorAction SilentlyContinue; Write-Output $Error[0].Exception.Message; $Error.Clear()

does not use Try-Catch and may fail silently.

Try { Get-Item 'C:\file.txt' } Catch { $Error.Clear(); Write-Output $Error[0].Exception.Message }

clears errors before reading message, losing the error.

Final Answer:
Try { Get-Item 'C:\file.txt' } Catch { $msg = $Error[0].Exception.Message; $Error.Clear(); Write-Output $msg } -> Option D
Quick Check:
Read error before clearing $Error [OK]

Hint: Always read $Error before calling $Error.Clear() [OK]

Common Mistakes:

Clearing $Error before reading error message
Not using Try-Catch for error handling
Expecting $Error to update immediately without Try-Catch

$Error automatic variable in PowerShell - Interactive Code Practice

Practice

Solution

Step 1: Understand the purpose of `$Error`

Step 2: Differentiate from other variables

Final Answer:

Quick Check:

Solution

Step 1: Identify the method to clear errors

Step 2: Evaluate other options

Final Answer:

Quick Check:

Solution

Step 1: Understand the Try-Catch block behavior

Step 2: Analyze $Error[0] and output

Final Answer:

Quick Check:

Solution

Step 1: Check if error occurred

Step 2: Consider why $Error[0] is empty

Final Answer:

Quick Check:

Solution

Step 1: Identify correct error handling and clearing order

Step 2: Check other options for mistakes

Final Answer:

Quick Check:

Ready to prove it?

Practice

Solution

Step 1: Understand the purpose of $Error

Step 2: Differentiate from other variables

Final Answer:

Quick Check:

Solution

Step 1: Identify the method to clear errors

Step 2: Evaluate other options

Final Answer:

Quick Check:

Solution

Step 1: Understand the Try-Catch block behavior

Step 2: Analyze $Error[0] and output

Final Answer:

Quick Check:

Solution

Step 1: Check if error occurred

Step 2: Consider why $Error[0] is empty

Final Answer:

Quick Check:

Solution

Step 1: Identify correct error handling and clearing order

Step 2: Check other options for mistakes

Final Answer:

Quick Check:

Ready to prove it?

Step 1: Understand the purpose of `$Error`