220-1102 Question 81
Single answerProcessesA user reports that their Windows 10 laptop becomes sluggish a few minutes after startup. Applications open slowly, the cooling fan runs constantly, and the system is difficult to use. You open Task Manager and notice one process is consistently using 95-99% of the CPU, but the user does not recognize the process name. You need to determine whether the process is legitimate before ending it. What should you do FIRST?
- A
Use Task Manager to expand the process and check its file location and publisher details
- B
End the process immediately, then restart the computer to see whether performance improves
- C
Disable all startup applications in Task Manager so the process cannot run again
- D
Run Disk Cleanup to remove temporary files that may be causing the CPU spike
Show answer and explanation
Correct answer: A
Explanation
The best first action is to identify the process rather than immediately terminating it. In real-world support, technicians commonly use Task Manager to review process details and then verify the executable's location and publisher to determine whether the process belongs to Windows, a trusted vendor, or something suspicious. This aligns with standard troubleshooting methodology: identify the problem, establish a theory, and test safely before taking disruptive action. Microsoft documentation for Task Manager and general Windows troubleshooting supports using process details to investigate resource usage before ending tasks, especially because terminating essential processes can affect system stability.
- A. Correct.
Correct. When an unfamiliar process is consuming excessive CPU, the first step is to identify it before terminating it. In Windows, checking the process details, file location, and publisher information helps determine whether it is part of the operating system, a legitimate application, or potentially malicious. This is the safest initial action because some critical system processes can cause instability if ended improperly.
- B. Incorrect.
Incorrect. Ending a process before identifying it can crash an application, interrupt user work, or destabilize Windows if the process is a critical system component. While stopping a runaway process may sometimes be necessary, best practice is to verify what it is first.
- C. Incorrect.
Incorrect. Disabling all startup applications is too broad and does not identify the currently running process. It may also create unnecessary user impact by preventing legitimate software from loading. Startup troubleshooting can be useful later, but it is not the best first step for an unknown high-CPU process.
- D. Incorrect.
Incorrect. Disk Cleanup addresses storage-related issues such as temporary files and low disk space. It does not directly identify or resolve a specific process consuming nearly all CPU resources. This option reflects a common misconception of using general maintenance tools for a process-specific problem.