Free NVIDIA NCP-AIO Actual Exam Questions - Question 8 Discussion
The data scientist alerts a system administrator to inspect the issue. The system administrator
suspects the disk IO is the issue.
What command should be used?
B, because tcpdump and nvidia-smi don’t cover storage, and htop is more general CPU/memory.
It’s B, since iostat directly reports disk IO stats, unlike the others.
B. iostat is really the go-to for checking disk IO stats directly. tcpdump (A) looks at network traffic, so that’s unrelated. nvidia-smi (C) is just for GPU monitoring, which doesn’t help with disk IO. htop (D) can show some IO info but it’s more about CPU and memory usage, not detailed disk performance. So iostat makes the most sense for pinpointing disk IO bottlenecks.
It’s B, since iostat directly monitors disk IO performance, perfect for this issue.
C imo, since the model uses GPU acceleration, checking GPU stats with nvidia-smi can rule out if the slowdown is due to GPU resource limits rather than disk IO. That might help narrow down the real bottleneck.
D imo, since htop gives a real-time overview of all system resources, including CPU, memory, and disk IO, it can quickly help spot if the disk is a bottleneck without needing extra permissions or installations. While iostat is more detailed for disk stats, htop’s accessibility makes it handy for initial checks.
Maybe D could also be useful here since htop gives a quick overview of system resources, including disk IO activity. It’s less detailed than iostat but might help the admin spot if the disk is being overused or if other processes are hogging resources. I guess if you want a fast general look first, htop works, then you can go deeper with iostat if needed.
Makes sense that it’s about disk IO, so B fits best. tcpdump (A) is for network stuff, and nvidia-smi (C) deals with GPU monitoring, which isn’t related here. htop (D) shows overall system load but doesn’t give detailed disk IO stats like iostat does. For pinpointing disk IO issues specifically, B is the go-to command.
True, htop can show disk usage stats but iostat (B) gives detailed disk IO metrics.
D imo, htop gives a quick overview of system resources including CPU, memory, and disk usage, which might help the admin spot disk IO bottlenecks indirectly. While iostat (B) is more specialized for disk IO, htop can be easier for a quick check before diving deeper. Plus, if there’s some other system strain affecting performance, htop could reveal that too.
Probably B, iostat is for disk IO stats.