220-1201 Practice Question: A user complains that their computer is running…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Insufficient RAM

  Why it's wrong here

  When a system has insufficient RAM, it frequently resorts to "disk thrashing," where the operating system constantly swaps data between RAM and the slower hard drive (using the page file). While this process significantly degrades overall system performance and responsiveness due to high I/O operations, the CPU itself typically spends more time waiting for these I/O operations to complete rather than actively computing at 100% utilization. Therefore, low RAM causes slowness but not usually a pegged CPU.

• ✗

  CPU thermal throttling

  Why it's wrong here

  CPU thermal throttling is a protective mechanism that reduces the processor's clock speed and voltage when it detects excessive heat, preventing damage. While this action severely slows down the computer's performance, the CPU's usage percentage itself would not necessarily be consistently pegged at 100% at idle. Instead, monitoring tools would reveal significantly lower clock speeds than expected, even if the CPU is attempting to process a workload, indicating reduced capacity rather than constant full utilization.

• ✓

  Background malware or a driver issue

  Why this is correct

  Background malware often executes resource-intensive tasks such as cryptocurrency mining, data exfiltration, or denial-of-service attacks, which can consume nearly all available CPU cycles without user interaction. Similarly, a poorly written or corrupted device driver can enter an infinite loop or mismanage hardware interrupts, causing the kernel to constantly process erroneous requests. Both scenarios lead to persistent, unexplained 100% CPU utilization, making the system extremely slow and unresponsive.

• ✗

  Failing hard drive

  Why it's wrong here

  A failing hard drive primarily manifests as extremely slow data access, frequent system freezes, and potential data corruption due to read/write errors. While these issues severely impact system responsiveness and can lead to applications hanging, the CPU's primary role during such events is often waiting for the storage device to respond. Consequently, CPU utilization typically remains low or fluctuates, as the bottleneck is I/O-bound rather than CPU-bound, meaning the CPU is idle while waiting for the slow drive.

Go deeper

Related to this question