Error logging patterns in PowerShell - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to catch errors using Try-Catch.

PowerShell

try {
    Get-Content 'file.txt' -ErrorAction Stop
} catch [[1]] {
    Write-Error $_.Exception.Message
}

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

AException

BError

CErrorAction

DCatch

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Error' instead of 'Exception' in catch block.

The catch block uses Exception to capture error details.

2fill in blank

medium

Complete the code to write error messages to a log file.

PowerShell

try {
    Remove-Item 'data.csv' -ErrorAction Stop
} catch {
    $_.Exception.Message | Out-File -FilePath [1] -Append
}

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

A'log.txt'

B'output.txt'

C'error.log'

D'data.csv'

Attempts:

3 left

💡 Hint

Common Mistakes

Logging errors to the wrong file name.

Errors are logged to 'error.log' file using Out-File with -Append.

3fill in blank

hard

Fix the error in the code to properly log errors with timestamps.

PowerShell

$timestamp = Get-Date -Format 'yyyy-MM-dd HH:mm:ss'
try {
    Get-Item 'missing.file' -ErrorAction Stop
} catch {
    "$timestamp - Error: [1]" | Out-File -FilePath 'error.log' -Append
}

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

A$_.Exception.Message

B$_.Exception

C$_.Error.Message

D$_.Message

Attempts:

3 left

💡 Hint

Common Mistakes

Using $_.Message which is undefined in this context.

The correct property to get the error message is Exception.Message.

4fill in blank

hard

Fill both blanks to create a function that logs errors with severity and message.

PowerShell

function Log-Error {
    param($errorMessage)
    $logEntry = "Severity: [1] - Message: [2]"
    $logEntry | Out-File -FilePath 'error.log' -Append
}

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

A'High'

B$errorMessage

C'Low'

D'Warning'

Attempts:

3 left

💡 Hint

Common Mistakes

Using a variable instead of a string for severity.

The severity is set to 'High' and the message uses the parameter $errorMessage.

5fill in blank

hard

Fill all three blanks to log errors with timestamp, severity, and message in a script.

PowerShell

$time = Get-Date -Format 'HH:mm:ss'
$severity = [1]
$errorMsg = [2]
"[$time] Severity: $severity - Error: $errorMsg" | [3] -FilePath 'error.log' -Append

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

A'Medium'

B$_.Exception.Message

COut-File

D'Critical'

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong cmdlet instead of Out-File.

Severity is set to 'Critical', error message is from Exception.Message, and Out-File writes to the log.

Practice

1. What is the main purpose of using try/catch blocks in PowerShell scripts for error logging?

easy

A. To automatically fix errors

B. To speed up script execution

C. To catch errors and handle them gracefully

D. To ignore all errors silently

Solution

1. Step 1: Understand the role of try/catch

   The try block runs code that might cause errors, and the catch block handles those errors.

2. Step 2: Purpose of error handling

   Using try/catch helps scripts manage errors without stopping abruptly, allowing logging or recovery.

3. Final Answer:

   To catch errors and handle them gracefully -> Option C

4. Quick Check:

   Error handling = catch errors [OK]

Hint: Try/catch blocks catch and handle errors safely [OK]

Common Mistakes:

• Thinking try/catch fixes errors automatically
• Believing try/catch speeds up scripts
• Assuming try/catch ignores errors

2. Which of the following is the correct syntax to write an error message with a timestamp to a log file in PowerShell?

easy

A. Add-Content error.log "$(Get-Date): Error occurred"

B. Write-Error "$(Get-Date): Error occurred" >> error.log

C. Write-Output "Error occurred at $(Get-Date)" > error.log

D. Write-Host "$(Get-Date): Error occurred" >> error.log

Solution

1. Step 1: Identify correct cmdlet for appending text

   Add-Content appends text to a file without overwriting it, suitable for logging.

2. Step 2: Check timestamp and message format

   Using "$(Get-Date): Error occurred" correctly adds a timestamp and message.

3. Final Answer:

   Add-Content error.log "$(Get-Date): Error occurred" -> Option A

4. Quick Check:

   Append log with Add-Content [OK]

Hint: Use Add-Content to append logs with timestamps [OK]

Common Mistakes:

• Using Write-Error which writes to error stream, not file
• Using Write-Host which outputs to console only
• Using > which overwrites the file instead of appending

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

try {
  Get-Item 'C:\nonexistentfile.txt'
} catch {
  Add-Content error.log "$(Get-Date): File not found error"
  'Error logged'
}

medium

A. No output, only error.log updated

B. Error logged

C. File not found error

D. Script stops with error

Solution

1. Step 1: Analyze try block

   The command tries to get a file that does not exist, causing an error.

2. Step 2: Analyze catch block

   The catch block appends a timestamped error message to error.log and outputs the string 'Error logged'.

3. Final Answer:

   Error logged -> Option B

4. Quick Check:

   Catch outputs message after logging [OK]

Hint: Catch block outputs text after logging error [OK]

Common Mistakes:

• Thinking no output appears because only file is updated
• Expecting script to stop on error
• Confusing error message with output string

4. Identify the error in this PowerShell error logging snippet:

try {
  Get-Content 'C:\missing.txt'
} catch {
  Write-Error "$(Get-Date): File missing"
  Add-Content error.log "File missing"
}

medium

A. Catch block should not write to error stream

B. Write-Error should be replaced with Write-Host to log properly

C. Try block syntax is incorrect

D. Add-Content should include timestamp for better logs

Solution

1. Step 1: Review logging commands

   Write-Error writes to error stream, which is okay for alerting, but Add-Content logs to file without timestamp.

2. Step 2: Importance of timestamps in logs

   Logs without timestamps make tracking errors over time difficult; adding $(Get-Date) improves log usefulness.

3. Final Answer:

   Add-Content should include timestamp for better logs -> Option D

4. Quick Check:

   Logs need timestamps for clarity [OK]

Hint: Always add timestamps when logging errors to files [OK]

Common Mistakes:

• Thinking Write-Error cannot be used in catch
• Ignoring importance of timestamps in logs
• Assuming try block syntax is wrong

5. You want to create a PowerShell script that logs errors with timestamps and the error message to a file, but only if the error is not a 'FileNotFoundException'. Which pattern correctly implements this?

hard

A. try {
# code
} catch [System.IO.FileNotFoundException] {
# ignore
} catch {
Add-Content error.log "$(Get-Date): $_"
}

B. try {
# code
} catch {
if ($_ -notlike '*FileNotFoundException*') {
Add-Content error.log "$(Get-Date): $_"
}
}

C. try {
# code
} catch {
Add-Content error.log "$(Get-Date): $_"
}

D. try {
# code
} catch [System.Exception] {
Add-Content error.log "$(Get-Date): $_"
}

Solution

1. Step 1: Understand exception filtering

   Using a typed catch block for FileNotFoundException allows ignoring that specific error.

2. Step 2: Use a general catch for other errors

   The second catch block logs all other errors with timestamp and message.

3. Final Answer:

   Typed catch ignores FileNotFoundException; general catch logs others -> Option A

4. Quick Check:

   Typed catch filters errors correctly [OK]

Hint: Use typed catch to skip specific errors [OK]

Common Mistakes:

• Logging all errors without filtering
• Using if condition incorrectly inside catch
• Not using typed catch blocks