A system administrator is investigating a malfunctioning background application on a Windows workstation that is consuming excessive CPU resources and maintaining unauthorized network connections. Arrange the command-line actions in the correct sequential order to identify, inspect, terminate, and verify the removal of the problematic process.
- 1Run `tasklist` to locate the application and identify its Process ID (PID).
- 2Run `netstat -ano` to map active network connections and listening ports directly to the identified PID.
- 3Run `taskkill /pid <PID> /t /f` to forcefully terminate the process along with any child processes it spawned.
- 4Run `tasklist /fi "IMAGENAME eq executable.exe"` to verify that no instances of the process remain active in memory.
Answer
The correct order of operations is: 1) Run `tasklist` to obtain the PID, 2) Run `netstat -ano` to inspect network sockets for that PID, 3) Run `taskkill /pid <PID> /t /f` to forcefully stop the process tree, and 4) Run `tasklist /fi "IMAGENAME eq executable.exe"` to verify complete termination.
The correct troubleshooting sequence begins with process identification via `tasklist`, followed by network socket inspection using `netstat -ano` to confirm connection ownership, forceful process tree termination via `taskkill /pid <PID> /t /f`, and concluding with filter verification via `tasklist /fi`.
Step-by-Step Solution
Key Concept
Windows Command-Line Process Management and Network Diagnostic Sequence