NVIDIA NCP-AIO Exam - Topic 4 Question 9 Discussion

Actual exam question for NVIDIA's NCP-AIO exam

Question #: 9
Topic #: 4

When troubleshooting Slurm job scheduling issues, a common source of problems is jobs getting 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?

Ascontrol

Bsacct

Csinfo

Show Suggested Answer

Suggested Answer: A

Comprehensive and Detailed Explanation From Exact Extract:

The Slurm command scontrol provides detailed job control and information capabilities. Using scontrol (e.g., scontrol show job <jobid>) can reveal comprehensive details about jobs, including pending jobs, and the specific reasons why they are delayed or blocked. It is the go-to command for in-depth troubleshooting of job states. While sacct provides accounting information and sinfo displays node and partition status, neither provides as detailed or actionable information on pending job causes as scontrol.

by Derick at Jan 05, 2026, 05:16 AM

Limited Time Offer

25%

Off

Get Premium NCP-AIO Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Anglea

2 months ago

True, but sacct won't show pending states like scontrol.

upvoted 0 times

...

Angella

2 months ago

But what about B) sacct? It tracks job accounting.

upvoted 0 times

...

Eleonora

3 months ago

I agree, scontrol shows job details.

upvoted 0 times

...

Luke

3 months ago

I think it's A) scontrol.

upvoted 0 times

...

Van

3 months ago

Wait, are you sure? I thought pending jobs were just stuck forever!

upvoted 0 times

...

Luisa

3 months ago

Really? I always use sinfo for that.

upvoted 0 times

...

Tonette

3 months ago

No way, it's scontrol!

upvoted 0 times

...

Emiko

3 months ago

I thought it was sacct?

upvoted 0 times

...

Carlota

4 months ago

It's definitely scontrol for checking pending jobs.

upvoted 0 times

...

Gene

4 months ago

Ah, the age-old Slurm troubleshooting dilemma. I'd go with scontrol - it's like the Swiss Army knife of Slurm commands.

upvoted 0 times

...

Ruby

4 months ago

Haha, good thing I read the question carefully. I was about to say "squeue" but that's just for listing jobs, not digging into the details.

upvoted 0 times

...

Timmy

5 months ago

sacct is the way to go! It gives you a comprehensive history of the job's lifecycle, which can be super helpful in troubleshooting.

upvoted 0 times

...

Tuyet

5 months ago

Hmm, I'd say scontrol is the best option here. It provides more detailed information about the job itself and the reasons for the delay.

upvoted 0 times

...

Melita

5 months ago

The sinfo command is the way to go! It gives you a clear picture of the cluster's status and pending jobs.

upvoted 0 times

...

Ivette

5 months ago

I have a vague memory of using scontrol to check job statuses, so that might be the answer we need for this question.

upvoted 0 times

...

Tyisha

5 months ago

I feel like sinfo is more about the state of nodes rather than individual jobs, so it might not be the right choice here.

upvoted 0 times

...

Yolando

6 months ago

I remember practicing with sacct for job accounting, but I don't think it shows pending jobs specifically.

upvoted 0 times

...

Trinidad

6 months ago

I think the command we need is scontrol, but I'm not entirely sure if it gives detailed info on pending jobs.

upvoted 0 times

...

Nana

6 months ago

I'm pretty confident the answer is C. sinfo is the command that provides the most comprehensive information about the state of the cluster and pending jobs. That's the one I'll go with.

upvoted 0 times

...

Johnetta

6 months ago

Okay, I've used sinfo before to check cluster status, so that's probably the way to go here. It should give me a good overview of what's causing those pending jobs.

upvoted 0 times

...

Roosevelt

6 months ago

Ugh, I'm not too familiar with Slurm commands. Is scontrol the one that shows job details? Or is that sacct? I'll have to think this through carefully.

upvoted 0 times

...