WhatIf and Confirm support in PowerShell - Step-by-Step Execution

Concept Flow - WhatIf and Confirm support

Start Script

↓

Check -WhatIf?

Yes→Show WhatIf message, skip action

No↓

Check -Confirm?

Yes→Ask user to confirm

↓

User says No?

Yes→Skip action

↓

Perform action

↓

End Script

The script first checks if -WhatIf is used to show the action without running it. If not, it checks -Confirm to ask user permission before running the action.

Execution Sample

PowerShell

Remove-Item -Path 'test.txt' -WhatIf
Remove-Item -Path 'test.txt' -Confirm

Shows how Remove-Item behaves with -WhatIf (shows message only) and -Confirm (asks user before deleting).

Execution Table

Step	Parameter	Action	User Input	Result	Output
1	-WhatIf	Check -WhatIf parameter	N/A	True	What if: Performing Remove-Item on 'test.txt'
2	-WhatIf	Skip actual Remove-Item	N/A	No deletion	What if: Performing Remove-Item on 'test.txt'
3	-Confirm	Check -Confirm parameter	N/A	True	Prompt user: "Are you sure you want to perform this action?"
4	-Confirm	User input	No	Action cancelled	Remove-Item not performed
5	-Confirm	User input	Yes	Action performed	File 'test.txt' deleted
6	No parameter	Perform Remove-Item directly	N/A	Action performed	File 'test.txt' deleted

💡 Execution stops after action is skipped or performed based on parameters and user input.

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 4/5	Final
WhatIf	False	True	True	True	True
Confirm	False	False	True	User input (Yes/No)	Depends on input
ActionPerformed	False	False	False	False or True	True if confirmed or no params

Key Moments - 3 Insights

Why does the script not delete the file when -WhatIf is used?

Because at Step 1 and 2 in the execution_table, -WhatIf is True, so the script only shows the message and skips the actual deletion.

What happens if the user answers 'No' to the confirmation prompt?

At Step 4, the user input is 'No', so the action is cancelled and the file is not deleted, as shown in the execution_table.

If neither -WhatIf nor -Confirm is used, what does the script do?

At Step 6, without parameters, the script performs the action directly and deletes the file.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output at Step 2 when -WhatIf is used?

A "File 'test.txt' deleted"

B "What if: Performing Remove-Item on 'test.txt'"

C "Remove-Item not performed"

D "Prompt user: Are you sure you want to perform this action?"

💡 Hint

Check the Output column at Step 2 in the execution_table.

At which step does the user input affect whether the action runs or not?

A Step 1

B Step 3

C Step 4

D Step 6

💡 Hint

Look at the User Input and Result columns in the execution_table.

If the user answers 'Yes' to the confirmation prompt, what is the final state of ActionPerformed?

A True

B Depends on -WhatIf

C False

D Unknown

💡 Hint

Check variable_tracker for ActionPerformed after Step 5.

Concept Snapshot

PowerShell supports -WhatIf and -Confirm parameters.
-WhatIf shows what would happen without running the action.
-Confirm asks user permission before running.
If -WhatIf is used, action is skipped but message shown.
If -Confirm is used, user input controls action.
Without these, action runs directly.

Full Transcript

This visual execution trace shows how PowerShell commands support -WhatIf and -Confirm parameters. When -WhatIf is used, the script shows a message about the action but does not perform it. When -Confirm is used, the script asks the user to confirm before running the action. If the user says no, the action is skipped. If yes, the action runs. Without these parameters, the action runs immediately. The execution table traces each step, showing parameter checks, user input, and results. The variable tracker shows how WhatIf, Confirm, and ActionPerformed change during execution. Key moments clarify common confusions about skipping actions and user confirmation. The quiz tests understanding of outputs and decision points. This helps beginners see exactly how these parameters control script behavior.