Free NVIDIA NCP-AIN Actual Exam Questions - Question 13 Discussion

Question No. 13
[InfiniBand Troubleshooting]
You are troubleshooting InfiniBand connectivity issues in a cluster managed by the NVIDIA Network
Operator. You need to verify the status of the InfiniBand interfaces. Which command should you use
to check the state and link layer of InfiniBand interfaces on a node?
Select one option, then reveal solution.
US
UW
Usman W.
2026-02-22

Maybe D is the way to go since it gives a quick look at ib0’s link state without needing to guess device names, which is handy for basic status checks.

0
IP
Imran P.
2026-02-15

It’s A for me. While B needs you to know the exact device name and C is a bit outdated since ifconfig is less commonly used now, A actually lists all RDMA devices on the node which helps confirm whether the InfiniBand hardware is detected at all before digging deeper. It’s a good first step to verify the presence and status of any InfiniBand devices without guessing interface names. Plus, it works well alongside other commands once you know what devices are there.

0
SM
Sam M.
2026-02-14

Good point about needing the device name for B, but I’d say A is worth a look too since "rdma show devices" lists all RDMA devices and could help identify if the InfiniBand hardware is recognized at all. It’s a quick way to confirm device presence before digging into interfaces. So, I’d pick A for a broader check on device status rather than just interface state.

0
AT
Amir T.
2026-02-12

I think D makes the most sense here. It gives you the link state info directly for the ib0 interface without needing to figure out the device name like mlx5_0, which B requires. Plus, ip link is a pretty universal Linux command, so it’s reliable in most environments. A and C don’t seem as focused on showing both state and link layer details clearly. So yeah, going with D seems safer when you just want a straightforward status check.

0
AT
Amir T.
2026-02-12

C imo, ifconfig ib0 gives a quick snapshot of the InfiniBand interface status without needing to know device names. It directly references the ib0 interface, which is usually the default for InfiniBand on most nodes. Plus, it’s pretty straightforward for checking link layer details. A and B feel more low-level and might require extra info, while D is good but might not show all the specific InfiniBand link details as clearly as ifconfig does.

0
AT
Amir T.
2026-02-10

Maybe D because it shows interface state directly without extra device names needed.

0
AT
Amir T.
2026-01-27

D imo, ip link show dev ib0 gives a straightforward look at the interface state and link layer details without needing the specific device name like mlx5_0. It’s a standard Linux command that works regardless of underlying hardware naming and can quickly confirm if the interface is up or down. That makes it handy for troubleshooting in mixed environments or when device names aren’t known upfront.

A and B both need some extra device info or don’t show the link layer in detail, so they seem less practical here. C (ifconfig) is kind of outdated and might not give full InfiniBand-specific details

0
AV
Amit V.
2026-01-20

It’s A because rdma show devices lists all InfiniBand devices on the node without needing the exact device name, making it easier to verify interface status quickly.

0
VN
Vikas N.
2026-01-16

B, since ibstat gives detailed InfiniBand device info, including link status.

0
SV
Sami V.
2026-01-13

B looks right since ibstat shows InfiniBand device status including link layer and state. The others are more general or not specific enough.

0