Free NVIDIA NCP-AIO Actual Exam Questions - Question 11 Discussion
stuck in a pending state indefinitely.
Which Slurm command can be used to view detailed information about all pending jobs and identify
the cause of the delay?
Maybe A, since scontrol shows detailed reasons if you check jobs individually.
A imo, since scontrol shows detailed pending job reasons directly.
Option A makes the most sense here because scontrol lets you drill into each job’s details, including why it’s stuck pending. sacct (B) is more for accounting and historical job data, not real-time job states. sinfo (C) shows node info and availability but won’t tell you why a job is waiting. So for figuring out the delay causes in pending jobs, scontrol is definitely the better fit.
A, it’s the only one that lists specific pending job causes clearly.
Probably A, since scontrol directly shows job details and pending reasons clearly.
A, because scontrol shows exact pending reasons, unlike sinfo or sacct.
Option A sounds right because scontrol can show the exact reason a job is stuck pending. sacct is more about past job records, so it won’t help with real-time issues. sinfo just shows node status, not job-specific info. So for figuring out why jobs don’t start, scontrol is the best tool here.
sacct (B) logs job accounting info, but it might not show real-time pending reasons. sinfo (C) lists node and partition status, which helps see resource availability. Could sinfo help spot why jobs wait?
It’s A. scontrol gives detailed info on job states and delays.