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.

Practice

1. What does the PowerShell command Get-Process do?

easy

A. Lists all running processes on the computer

B. Stops a running process immediately

C. Starts a new process

D. Deletes a file from the system

Solution

1. Step 1: Understand the purpose of Get-Process

   The command Get-Process is used to display information about processes currently running on the computer.

2. Step 2: Compare options with command function

   Only Lists all running processes on the computer correctly describes listing running processes. Other options describe different actions not related to Get-Process.

3. Final Answer:

   Lists all running processes on the computer -> Option A

4. Quick Check:

   Get-Process lists processes = A [OK]

Hint: Get-Process always shows running programs, not stopping them [OK]

Common Mistakes:

• Confusing Get-Process with Stop-Process
• Thinking Get-Process starts or deletes processes
• Assuming it modifies processes instead of listing

2. Which of the following is the correct syntax to stop a process named 'notepad' in PowerShell?

easy

A. Stop-Process notepad -Force

B. Get-Process -Stop notepad

C. Kill-Process -Name notepad

D. Stop-Process -Name notepad

Solution

1. Step 1: Identify correct cmdlet and parameter

   The cmdlet to stop a process is Stop-Process. The parameter to specify process by name is -Name.

2. Step 2: Validate syntax correctness

   Stop-Process -Name notepad uses correct cmdlet and parameter: Stop-Process -Name notepad. Get-Process -Stop notepad uses wrong cmdlet and parameter. Stop-Process notepad -Force misses the parameter name before 'notepad'. Kill-Process -Name notepad uses a non-existent cmdlet.

3. Final Answer:

   Stop-Process -Name notepad -> Option D

4. Quick Check:

   Stop-Process with -Name is correct syntax = C [OK]

Hint: Use Stop-Process with -Name to stop by process name [OK]

Common Mistakes:

• Omitting the -Name parameter
• Using incorrect cmdlet names like Kill-Process
• Placing process name without parameter name

3. What will be the output of this PowerShell command?

Get-Process -Name powershell | Stop-Process -PassThru

medium

A. Lists all running PowerShell processes without stopping them

B. Stops the PowerShell process and outputs the stopped process details

C. Throws an error because Stop-Process cannot be piped

D. Starts a new PowerShell process

Solution

1. Step 1: Understand the pipeline usage

   The command gets the process named 'powershell' and pipes it to Stop-Process. The -PassThru parameter makes Stop-Process output the stopped process object.

2. Step 2: Predict command behavior

   The process will be stopped, and its details will be shown as output. No error occurs because piping is supported.

3. Final Answer:

   Stops the PowerShell process and outputs the stopped process details -> Option B

4. Quick Check:

   Get-Process piped to Stop-Process with -PassThru stops and outputs = B [OK]

Hint: Stop-Process supports pipeline input and -PassThru outputs stopped process [OK]

Common Mistakes:

• Thinking Stop-Process cannot accept pipeline input
• Assuming it only lists processes without stopping
• Confusing -PassThru as a force stop

4. You run this command but get an error:

Stop-Process -Name

What is the problem and how to fix it?

medium

A. The command should be Get-Process -Name instead

B. Stop-Process does not use -Name; use -Id instead

C. Missing process name after -Name; add the process name

D. Stop-Process requires -Force parameter always

Solution

1. Step 1: Identify the error cause

   The command uses -Name parameter but does not specify the process name, causing a syntax error.

2. Step 2: Correct the command

   To fix, provide the process name after -Name, for example: Stop-Process -Name notepad.

3. Final Answer:

   Missing process name after -Name; add the process name -> Option C

4. Quick Check:

   Parameter -Name needs a value = D [OK]

Hint: Always provide a value after -Name parameter [OK]

Common Mistakes:

• Leaving -Name without a value
• Assuming -Force is always required
• Confusing Stop-Process with Get-Process

5. You want to stop all running instances of 'chrome' safely but only if they use more than 100 MB of memory. Which PowerShell command achieves this?

hard

A. Get-Process -Name chrome | Where-Object { $_.WorkingSet -gt 100000000 } | Stop-Process

B. Get-Process -Name chrome | Where-Object { $_.WorkingSet -gt 100MB } | Stop-Process

C. Stop-Process -Name chrome -MemoryLimit 100MB

D. Get-Process chrome | Stop-Process -MemoryUsage 100MB

Solution

1. Step 1: Understand memory property and filtering

   The WorkingSet property shows memory usage in bytes. 100 MB equals 100,000,000 bytes approximately.

2. Step 2: Filter processes by memory and stop them

   Get-Process -Name chrome | Where-Object { $_.WorkingSet -gt 100000000 } | Stop-Process correctly filters chrome processes with memory usage greater than 100,000,000 bytes and pipes them to Stop-Process. Get-Process -Name chrome | Where-Object { $_.WorkingSet -gt 100MB } | Stop-Process uses '100MB' which is invalid syntax. Options C and D use non-existent parameters.

3. Final Answer:

   Get-Process -Name chrome | Where-Object { $_.WorkingSet -gt 100000000 } | Stop-Process -> Option A

4. Quick Check:

   Memory in bytes filter with Where-Object = A [OK]

Hint: Memory is in bytes; use numeric value, not '100MB' string [OK]

Common Mistakes:

• Using '100MB' as a value instead of bytes
• Trying to use Stop-Process parameters that don't exist
• Not filtering processes before stopping