220-1101 Question 408
Single answerLow performance input/output operations per second (IOPS)A graphic design workstation takes several minutes to open large project files, and users report that saving files causes the system to pause even though CPU and RAM usage remain low. In Task Manager and Resource Monitor, disk activity stays near 100% with long queue lengths during these slowdowns. The technician suspects low IOPS from the storage subsystem. Which action is the BEST way to improve performance?
- A
Replace the existing 5400 RPM hard drive with a solid-state drive (SSD)
- B
Increase the display resolution so the GPU handles more of the workload
- C
Add more system memory from 16 GB to 32 GB because disk queue length indicates a RAM bottleneck
- D
Disable automatic updates so background network traffic does not affect storage speed
Show answer and explanation
Correct answer: A
Explanation
This scenario focuses on identifying a storage bottleneck caused by low IOPS. When a system shows high disk utilization, long queue lengths, and pauses during file open/save operations while CPU and RAM remain low, the disk is the likely limiting component. In real-world support, replacing a mechanical HDD, especially a 5400 RPM model, with an SSD is one of the most effective ways to improve I/O responsiveness. SSDs provide far lower access latency and much higher IOPS than traditional spinning disks, which is why they dramatically improve tasks involving many small random reads and writes. This aligns with common vendor and industry best practices from storage manufacturers and operating system performance guidance: match the storage type to the workload, and use SSDs when higher I/O performance is needed.
- A. Correct.
Correct. Low IOPS means the storage device cannot service enough read/write operations quickly. A 5400 RPM HDD has much higher latency and far fewer I/O operations per second than an SSD. Replacing it with an SSD is a common and effective fix for sustained disk bottlenecks, especially when CPU and memory are not the limiting factors.
- B. Incorrect.
Incorrect. Display resolution affects GPU workload and video output, not the storage device's ability to process read/write requests. Users may experience lag from graphics issues, but the scenario specifically points to disk saturation and queue length, which are storage performance indicators.
- C. Incorrect.
Incorrect. Adding RAM can help if the system is paging heavily due to memory pressure, but the scenario states CPU and RAM usage remain low. Disk queue length alone does not prove a RAM bottleneck. This option reflects a common misconception that any disk slowness is caused by insufficient memory.
- D. Incorrect.
Incorrect. Background network traffic or update downloads can contribute to activity in some cases, but disabling updates does not address the core issue of low storage IOPS. The described symptoms are consistent with a slow disk subsystem under I/O-intensive workloads, not primarily a network problem.