Try-Catch-Finally in PowerShell - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a try block in PowerShell.

PowerShell

try [1]

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

A<

B[

C(

D{

Attempts:

3 left

💡 Hint

Common Mistakes

Using parentheses or square brackets instead of curly braces.

Forgetting to open the block with any symbol.

In PowerShell, a try block starts with the keyword 'try' followed by an opening curly brace '{'.

2fill in blank

medium

Complete the code to catch an exception in PowerShell.

PowerShell

catch [1]

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

A(Exception)

B[Exception]

C{Exception}

D<Exception>

Attempts:

3 left

💡 Hint

Common Mistakes

Using parentheses or curly braces instead of square brackets.

Omitting the exception type brackets.

In PowerShell, the catch block can specify the exception type in square brackets, like [Exception].

3fill in blank

hard

Fix the error in the finally block syntax.

PowerShell

finally [1] Write-Host "Cleanup done" }

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

A{

B[

C(

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Using parentheses or square brackets instead of curly braces.

Forgetting to open the block with any symbol.

The finally block must start with an opening curly brace '{' to contain the code block.

4fill in blank

hard

Fill both blanks to complete a try-catch block that writes an error message.

PowerShell

try [1] Write-Host "Trying code" } catch [2] Write-Host "Error caught" }

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

A{

B[Exception]

D(Exception)

Attempts:

3 left

💡 Hint

Common Mistakes

Using parentheses instead of curly braces for blocks.

Mixing up exception type syntax.

The try block starts with '{' and the catch block also starts with '{'. The exception type is optional but here omitted.

5fill in blank

hard

Complete the code to complete a try-catch-finally block that handles errors and cleans up.

PowerShell

try { Write-Host "Start" } catch {{BLANK_2} Write-Host "Caught error" } finally { Write-Host "Done" }

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

A{

B[Exception]

D(

Attempts:

3 left

💡 Hint

Common Mistakes

Using parentheses instead of curly braces.

Omitting exception type brackets in catch.

Try and finally blocks start with '{'. Catch specifies exception type in '[Exception]' and also uses '{' to open the block.

Practice

1. What is the main purpose of the try block in PowerShell's Try-Catch-Finally structure?

easy

A. To always run code regardless of errors

B. To handle errors after they occur

C. To run code only if no errors happen

D. To run code that might cause an error

Solution

1. Step 1: Understand the role of try

   The try block contains code that might cause an error during execution.

2. Step 2: Differentiate from catch and finally

   catch handles errors after they happen, and finally runs code always, but try is where risky code runs.

3. Final Answer:

   To run code that might cause an error -> Option D

4. Quick Check:

   try runs risky code = A [OK]

Hint: Try block runs code that may fail [OK]

Common Mistakes:

• Confusing try with catch
• Thinking finally runs only on errors
• Believing try runs only if no errors

2. Which of the following is the correct syntax to catch an error in PowerShell?

easy

A. catch { Write-Host 'Error occurred' }

B. catch() { Write-Host 'Error occurred' }

C. catch: { Write-Host 'Error occurred' }

D. catch[] { Write-Host 'Error occurred' }

Solution

1. Step 1: Recall PowerShell catch syntax

   In PowerShell, catch is followed by a script block in curly braces without parentheses or other symbols.

2. Step 2: Identify correct syntax

   catch { Write-Host 'Error occurred' } uses catch { ... } which is correct; others add invalid symbols like parentheses or colons.

3. Final Answer:

   catch { Write-Host 'Error occurred' } -> Option A

4. Quick Check:

   Correct catch syntax uses braces only = A [OK]

Hint: Catch uses braces {} without parentheses [OK]

Common Mistakes:

• Adding parentheses after catch
• Using colon or brackets with catch
• Missing curly braces around catch code

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

try {
  1 / 0
  Write-Output 'Success'
} catch {
  Write-Output 'Error caught'
} finally {
  Write-Output 'Always runs'
}

medium

A. Error caught
Always runs

B. Success

C. Success
Always runs

D. Error caught

Solution

1. Step 1: Analyze the try block

   The code attempts to divide 1 by 0, which causes a runtime error, so the line Write-Output 'Success' is skipped.

2. Step 2: Check catch and finally behavior

   The catch block runs and outputs 'Error caught'. The finally block always runs and outputs 'Always runs'.

3. Final Answer:

   Error caught Always runs -> Option A

4. Quick Check:

   Error triggers catch, finally always runs = C [OK]

Hint: Error skips try rest, runs catch then finally [OK]

Common Mistakes:

• Assuming 'Success' prints despite error
• Ignoring finally block output
• Thinking catch runs only sometimes

4. Identify the error in this PowerShell script:

try {
  Write-Output 'Start'
} catch {
  Write-Output 'Error'
} finaly {
  Write-Output 'Done'
}

medium

A. Missing parentheses after catch

B. No error in the script

C. Misspelled 'finally' keyword

D. Missing semicolon after Write-Output

Solution

1. Step 1: Check spelling of keywords

   The script uses finaly instead of the correct finally keyword.

2. Step 2: Verify other syntax elements

   Catch does not require parentheses, and semicolons are optional in PowerShell; so these are not errors.

3. Final Answer:

   Misspelled 'finally' keyword -> Option C

4. Quick Check:

   Keyword spelling matters: 'finally' correct = B [OK]

Hint: Check spelling of 'finally' carefully [OK]

Common Mistakes:

• Thinking catch needs parentheses
• Expecting semicolons after commands
• Missing typo in finally keyword

5. You want to ensure a log file is always closed after writing, even if an error occurs during writing. Which Try-Catch-Finally structure correctly achieves this?

hard

A. try { Write-Output 'Write log' } catch { Close-LogFile } finally { Write-Output 'Error' }

B. try { Write-Output 'Write log' } catch { Write-Output 'Error' } finally { Close-LogFile }

C. catch { Write-Output 'Error' } try { Write-Output 'Write log' } finally { Close-LogFile }

D. try { Write-Output 'Write log' } finally { Close-LogFile } catch { Write-Output 'Error' }

Solution

1. Step 1: Understand Try-Catch-Finally order

   The correct order is try, then catch, then finally. The finally block always runs last.

2. Step 2: Identify correct usage for closing log file

   try { Write-Output 'Write log' } catch { Write-Output 'Error' } finally { Close-LogFile } correctly places Close-LogFile in finally to ensure it runs always, even if an error occurs.

3. Final Answer:

   try { Write-Output 'Write log' } catch { Write-Output 'Error' } finally { Close-LogFile } -> Option B

4. Quick Check:

   Try-Catch-Finally order with cleanup in finally = D [OK]

Hint: Put cleanup code in finally block [OK]

Common Mistakes:

• Placing finally before catch
• Putting cleanup in catch only
• Misordering Try-Catch-Finally blocks