Try-Catch-Finally in PowerShell - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this PowerShell try-catch-finally script?

Consider this script that tries to divide numbers and handles errors:

PowerShell

try {
  $result = 10 / 0
  Write-Output "Result: $result"
} catch {
  Write-Output "Error caught: $_"
} finally {
  Write-Output "Cleanup done"
}

A

Error caught: Attempted to divide by zero.
Cleanup done

B

Result: 0
Cleanup done

C

Error caught: $_
Cleanup done

D

Result: Infinity
Cleanup done

💡 Hint

Remember dividing by zero causes an exception caught by catch block.

Dividing by zero throws a runtime error. The catch block captures it and prints the error message. The finally block always runs, printing 'Cleanup done'.

🧠 Conceptual

intermediate

Which statement about PowerShell try-catch-finally is true?

Choose the correct statement about how try-catch-finally works in PowerShell.

A The catch block runs only if an error occurs in try.

B The finally block runs only if no error occurs in try.

C The catch block runs even if no error occurs in try.

D The finally block runs only if an error occurs in try.

💡 Hint

Think about when catch and finally blocks execute.

Catch runs only when an error happens in try. Finally always runs regardless of error.

🔧 Debug

advanced

Why does this PowerShell script not catch the error?

Look at this script and find why the catch block never runs:

PowerShell

try {
  Write-Output "Start"
  Get-Item 'C:\nonexistentfile.txt'
  Write-Output "End"
} catch {
  Write-Output "Caught error"
} finally {
  Write-Output "Done"
}

A The finally block prevents catch from running.

B The catch block is missing a parameter to catch the error.

C Get-Item does not throw terminating errors by default, so catch is skipped.

D The script syntax is invalid, so catch never runs.

💡 Hint

Check the type of error Get-Item throws by default.

Get-Item throws non-terminating errors by default, which do not trigger catch. To catch, use -ErrorAction Stop.

🚀 Application

advanced

What is the output of this script with nested try-catch-finally?

Analyze this nested try-catch-finally script and select the correct output:

PowerShell

try {
  Write-Output "Outer try start"
  try {
    Write-Output "Inner try start"
    throw "Inner error"
    Write-Output "Inner try end"
  } catch {
    Write-Output "Inner catch: $_"
  } finally {
    Write-Output "Inner finally"
  }
  Write-Output "Outer try end"
} catch {
  Write-Output "Outer catch: $_"
} finally {
  Write-Output "Outer finally"
}

A

Outer try start
Inner try start
Inner catch: Inner error
Inner finally
Outer finally

B

Outer try start
Inner try start
Inner finally
Outer catch: Inner error
Outer finally

C

Outer try start
Inner try start
Inner catch: Inner error
Outer catch: Inner error
Inner finally
Outer finally

D

Outer try start
Inner try start
Inner catch: Inner error
Inner finally
Outer try end
Outer finally

💡 Hint

Remember that the inner catch handles the inner throw, so outer catch is not triggered.

The inner throw is caught by the inner catch, so outer catch does not run. Both finally blocks run. Outer try continues after inner finally.

🧠 Conceptual

expert

What happens if a finally block itself throws an error in PowerShell?

Consider a try-catch-finally where the finally block throws an error. What is the behavior?

A The script terminates immediately without running catch or finally.

B The error from finally replaces any previous error and must be handled separately.

C The catch block catches errors from finally automatically.

D The error in finally is ignored and does not affect script execution.

💡 Hint

Think about error precedence when finally throws an error.

If finally throws an error, it overrides any previous error and must be handled separately. Catch does not catch errors from finally.