Process management (Get/Stop-Process) in PowerShell - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this PowerShell command?

Consider the following command run on a system with multiple running processes named 'notepad':

Get-Process -Name notepad | Select-Object -First 1 | Format-Table -Property Id, ProcessName -HideTableHeaders

What will this command output?

PowerShell

Get-Process -Name notepad | Select-Object -First 1 | Format-Table -Property Id, ProcessName -HideTableHeaders

A Displays all 'notepad' processes with Id and ProcessName including headers

B Displays the Id and ProcessName of the first 'notepad' process found, without table headers

C Throws an error because Format-Table cannot be used with Select-Object

D Displays only the ProcessName of all 'notepad' processes

💡 Hint

Think about how Select-Object and Format-Table work together and what -HideTableHeaders does.

The command gets all 'notepad' processes, selects only the first one, then formats the output to show only Id and ProcessName without headers. It does not throw an error.

📝 Syntax

intermediate

Which command correctly stops all running 'calc' processes?

You want to stop all processes named 'calc' using PowerShell. Which of the following commands will do this correctly?

A Stop-Process -ProcessName calc

B Stop-Process calc

C Stop-Process -Id calc

D Stop-Process -Name calc

💡 Hint

Check the parameter names for Stop-Process.

The correct parameter to specify process by name is '-Name'. Option D uses it correctly. Option D misses the parameter name, C uses a wrong parameter name, and D expects a numeric Id, not a name.

🔧 Debug

advanced

Why does this script fail to stop the process?

You run this script to stop a process named 'example':

$proc = Get-Process example
Stop-Process $proc

But it throws an error. What is the cause?

A Stop-Process expects process Id or name, not a process object

B You need to convert $proc to string before passing

C Stop-Process requires the -Name parameter explicitly

D Get-Process did not find any process named 'example'

💡 Hint

Check what type of input Stop-Process accepts.

Stop-Process does not accept a process object directly. It requires either the process Id or the process name as a string or integer. Passing the object causes an error.

🚀 Application

advanced

How to safely stop a process only if it is running?

You want to stop a process named 'myapp' only if it is currently running, without causing errors if it is not. Which script snippet achieves this?

A Get-Process -Name myapp | Stop-Process

B Stop-Process -Name myapp -ErrorAction SilentlyContinue

C if (Get-Process -Name myapp -ErrorAction SilentlyContinue) { Stop-Process -Name myapp }

D Stop-Process -Name myapp -Force

💡 Hint

Think about checking existence before stopping.

Option C checks if the process exists and only then stops it, avoiding errors. Option C tries to stop without checking, but errors are silenced (may hide issues). Option C pipes objects which Stop-Process accepts, so it is valid. Option C forces stop but does not check existence.

🧠 Conceptual

expert

What is the effect of using Stop-Process with the -Force parameter?

In PowerShell, what does the -Force parameter do when used with Stop-Process?

A It forces the process to stop immediately, ignoring any prompts or errors

B It only stops processes running with administrator privileges

C It delays stopping the process until all child processes are stopped

D It logs the stop action but does not actually stop the process

💡 Hint

Consider what 'force' usually means in commands.

The -Force parameter forces the process to stop immediately, bypassing any prompts or protections. It does not delay or log without stopping.