ErrorAction parameter in PowerShell - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output when using ErrorAction SilentlyContinue?

Consider the following PowerShell command that tries to get a non-existent service with ErrorAction set to SilentlyContinue. What will be the output?

PowerShell

Get-Service -Name 'NoSuchService' -ErrorAction SilentlyContinue
Write-Output 'Command completed'

A No output from Get-Service, then 'Command completed' printed

B Error message about service not found, then 'Command completed' printed

C Script stops with an error and does not print 'Command completed'

D Empty output and no 'Command completed' printed

💡 Hint

ErrorAction SilentlyContinue suppresses error messages but lets the script continue.

Using ErrorAction SilentlyContinue hides the error message from Get-Service when the service does not exist, so no error is shown. The script continues and prints 'Command completed'.

💻 Command Output

intermediate

What happens with ErrorAction Stop on a failing command?

What is the result of running this PowerShell command that tries to get a non-existent service with ErrorAction set to Stop? Get-Service -Name 'NoSuchService' -ErrorAction Stop Write-Output 'This line runs'

PowerShell

Get-Service -Name 'NoSuchService' -ErrorAction Stop
Write-Output 'This line runs'

A Error message printed but script continues to print 'This line runs'

B Error is ignored and 'This line runs' is printed

C Error is thrown and script stops before printing 'This line runs'

D No error, empty output, and 'This line runs' printed

💡 Hint

ErrorAction Stop causes the script to stop on errors.

With ErrorAction Stop, the command throws a terminating error when the service is missing. The script stops immediately and does not run the next line.

📝 Syntax

advanced

Which command correctly uses ErrorAction to ignore errors?

Select the PowerShell command that correctly uses the ErrorAction parameter to ignore errors when deleting a file that may not exist.

A Remove-Item 'C:\temp\file.txt' -ErrorAction Ignore

B Remove-Item 'C:\temp\file.txt' -ErrorAction SilentlyContinue

C Remove-Item 'C:\temp\file.txt' -ErrorAction Continue

D Remove-Item 'C:\temp\file.txt' -ErrorAction Stop

💡 Hint

ErrorAction SilentlyContinue suppresses error messages and continues.

ErrorAction SilentlyContinue hides error messages and lets the script continue. 'Ignore' is not a valid value for ErrorAction, so option B causes an error.

🚀 Application

advanced

How to catch errors when using ErrorAction Stop?

You want to run a command that stops on error and catch that error to handle it gracefully. Which script snippet correctly does this?

A try { Get-Item 'C:\no_file.txt' } catch { Write-Output 'File not found' }

B Get-Item 'C:\no_file.txt' -ErrorAction Stop; if ($?) { Write-Output 'File found' } else { Write-Output 'File not found' }

C Get-Item 'C:\no_file.txt' -ErrorAction SilentlyContinue; Write-Output 'Checked file'

D try { Get-Item 'C:\no_file.txt' -ErrorAction Stop } catch { Write-Output 'File not found' }

💡 Hint

Use try/catch with ErrorAction Stop to catch terminating errors.

Only option D uses try/catch with ErrorAction Stop to catch the terminating error and handle it. Option D does not catch the error and will stop the script. Option D does not stop on error. Option D lacks ErrorAction Stop, so errors may be non-terminating and not caught.

🧠 Conceptual

expert

What is the difference between ErrorAction SilentlyContinue and Ignore?

In PowerShell, what is the difference between using ErrorAction SilentlyContinue and ErrorAction Ignore?

A Ignore is not a valid ErrorAction value and causes an error; SilentlyContinue suppresses errors

B SilentlyContinue and Ignore are synonyms and behave the same

C SilentlyContinue suppresses error messages but runs error handlers; Ignore suppresses errors completely and skips error handlers

D Ignore logs errors to a file; SilentlyContinue shows errors on screen

💡 Hint

Check PowerShell documentation for valid ErrorAction values.

Ignore is not a valid value for the ErrorAction parameter and will cause a parameter binding error. SilentlyContinue is valid and suppresses error messages while continuing execution.

Practice

1. What does the -ErrorAction SilentlyContinue parameter do in a PowerShell command?

easy

A. It displays error messages and pauses the script.

B. It stops the script immediately when an error occurs.

C. It suppresses error messages and continues running the script.

D. It logs errors to a file but shows no messages.

Solution

1. Step 1: Understand the SilentlyContinue behavior

   The SilentlyContinue value tells PowerShell to hide error messages and keep running the script without interruption.

2. Step 2: Compare with other ErrorAction values

   Unlike Stop, which halts the script, SilentlyContinue ignores errors silently, so the script continues smoothly.

3. Final Answer:

   It suppresses error messages and continues running the script. -> Option C

4. Quick Check:

   SilentlyContinue = suppress errors and continue [OK]

Hint: SilentlyContinue hides errors and keeps script running [OK]

Common Mistakes:

• Confusing SilentlyContinue with Stop which halts execution
• Thinking errors are logged automatically
• Assuming errors still display on screen

2. Which of the following is the correct syntax to stop a PowerShell script on error using the ErrorAction parameter?

easy

A. Get-Item 'C:\file.txt' -ErrorAction Stop

B. Get-Item 'C:\file.txt' -ErrorAction Ignore

C. Get-Item 'C:\file.txt' -ErrorAction SilentlyContinue

D. Get-Item 'C:\file.txt' -ErrorAction Continue

Solution

1. Step 1: Identify the ErrorAction value that stops script

   The Stop value causes the script to halt immediately when an error occurs.

2. Step 2: Verify syntax correctness

   The syntax uses -ErrorAction Stop correctly after the command.

3. Final Answer:

   Get-Item 'C:\file.txt' -ErrorAction Stop -> Option A

4. Quick Check:

   ErrorAction Stop halts script on error [OK]

Hint: Use -ErrorAction Stop to halt script on errors [OK]

Common Mistakes:

• Using Continue which only shows errors but continues
• Using SilentlyContinue which hides errors but continues
• Using non-existent value Ignore

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

Get-Item 'C:\nonexistentfile.txt' -ErrorAction SilentlyContinue; Write-Output 'Done'

medium

A. Only 'Done' is printed, no error message

B. Error message about missing file, then 'Done'

C. Script stops with error, no output

D. Nothing is printed

Solution

1. Step 1: Analyze Get-Item with SilentlyContinue

   The command tries to get a missing file but errors are suppressed silently.

2. Step 2: Check what Write-Output does after

   Since error is suppressed, the script continues and prints 'Done'.

3. Final Answer:

   Only 'Done' is printed, no error message -> Option A

4. Quick Check:

   SilentlyContinue hides errors, script continues [OK]

Hint: SilentlyContinue hides errors, next commands run [OK]

Common Mistakes:

• Expecting error message to show
• Thinking script stops on error
• Assuming no output at all

4. You wrote this script:

Get-Content 'C:\missing.txt' -ErrorAction Stop
Write-Output 'File read successfully'

But the script does not print 'File read successfully' when the file is missing. What is the fix?

medium

A. Change -ErrorAction Stop to -ErrorAction SilentlyContinue

B. Add try/catch block around Get-Content

C. Remove the Write-Output line

D. Change -ErrorAction Stop to -ErrorAction Continue

Solution

1. Step 1: Understand Stop behavior

   -ErrorAction Stop halts script on error, so Write-Output is not reached if file missing.

2. Step 2: Use try/catch to handle error gracefully

   Wrapping Get-Content in try/catch lets you catch the error and continue script safely.

3. Final Answer:

   Add try/catch block around Get-Content -> Option B

4. Quick Check:

   Stop halts script; try/catch handles errors [OK]

Hint: Use try/catch with Stop to handle errors safely [OK]

Common Mistakes:

• Changing Stop to SilentlyContinue hides errors but may ignore important failures
• Removing Write-Output loses useful output
• Using Continue still shows errors but doesn't stop script

5. You want to run a script that tries to delete multiple files. If a file is missing, you want to skip it silently and continue deleting others. But if a file exists but cannot be deleted due to permission issues, the script should stop immediately. Which ErrorAction usage fits this requirement?

hard

A. Use Remove-Item -ErrorAction Continue and handle errors in catch block

B. Use Remove-Item -ErrorAction Stop for all files

C. Use Remove-Item -ErrorAction SilentlyContinue for all files

D. Use Remove-Item -ErrorAction SilentlyContinue and check error type manually

Solution

1. Step 1: Understand SilentlyContinue hides all errors

   Using SilentlyContinue alone skips errors silently, so permission errors won't stop script.

2. Step 2: Combine SilentlyContinue with manual error check

   Run Remove-Item with SilentlyContinue, then check error details to stop on permission errors but ignore missing files.

3. Final Answer:

   Use Remove-Item -ErrorAction SilentlyContinue and check error type manually -> Option D

4. Quick Check:

   SilentlyContinue + manual check = skip missing, stop permission errors [OK]

Hint: SilentlyContinue plus manual error check handles complex cases [OK]

Common Mistakes:

• Using Stop stops on all errors including missing files
• Using Continue shows errors but does not stop script
• Ignoring error type and blindly continuing