Verbose and debug output in PowerShell - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable verbose output for the command.

PowerShell

Get-Process [1]

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

A-Debug

B-ErrorAction

C-Verbose

D-WarningAction

Attempts:

3 left

💡 Hint

Common Mistakes

Using -Debug instead of -Verbose, which shows debug messages, not verbose output.

Using -ErrorAction or -WarningAction which control error or warning behavior, not verbose output.

The -Verbose parameter enables detailed output about the command's operation.

2fill in blank

medium

Complete the code to write a debug message inside a script.

PowerShell

Write-[1] "This is a debug message"

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

AVerbose

BDebug

COutput

DWarning

Attempts:

3 left

💡 Hint

Common Mistakes

Using Write-Verbose instead of Write-Debug, which shows verbose messages.

Using Write-Warning or Write-Output which do not write debug messages.

Write-Debug writes a debug message that appears when debugging is enabled.

3fill in blank

hard

Fix the error in the script to enable debug messages.

PowerShell

$DebugPreference = '[1]'
Write-Debug "Debugging enabled"

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

AContinue

BOff

CSilentlyContinue

DStop

Attempts:

3 left

💡 Hint

Common Mistakes

Setting $DebugPreference to 'Off' disables debug messages.

Using 'SilentlyContinue' hides debug messages without stopping the script.

Setting $DebugPreference to 'Continue' enables debug messages to be shown.

4fill in blank

hard

Fill both blanks to write a verbose message and enable verbose output.

PowerShell

$VerbosePreference = '[1]'
Write-[2] "Verbose message here"

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

AContinue

BStop

CVerbose

DDebug

Attempts:

3 left

💡 Hint

Common Mistakes

Using $VerbosePreference = 'Stop' which blocks verbose messages.

Using Write-Debug instead of Write-Verbose for verbose messages.

Setting $VerbosePreference to 'Continue' enables verbose messages, and Write-Verbose writes the message.

5fill in blank

hard

Fill all three blanks to create a script that enables debug, verbose output, and writes both messages.

PowerShell

$DebugPreference = '[1]'
$VerbosePreference = '[2]'
Write-[3] "Debug message"; Write-Verbose "Verbose message"

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

AContinue

BStop

CDebug

DVerbose

Attempts:

3 left

💡 Hint

Common Mistakes

Setting preferences to 'Stop' which disables messages.

Using Write-Verbose instead of Write-Debug for the debug message.

Both $DebugPreference and $VerbosePreference must be set to 'Continue' to show messages. Write-Debug writes the debug message.

Practice

1. What is the main purpose of using Write-Verbose in a PowerShell script?

easy

A. To stop the script execution immediately

B. To write error messages to the console

C. To show extra informational messages when the script runs with -Verbose enabled

D. To create output files automatically

Solution

1. Step 1: Understand Write-Verbose purpose

   Write-Verbose is used to add extra informational messages that only show when the script is run with the -Verbose flag.

2. Step 2: Differentiate from other commands

   It does not stop execution, write errors, or create files. It only provides optional extra info.

3. Final Answer:

   To show extra informational messages when the script runs with -Verbose enabled -> Option C

4. Quick Check:

   Verbose messages = extra info shown with -Verbose [OK]

Hint: Verbose shows extra info only when -Verbose is used [OK]

Common Mistakes:

• Confusing Write-Verbose with Write-Error
• Expecting verbose messages without -Verbose flag
• Thinking Write-Verbose stops script execution

2. Which of the following is the correct syntax to enable debug messages in a PowerShell script?

easy

A. Run the script with -Debug parameter

B. Add Write-Debug -Enable inside the script

C. Use Set-DebugMode On before running the script

D. Include Enable-Debug command in the script

Solution

1. Step 1: Identify how to enable debug output

   Debug messages appear when the script is run with the -Debug parameter.

2. Step 2: Check other options for validity

   There is no Write-Debug -Enable, Set-DebugMode, or Enable-Debug commands in PowerShell.

3. Final Answer:

   Run the script with -Debug parameter -> Option A

4. Quick Check:

   Debug enabled by running script with -Debug [OK]

Hint: Use -Debug flag when running script to see debug messages [OK]

Common Mistakes:

• Trying to enable debug inside script with wrong commands
• Confusing debug enabling with verbose enabling
• Assuming debug is always on by default

3. What will be the output when running this script with -Verbose?

Write-Verbose "Starting process"
Write-Output "Process running"
Write-Verbose "Process completed"

medium

A. No output

B. Process running

C. Process running\nStarting process\nProcess completed

D. Starting process\nProcess running\nProcess completed

Solution

1. Step 1: Understand Write-Verbose output with -Verbose

   When run with -Verbose, all Write-Verbose messages show along with normal output.

2. Step 2: Identify output order

   The script writes verbose messages "Starting process" and "Process completed" plus the normal output "Process running" in order.

3. Final Answer:

   Starting process Process running Process completed -> Option D

4. Quick Check:

   Verbose + Output = all messages shown [OK]

Hint: Verbose messages show only with -Verbose, normal output always shows [OK]

Common Mistakes:

• Ignoring verbose messages in output
• Assuming verbose messages appear without -Verbose
• Mixing order of output lines

4. You wrote a script using Write-Debug messages, but no debug output appears when running it with -Debug. What is the most likely cause?

medium

A. The debug preference variable $DebugPreference is set to 'SilentlyContinue'

B. The script does not contain any Write-Debug commands

C. The script was run with -Verbose instead of -Debug

D. The script has syntax errors preventing debug output

Solution

1. Step 1: Check $DebugPreference effect

   Even with -Debug, if $DebugPreference is 'SilentlyContinue', debug messages won't show.

2. Step 2: Verify other options

   The script does not contain any Write-Debug commands means no debug commands, but question states debug commands exist. The script was run with -Verbose instead of -Debug is about verbose, not debug. The script has syntax errors preventing debug output would cause errors, not silent debug.

3. Final Answer:

   The debug preference variable $DebugPreference is set to 'SilentlyContinue' -> Option A

4. Quick Check:

   $DebugPreference controls debug output display [OK]

Hint: Check $DebugPreference; must not be 'SilentlyContinue' to see debug [OK]

Common Mistakes:

• Confusing -Verbose with -Debug flags
• Ignoring $DebugPreference variable
• Assuming debug always shows if -Debug used

5. You want to write a PowerShell script that shows detailed debug messages only when debugging is enabled, and verbose messages only when verbose is enabled. Which code snippet correctly implements this behavior?

hard

A. $DebugPreference = 'Continue'
Write-Output "Normal output"
Write-Debug "Debug info"
Write-Verbose "Verbose info"

B. Write-Debug "Debug info"
Write-Verbose "Verbose info"
Write-Output "Normal output"

C. if ($DebugPreference -eq 'SilentlyContinue') { Write-Debug "Debug info" }
if ($VerbosePreference -eq 'SilentlyContinue') { Write-Verbose "Verbose info" }
Write-Output "Normal output"

D. Write-Debug "Debug info"
Write-Verbose "Verbose info"
Write-Output "Normal output"
Set-Variable -Name DebugPreference -Value 'Continue'

Solution

1. Step 1: Understand default behavior of Write-Debug and Write-Verbose

   These commands automatically show messages only if debugging or verbose is enabled by running script with -Debug or -Verbose.

2. Step 2: Analyze code snippets

   Write-Debug "Debug info"
   Write-Verbose "Verbose info"
   Write-Output "Normal output"

   uses both commands directly, which is correct.

   $DebugPreference = 'Continue'
   Write-Output "Normal output"
   Write-Debug "Debug info"
   Write-Verbose "Verbose info"

   sets $DebugPreference to 'Continue' first, forcing debug messages to always show even without -Debug.

   if ($DebugPreference -eq 'SilentlyContinue') { Write-Debug "Debug info" }
   if ($VerbosePreference -eq 'SilentlyContinue') { Write-Verbose "Verbose info" }
   Write-Output "Normal output"

   checks for 'SilentlyContinue', showing messages when NOT enabled.

   Write-Debug "Debug info"
   Write-Verbose "Verbose info"
   Write-Output "Normal output"
   Set-Variable -Name DebugPreference -Value 'Continue'

   sets DebugPreference after messages, so ineffective.

3. Final Answer:

   Write-Debug "Debug info" Write-Verbose "Verbose info" Write-Output "Normal output" -> Option B

4. Quick Check:

   Write-Debug and Write-Verbose auto-check flags [OK]

Hint: Use Write-Debug and Write-Verbose directly; flags control output [OK]

Common Mistakes:

• Forcing preference to 'Continue' unconditionally
• Using incorrect condition like 'SilentlyContinue' in checks
• Setting preferences after output commands