Question 1
IntermediateUse Utilities to Analyze System Behavior · System performance monitoring utilities
A financial institution is running a latency-sensitive trading application on Red Hat Enterprise Linux 8. The application performance degrades intermittently. You capture the following iostat output during a degradation event:
avg-cpu: %user %nice %system %iowait %steal %idle
12.40 0.00 4.10 48.50 0.00 35.00
Device tps kB_read/s kB_wrtn/s kB_read kB_wrtn
nvme0n1 850.00 4500.0 125000.0 ... ...
Based on these metrics, which subsystem is the primary bottleneck and what is the most appropriate next step to analyze the root cause?
Answer and explanation
Correct answer: C
The iostat output shows a high %iowait (48.50%) and significant write throughput (125MB/s) relative to the read throughput, while the CPU idle time is 35%. This indicates the system is waiting on I/O completion rather than being CPU bound. The next logical step is to identify which process is generating this I/O using tools like iotop or pidstat -d. Checking CPU saturation would be incorrect as the CPU is largely idle waiting for I/O.
