Verbose and debug output in PowerShell - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this PowerShell script with verbose enabled?

Consider this script run with the -Verbose flag:

function Test-Verbose {
  [CmdletBinding()] 
  param()
  Write-Verbose "Starting process"
  Write-Output "Process running"
  Write-Verbose "Process completed"
}

Test-Verbose -Verbose

What will be printed to the console?

PowerShell

function Test-Verbose {
  [CmdletBinding()] 
  param()
  Write-Verbose "Starting process"
  Write-Output "Process running"
  Write-Verbose "Process completed"
}

Test-Verbose -Verbose

A No output

B Process running

C

VERBOSE: Starting process
Process running
VERBOSE: Process completed

D

VERBOSE: Starting process
VERBOSE: Process completed

💡 Hint

Verbose messages appear only when the -Verbose flag is used.

Write-Verbose outputs messages only if the -Verbose flag is specified. Write-Output always prints to the console. So both verbose messages and the output line appear.

💻 Command Output

intermediate

What happens when you use Write-Debug without enabling debug?

Given this script:

function Test-Debug {
  [CmdletBinding()] 
  param()
  Write-Debug "Debug info"
  Write-Output "Normal output"
}

Test-Debug

What will be the output?

PowerShell

function Test-Debug {
  [CmdletBinding()] 
  param()
  Write-Debug "Debug info"
  Write-Output "Normal output"
}

Test-Debug

A DEBUG: Debug info

B

DEBUG: Debug info
Normal output

C No output

D Normal output

💡 Hint

Debug messages show only when debug preference is enabled.

Write-Debug messages are hidden unless the script is run with -Debug or $DebugPreference is set to 'Continue'. Without that, only Write-Output prints.

📝 Syntax

advanced

Which option correctly enables debug output in a PowerShell script?

You want to see debug messages from Write-Debug in your script. Which code snippet correctly enables debug output?

A

$DebugPreference = 'Continue'
Write-Debug "Debug message"

B

Set-Debug -Enable
Write-Debug "Debug message"

C

Enable-Debug
Write-Debug "Debug message"

D

$DebugMode = $true
Write-Debug "Debug message"

💡 Hint

PowerShell uses a preference variable to control debug message display.

Setting $DebugPreference to 'Continue' tells PowerShell to show debug messages. The other options are invalid commands or variables.

🚀 Application

advanced

How to capture verbose output into a variable in PowerShell?

You want to run a command and save its verbose messages into a variable for later use. Which approach works?

A $verboseOutput = Get-Process -Verbose 4>&1

B $verboseOutput = Get-Process -Verbose | Out-String

C $verboseOutput = & { Get-Process -Verbose 4>&1 }

D $verboseOutput = Get-Process -Verbose 3>&1

💡 Hint

Verbose messages are sent to stream 4 in PowerShell.

Redirecting stream 4 (verbose) to stream 1 (output) with 4>&1 captures verbose messages into the variable. Option A uses a script block unnecessarily, B captures only output, D redirects the wrong stream.

🧠 Conceptual

expert

What is the effect of setting $VerbosePreference to 'SilentlyContinue'?

In PowerShell, what happens if you set:

$VerbosePreference = 'SilentlyContinue'

and then run a script that uses Write-Verbose?

A Verbose messages are always shown regardless of -Verbose flag.

B Verbose messages are suppressed and not shown.

C Verbose messages cause an error.

D Verbose messages are shown only if -Verbose flag is used.

💡 Hint

The preference variable controls how verbose messages behave.

'SilentlyContinue' means PowerShell ignores verbose messages and does not display them.