Throw statement in PowerShell - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this PowerShell script with a throw statement?

Consider the following PowerShell script. What will it output when run?

PowerShell

try {
  Write-Output "Start"
  throw "Error occurred"
  Write-Output "End"
} catch {
  Write-Output "Caught: $_"
}

A

Start
Caught: Error occurred

B

Start
End

C Caught: Error occurred

D

Start
End
Caught: Error occurred

💡 Hint

Remember that throw stops the script flow and jumps to catch.

The script writes "Start", then throws an error which is caught by catch. "End" is never printed.

💻 Command Output

intermediate

What error message does this throw statement produce?

What error message will this PowerShell code produce?

PowerShell

throw "File not found"

A Exception calling "throw" with "1" argument(s): "File not found"

B Throw: File not found

C Terminating error: File not found

D File not found

💡 Hint

Throw produces a terminating error with the message you provide.

Throw creates a terminating error with the message "File not found" shown as a terminating error.

🔧 Debug

advanced

Why does this PowerShell script not catch the thrown error?

Examine the script below. Why does the catch block not run?

PowerShell

try {
  throw "Oops"
} finally {
  Write-Output "Cleaning up"
}
Write-Output "Done"

A Because throw inside try without catch causes script to stop immediately

B Because finally blocks prevent catch from running

C Because Write-Output after finally stops the error

D Because there is no catch block to handle the throw

💡 Hint

Catch is needed to handle errors thrown in try.

The script has no catch block, so the thrown error is not caught. Finally runs regardless.

🚀 Application

advanced

Which script correctly throws a custom error with a specific error ID?

You want to throw an error with message "Invalid input" and error ID "InputError". Which script does this correctly?

A throw [System.Management.Automation.ErrorRecord]::new((New-Object System.Exception('Invalid input')), 'InputError', [System.Management.Automation.ErrorCategory]::InvalidArgument, $null)

B throw [System.Management.Automation.ErrorRecord]::new('Invalid input', 'InputError', [System.Management.Automation.ErrorCategory]::InvalidArgument, $null)

C throw [System.Exception]::new('Invalid input', 'InputError')

D throw New-Object System.Exception('Invalid input') -ErrorId 'InputError'

💡 Hint

Throwing a custom error record requires wrapping an exception inside ErrorRecord.

Option A correctly creates an ErrorRecord with an Exception, error ID, category, and target, then throws it.

🧠 Conceptual

expert

What happens when a throw statement is used inside a PowerShell function without try-catch?

If a PowerShell function contains a throw statement but no try-catch, what is the behavior when the function is called?

A The error is silently ignored and the function returns null

B The error is thrown and stops the script unless the caller handles it

C The function automatically catches the error and returns an error object

D The error is converted to a warning and script continues

💡 Hint

Throw creates a terminating error unless caught.

Without try-catch, the throw causes a terminating error that stops the script unless the caller handles it.