CV0-003 · Question #855
A technician deployed a VM with NL-SAS storage to host a critical application. Two weeks later, users have begun to report high application latency. Which of the following is the best action to correc
The correct answer is D. Migrate the data to flash storage.. NL-SAS (Near-Line SAS) uses high-capacity spinning magnetic disks optimized for archival and cold data, resulting in high I/O latency unsuitable for critical applications. Migrating to flash storage eliminates mechanical seek times and dramatically reduces latency.
Question
A technician deployed a VM with NL-SAS storage to host a critical application. Two weeks later, users have begun to report high application latency. Which of the following is the best action to correct the latency issue?
Options
- AIncrease the capacity of the data storage.
- BMigrate the data to SAS storage.
- CIncrease the CPU of the VM.
- DMigrate the data to flash storage.
How the community answered
(45 responses)- A13% (6)
- B7% (3)
- C4% (2)
- D76% (34)
Why each option
NL-SAS (Near-Line SAS) uses high-capacity spinning magnetic disks optimized for archival and cold data, resulting in high I/O latency unsuitable for critical applications. Migrating to flash storage eliminates mechanical seek times and dramatically reduces latency.
Increasing storage capacity adds more space but does not change the I/O performance characteristics of NL-SAS drives, leaving latency unchanged.
SAS drives are faster than NL-SAS due to higher RPM and better sustained throughput, but they are still spinning magnetic disks and cannot match the sub-millisecond latency of flash storage.
Increasing CPU resources addresses compute-bound bottlenecks, but the symptom - latency beginning two weeks after deployment with NL-SAS - points to storage I/O as the constraint, not processor utilization.
Flash storage - whether SATA SSD, SAS SSD, or NVMe - has no moving parts and achieves sub-millisecond I/O latency compared to the 4-8 ms average seek time of NL-SAS spinning disks. For a critical application experiencing user-reported latency, the storage I/O tier is the primary bottleneck when NL-SAS is in use. Migrating to flash directly resolves the mechanical disk latency that is degrading application response times.
Concept tested: Storage tier selection for application latency optimization
Source: https://www.snia.org/education/storage_networking_primer/storage_media
Topics
Community Discussion
No community discussion yet for this question.