Terminating vs non-terminating errors in PowerShell - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to catch a terminating error using Try-Catch.

PowerShell

try {
    Get-Item 'C:\nonexistentfile.txt' -ErrorAction Stop
} catch [[1]] {
    Write-Host 'Error caught'
}

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

AException

BError

CWarning

DMessage

Attempts:

3 left

💡 Hint

Common Mistakes

Using catch without specifying Exception may not catch all terminating errors.

Using catch with 'Error' or 'Warning' is incorrect syntax.

The catch block catches terminating errors by specifying Exception.

2fill in blank

medium

Complete the code to continue execution after a non-terminating error.

PowerShell

Get-Item 'C:\nonexistentfile.txt' -ErrorAction [1]

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

AStop

BContinue

CIgnore

DSilentlyContinue

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Stop' causes the script to stop on errors.

Using 'Continue' displays the error message but continues execution.

The -ErrorAction SilentlyContinue parameter suppresses non-terminating errors and continues execution silently.

3fill in blank

hard

Fix the error in the Try-Catch block to handle terminating errors properly.

PowerShell

try {
    Get-Item 'C:\nonexistentfile.txt' -ErrorAction [1]
} catch {
    Write-Host 'Caught error'
}

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

ASilentlyContinue

BStop

CContinue

DIgnore

Attempts:

3 left

💡 Hint

Common Mistakes

Using SilentlyContinue prevents the error from being caught.

Using 'Continue' or 'Ignore' will not make the error terminating.

To make an error terminating and catch it, use -ErrorAction Stop.

4fill in blank

hard

Fill both blanks to create a hashtable of files with size greater than 1MB.

PowerShell

$files = Get-ChildItem | Where-Object { $_.Length [1] 1MB } | ForEach-Object { @{ Name = $_.Name; Size = $_.Length [2] 1MB } }

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

A>

B<

C/

D*

Attempts:

3 left

💡 Hint

Common Mistakes

Using < instead of > filters smaller files.

Using * instead of / causes incorrect size calculation.

The code filters files larger than 1MB using > and converts size to MB by dividing by 1MB.

5fill in blank

hard

Fill all three blanks to create a dictionary of file names and sizes for files larger than 500KB.

PowerShell

$result = @{
    [1] = Get-ChildItem | Where-Object { $_.Length [2] 500KB } | ForEach-Object { $_.Name }
    [3] = Get-ChildItem | Where-Object { $_.Length [2] 500KB } | ForEach-Object { $_.Length }
}

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

ANames

BSize

C>

DFiles

Attempts:

3 left

💡 Hint

Common Mistakes

Using < instead of > filters smaller files.

Mixing up dictionary keys causes confusion.

The dictionary keys are Files and Size. The filter uses > to select files larger than 500KB.

Practice

1. What is the main difference between terminating and non-terminating errors in PowerShell?

easy

A. Neither error affects script execution.

B. Terminating errors stop the script execution, non-terminating errors allow it to continue.

C. Both errors stop the script execution immediately.

D. Non-terminating errors stop the script execution, terminating errors allow it to continue.

Solution

1. Step 1: Understand error types in PowerShell

   Terminating errors cause the script to stop unless handled, while non-terminating errors only show warnings.

2. Step 2: Compare effects on script execution

   Terminating errors halt the script, non-terminating errors let it continue running.

3. Final Answer:

   Terminating errors stop the script execution, non-terminating errors allow it to continue. -> Option B

4. Quick Check:

   Terminating stops, non-terminating continues [OK]

Hint: Terminating errors stop scripts; non-terminating just warn [OK]

Common Mistakes:

• Confusing which error type stops the script
• Thinking non-terminating errors halt execution
• Assuming both errors behave the same

2. Which of the following is the correct way to make a non-terminating error behave like a terminating error in PowerShell?

easy

A. Use the parameter -ErrorAction Stop

B. Use the parameter -ErrorAction Continue

C. Use the parameter -ErrorAction SilentlyContinue

D. Use the parameter -ErrorAction Ignore

Solution

1. Step 1: Recall the -ErrorAction parameter options

   The -ErrorAction parameter controls how errors behave; Stop makes non-terminating errors act as terminating.

2. Step 2: Match the correct option

   -ErrorAction Stop forces the error to stop the script, unlike Continue or SilentlyContinue which allow continuation.

3. Final Answer:

   Use the parameter -ErrorAction Stop -> Option A

4. Quick Check:

   -ErrorAction Stop makes errors terminate [OK]

Hint: Use -ErrorAction Stop to force termination on errors [OK]

Common Mistakes:

• Using Continue or SilentlyContinue expecting termination
• Confusing Ignore with Stop
• Not knowing -ErrorAction controls error behavior

3. What will be the output of this PowerShell script?

Get-Item 'C:\nonexistentfile.txt' -ErrorAction Continue
Write-Output 'Script continues'

medium

A. No error message, only 'Script continues' is printed

B. Script stops with an error, 'Script continues' is not printed

C. Error message shown, then 'Script continues' is printed

D. Script crashes with no output

Solution

1. Step 1: Understand -ErrorAction Continue behavior

   With -ErrorAction Continue, non-terminating errors show error messages but do not stop the script.

2. Step 2: Trace script output

   The error about missing file is displayed, then the script prints 'Script continues'.

3. Final Answer:

   Error message shown, then 'Script continues' is printed -> Option C

4. Quick Check:

   Continue shows error but script runs [OK]

Hint: Continue shows error but script keeps running [OK]

Common Mistakes:

• Assuming script stops on Continue error
• Expecting no error message with Continue
• Confusing Continue with Stop

4. You run this script but it continues unexpectedly:

Try {
  Get-Item 'C:\nonexistentfile.txt' -ErrorAction Stop
} Catch {
  Write-Output 'Caught error'
}
Write-Output 'Script continues'

What is the likely cause?

medium

A. The script stops because the Catch block is missing

B. The error is non-terminating, so Try/Catch does not catch it

C. The script stops because -ErrorAction Stop causes termination without Catch

D. The error is terminating and caught, so script continues after Catch

Solution

1. Step 1: Analyze -ErrorAction Stop with Try/Catch

   Using -ErrorAction Stop makes the error terminating, so Try/Catch can catch it.

2. Step 2: Understand script flow after Catch

   The Catch block runs and outputs 'Caught error', then script continues to print 'Script continues'.

3. Final Answer:

   The error is terminating and caught, so script continues after Catch -> Option D

4. Quick Check:

   Terminating error caught, script continues [OK]

Hint: Try/Catch catches terminating errors with -ErrorAction Stop [OK]

Common Mistakes:

• Thinking non-terminating errors trigger Catch
• Assuming script stops without Catch block
• Confusing error action effects on Try/Catch

5. You want to run a script that tries to get multiple files, but you want it to stop immediately if any file is missing. Which approach correctly enforces this behavior?

hard

A. Use Get-Item with -ErrorAction Stop inside a Try/Catch block to handle errors.

B. Use Get-Item with -ErrorAction Continue and no error handling.

C. Use Get-Item with -ErrorAction SilentlyContinue and log errors later.

D. Use Get-Item without any -ErrorAction parameter.

Solution

1. Step 1: Identify requirement to stop on missing file

   Stopping immediately on error means using terminating errors with -ErrorAction Stop.

2. Step 2: Use Try/Catch to handle and control flow

   Wrapping calls in Try/Catch lets you catch the error and stop or handle it as needed.

3. Final Answer:

   Use Get-Item with -ErrorAction Stop inside a Try/Catch block to handle errors. -> Option A

4. Quick Check:

   Stop errors + Try/Catch = immediate stop [OK]

Hint: Use -ErrorAction Stop with Try/Catch to halt on errors [OK]

Common Mistakes:

• Using Continue or SilentlyContinue expecting stop
• Not using Try/Catch to handle terminating errors
• Ignoring error handling for critical failures