Why error handling prevents script failure in PowerShell - Challenge Your Understanding

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output when error handling is used?

Consider this PowerShell script that tries to read a file. What will be the output when the file does not exist?

PowerShell

try {
  Get-Content -Path 'nonexistentfile.txt' -ErrorAction Stop
  Write-Output 'File read successfully'
} catch {
  Write-Output 'Error caught: File not found'
}

A Get-Content : Cannot find path 'nonexistentfile.txt' because it does not exist.

B Error caught: File not found

C File read successfully

D Script stops with an unhandled exception

💡 Hint

Think about what happens when the file is missing and how the catch block works.

The try block attempts to read a file that does not exist, which causes an error. The catch block catches this error and outputs a friendly message instead of letting the script fail.

🧠 Conceptual

intermediate

Why use error handling in scripts?

Why is it important to use error handling like try-catch in scripts?

A To ignore all errors silently without any message

B To make the script run faster by skipping error checks

C To stop the script immediately when an error occurs

D To catch errors and allow the script to continue or handle them gracefully

💡 Hint

Think about what happens if errors are not handled.

Error handling lets the script catch problems and respond without crashing, so the script can continue or provide useful feedback.

🔧 Debug

advanced

Identify the error handling mistake

This script is supposed to catch errors but fails to do so. What is the mistake?

PowerShell

try {
  Get-Content -Path 'missingfile.txt' -ErrorAction SilentlyContinue
  Write-Output 'File read'
} catch {
  Write-Output 'Error caught'
}

A The -ErrorAction SilentlyContinue prevents errors from reaching catch

B The Write-Output command is inside the try block

C Get-Content does not throw errors for missing files

D The catch block is missing a closing brace

💡 Hint

Check how -ErrorAction affects error handling.

Using -ErrorAction SilentlyContinue tells PowerShell to suppress errors, so the catch block never runs because no terminating error occurs.

💻 Command Output

advanced

What happens without error handling?

What will be the output of this script when the file does not exist?

PowerShell

Get-Content -Path 'nofile.txt'
Write-Output 'This line runs after file read'

A

Get-Content : Cannot find path 'nofile.txt' because it does not exist.
This line runs after file read

B Get-Content : Cannot find path 'nofile.txt' because it does not exist.

C Script stops with an unhandled exception before the second line

D This line runs after file read

💡 Hint

Think about what happens when an error is not caught.

Without error handling, Get-Content writes a non-terminating error message but continues execution, so the next line runs.

🚀 Application

expert

How to ensure script continues after error?

You want your PowerShell script to try reading a file and if it fails, print a message but continue running other commands. Which script achieves this?

A

Get-Content 'file.txt'
Write-Output 'File missing'
Write-Output 'Script continues'

B

Get-Content 'file.txt' -ErrorAction SilentlyContinue
Write-Output 'File missing'
Write-Output 'Script continues'

C

try {
  Get-Content 'file.txt' -ErrorAction Stop
} catch {
  Write-Output 'File missing'
}
Write-Output 'Script continues'

D

try {
  Get-Content 'file.txt'
} catch {
  Write-Output 'File missing'
}
Write-Output 'Script continues'

💡 Hint

Consider how to make errors terminating to trigger catch and continue script.

Option C uses -ErrorAction Stop to make errors terminating so catch runs, allowing the script to handle the error and continue.