Advanced functions (CmdletBinding) in PowerShell - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this advanced function call?

Consider this PowerShell advanced function with CmdletBinding. What will be the output when calling Get-Greeting -Name 'Alice'?

PowerShell

function Get-Greeting {
  [CmdletBinding()]
  param(
    [Parameter(Mandatory=$true)]
    [string]$Name
  )
  Write-Output "Hello, $Name!"
}

Get-Greeting -Name 'Alice'

A Hello, $Name!

B Error: Missing mandatory parameter 'Name'

C Hello, Alice!

D Hello, !

💡 Hint

Look at how the parameter is used inside the function and how the function is called.

The function uses CmdletBinding with a mandatory parameter 'Name'. When called with -Name 'Alice', it outputs 'Hello, Alice!'.

💻 Command Output

intermediate

What error does this advanced function produce?

What error will this PowerShell advanced function produce when called without parameters?

PowerShell

function Test-Param {
  [CmdletBinding()]
  param(
    [Parameter(Mandatory=$true)]
    [string]$InputValue
  )
  Write-Output $InputValue
}

Test-Param

A Error: Missing mandatory parameter 'InputValue'

B No output, function runs silently

C Error: Unexpected token 'Test-Param'

D Output: null

💡 Hint

Mandatory parameters require a value when calling the function.

Since 'InputValue' is mandatory, calling the function without it causes an error about the missing parameter.

📝 Syntax

advanced

Which option correctly defines an advanced function with CmdletBinding and a switch parameter?

Select the correct PowerShell function definition that uses CmdletBinding and includes a switch parameter named 'VerboseMode'.

A

function Show-Info {
  [CmdletBinding()]
  param(
    [switch]$VerboseMode
  )
  if ($VerboseMode) { Write-Output 'Verbose mode on' }
}

B

function Show-Info {
  param(
    [CmdletBinding()]
    [switch]$VerboseMode
  )
  if ($VerboseMode) { Write-Output 'Verbose mode on' }
}

C

function Show-Info {
  [CmdletBinding]
  param(
    [switch]$VerboseMode
  )
  if ($VerboseMode) { Write-Output 'Verbose mode on' }
}

D

function Show-Info {
  [CmdletBinding()]
  param(
    switch $VerboseMode
  )
  if ($VerboseMode) { Write-Output 'Verbose mode on' }
}

💡 Hint

CmdletBinding must be an attribute before param block, and switch parameters require [switch] type.

Option A correctly places [CmdletBinding()] before param and declares the switch parameter with [switch]. Other options have syntax errors or misplaced attributes.

🚀 Application

advanced

What is the output of this advanced function using Begin, Process, and End blocks?

Given this advanced function, what will be the output when calling Process-Numbers -Numbers 1,2,3?

PowerShell

function Process-Numbers {
  [CmdletBinding()]
  param(
    [int[]]$Numbers
  )
  begin {
    Write-Output 'Starting processing'
  }
  process {
    foreach ($num in $Numbers) {
      Write-Output ($num * 2)
    }
  }
  end {
    Write-Output 'Processing complete'
  }
}

Process-Numbers -Numbers 1,2,3

A [1, 2, 3]

B [2, 4, 6]

C [Starting processing, Processing complete]

D [Starting processing, 2, 4, 6, Processing complete]

💡 Hint

Begin runs once before processing, Process runs for each input, End runs after all processing.

The function writes 'Starting processing' once, then outputs each number doubled, then writes 'Processing complete'.

🔧 Debug

expert

Why does this advanced function fail to bind the parameter correctly?

This function is intended to accept pipeline input by property name. Why does it fail to bind the parameter when called with pipeline input?

PowerShell

function Get-UserName {
  [CmdletBinding()]
  param(
    [Parameter(Mandatory=$true, ValueFromPipelineByPropertyName=$true)]
    [string]$UserName
  )
  process {
    Write-Output "User: $UserName"
  }
}

# Pipeline input
$users = @(@{UserName='Bob'}, @{UserName='Carol'})
$users | Get-UserName

A The parameter name 'UserName' does not match the property name in the pipeline objects.

B The pipeline objects are hashtables, which do not support property binding as expected.

C The function does not declare the parameter as accepting pipeline input by property name correctly.

D The function lacks a 'begin' block to initialize pipeline processing.

💡 Hint

Consider how PowerShell binds pipeline input by property name and the type of objects passed.

Hashtable objects do not have properties accessible by property name binding. PowerShell expects objects with properties, not hashtables, for ValueFromPipelineByPropertyName to work.