NVIDIA NCP-AII Practice Test 83
Question 820
During an NVIDIA AI factory acceptance test, engineers discover: A tuning script forces socket transport after a previous RDMA outage and measured NCCL bandwidth remains low. Which TWO complementary elements are needed: the correct technical action and the strongest independent diagnostic evidence? Select TWO answers.
- Capture and rationalize NCCL environment settings and selected interfaces with each repeatable benchmark.
- Test NCCL throughput and latency across representative message sizes and node counts with repeatable conditions.
- Inspect RDMA device state, NCCL transport logs, port counters, rank mapping and cross-node bandwidth.
- Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings.
- Inspect NCCL debug traces, selected network plugin, environment variables and host network topology.
Explanation
Correct Answers
A:This is an appropriate correction for NCCL transport environment and benchmark reproducibility: Capture and rationalize NCCL environment settings and selected interfaces with each repeatable benchmark. Observed scenario: A tuning script forces socket transport after a previous RDMA outage and measured NCCL bandwidth remains low. The governing mechanism is: Environment overrides can change transport or algorithm choice; performance claims require documented configuration.
E:This is the direct operational evidence to investigate: Inspect NCCL debug traces, selected network plugin, environment variables and host network topology. Observed scenario: A tuning script forces socket transport after a previous RDMA outage and measured NCCL bandwidth remains low. The governing mechanism is: Environment overrides can change transport or algorithm choice; performance claims require documented configuration.
Incorrect Answers
B:That option concerns NCCL bandwidth and latency payload sweep. Environment overrides can change transport or algorithm choice; performance claims require documented configuration.
C:This alternative is relevant to Inter-node NCCL east-west RDMA readiness but does not directly resolve the current NCCL transport environment and benchmark reproducibility issue: Inspect RDMA device state, NCCL transport logs, port counters, rank mapping and cross-node bandwidth. Observed scenario: A tuning script forces socket transport after a previous RDMA outage and measured NCCL bandwidth remains low.
D:This tempting but unsafe shortcut is not a sufficient remediation for NCCL transport environment and benchmark reproducibility: Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings. A tuning script forces socket transport after a previous RDMA outage and measured NCCL bandwidth remains low. Environment overrides can change transport or algorithm choice; performance claims require documented configuration.
Question 821
A production GPU cluster review identifies this condition: Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides. Which operational response is MOST appropriate to address the root issue? Select ONE best answer.
- Capture and rationalize NCCL environment settings and selected interfaces with each repeatable benchmark.
- Validate the complete rank count, GPU mapping and launch environment on all participating nodes.
- Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings.
- Schedule supported active DCGM diagnostics for the relevant GPU class and investigate detailed failures.
Explanation
Correct Answer
A:This is an appropriate correction for NCCL transport environment and benchmark reproducibility: Capture and rationalize NCCL environment settings and selected interfaces with each repeatable benchmark. Observed scenario: Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides.
Incorrect Answers
B:This alternative is relevant to NCCL communicator and rank-to-device consistency but does not directly resolve the current NCCL transport environment and benchmark reproducibility issue: Validate the complete rank count, GPU mapping and launch environment on all participating nodes. Observed scenario: Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides.
C:This tempting but unsafe shortcut is not a sufficient remediation for NCCL transport environment and benchmark reproducibility: Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings. Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides.
D:This alternative is relevant to DCGM active single-node diagnostic suites but does not directly resolve the current NCCL transport environment and benchmark reproducibility issue: Schedule supported active DCGM diagnostics for the relevant GPU class and investigate detailed failures. Observed scenario: Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides.
Question 822
In a professional AI infrastructure deployment, a technician observes: Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides. Which underlying infrastructure principle BEST explains the issue? Select ONE best answer.
- Local NVLink health does not establish end-to-end east-west cluster communication across NICs and switches.
- Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings.
- Environment overrides can change transport or algorithm choice; performance claims require documented configuration.
- Repeated collective communication can uncover unstable links, transport state and intermittent rank failures that smoke tests miss.
Explanation
Correct Answer
C:This is the governing infrastructure principle: Environment overrides can change transport or algorithm choice; performance claims require documented configuration. Observed scenario: Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides.
Incorrect Answers
A:This alternative is relevant to Inter-node NCCL east-west RDMA readiness but does not directly resolve the current NCCL transport environment and benchmark reproducibility issue: Local NVLink health does not establish end-to-end east-west cluster communication across NICs and switches. Observed scenario: Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides.
B:This tempting but unsafe shortcut is not a sufficient remediation for NCCL transport environment and benchmark reproducibility: Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings. Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides. Environment overrides can change transport or algorithm choice; performance claims require documented configuration.
D:That option concerns Multi-node NCCL repeated burn-in. The acceptance condition is: Benchmark runs can be repeated with the same approved transport and explainable performance changes.
Question 823
The cluster operations team needs to evaluate this situation: Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides. Which diagnostic evidence should be obtained FIRST to substantiate the likely fault or configuration gap? Select ONE best answer.
- Inspect RDMA device state, NCCL transport logs, port counters, rank mapping and cross-node bandwidth.
- Inspect process lists, world-size and rank variables, GPU device assignments and NCCL initialization logs.
- Inspect NCCL debug traces, selected network plugin, environment variables and host network topology.
- Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings.
Explanation
Correct Answer
C:This is the direct operational evidence to investigate: Inspect NCCL debug traces, selected network plugin, environment variables and host network topology. Observed scenario: Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides.
Incorrect Answers
A:This alternative is relevant to Inter-node NCCL east-west RDMA readiness but does not directly resolve the current NCCL transport environment and benchmark reproducibility issue: Inspect RDMA device state, NCCL transport logs, port counters, rank mapping and cross-node bandwidth. Observed scenario: Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides.
B:This alternative is relevant to NCCL communicator and rank-to-device consistency but does not directly resolve the current NCCL transport environment and benchmark reproducibility issue: Inspect process lists, world-size and rank variables, GPU device assignments and NCCL initialization logs. Observed scenario: Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides.
D:This tempting but unsafe shortcut is not a sufficient remediation for NCCL transport environment and benchmark reproducibility: Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings. Observed scenario: Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides. The governing mechanism is: Environment overrides can change transport or algorithm choice; performance claims require documented configuration. The proportionate action is: Capture and rationalize NCCL environment settings and selected interfaces with each repeatable benchmark.
Question 824
At a multi-node AI infrastructure handoff, the team records: Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides. After corrective work, which observable result BEST confirms that the requirement is met? Select ONE best answer.
- Every planned rank completes sustained correct collectives with throughput and error levels within acceptance limits.
- Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings.
- Benchmark runs can be repeated with the same approved transport and explainable performance changes.
- Every intended node is accounted for and deviations are dispositioned before workload benchmarking begins.
Explanation
Correct Answer
C:This is an observable verified result, not merely a claimed configuration change: Benchmark runs can be repeated with the same approved transport and explainable performance changes. Observed scenario: Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides.
Incorrect Answers
A:That option concerns Multi-node NCCL repeated burn-in. Environment overrides can change transport or algorithm choice; performance claims require documented configuration.
B:This tempting but unsafe shortcut is not a sufficient remediation for NCCL transport environment and benchmark reproducibility: Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings. Observed scenario: Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides. The governing mechanism is: Environment overrides can change transport or algorithm choice; performance claims require documented configuration. The proportionate action is: Capture and rationalize NCCL environment settings and selected interfaces with each repeatable benchmark. A direct check is: Inspect NCCL debug traces, selected network plugin, environment variables and host network topology. The acceptance condition is: Benchmark runs can be repeated with the same approved transport and explainable performance changes.
D:This alternative is relevant to Cluster-wide preflight hardware inventory but does not directly resolve the current NCCL transport environment and benchmark reproducibility issue: Every intended node is accounted for and deviations are dispositioned before workload benchmarking begins. Observed scenario: Engineers compare two runs without recording whether NCCL selected different NICs or environment overrides.
Question 825
During an NVIDIA AI factory acceptance test, engineers discover: A job sets multiple contradictory fabric variables and then treats the result as default system behavior. Which operational response is MOST appropriate to address the root issue? Select ONE best answer.
- Schedule supported active DCGM diagnostics for the relevant GPU class and investigate detailed failures.
- Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings.
- Capture a reproducible preflight inventory of node hardware, software, connections and expected acceptance tests.
- Capture and rationalize NCCL environment settings and selected interfaces with each repeatable benchmark.
Explanation
Correct Answer
D:This is an appropriate correction for NCCL transport environment and benchmark reproducibility: Capture and rationalize NCCL environment settings and selected interfaces with each repeatable benchmark. Observed scenario: A job sets multiple contradictory fabric variables and then treats the result as default system behavior.
Incorrect Answers
A:This alternative is relevant to DCGM active single-node diagnostic suites but does not directly resolve the current NCCL transport environment and benchmark reproducibility issue: Schedule supported active DCGM diagnostics for the relevant GPU class and investigate detailed failures. Observed scenario: A job sets multiple contradictory fabric variables and then treats the result as default system behavior.
B:This tempting but unsafe shortcut is not a sufficient remediation for NCCL transport environment and benchmark reproducibility: Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings. A job sets multiple contradictory fabric variables and then treats the result as default system behavior.
C:This alternative is relevant to Cluster-wide preflight hardware inventory but does not directly resolve the current NCCL transport environment and benchmark reproducibility issue: Capture a reproducible preflight inventory of node hardware, software, connections and expected acceptance tests. Observed scenario: A job sets multiple contradictory fabric variables and then treats the result as default system behavior.
Question 826
A production GPU cluster review identifies this condition: A job sets multiple contradictory fabric variables and then treats the result as default system behavior. Which underlying infrastructure principle BEST explains the issue? Select ONE best answer.
- DCGM diagnostic suites exercise hardware and software health more deeply than passive status queries, sometimes consuming substantial resources.
- Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings.
- Environment overrides can change transport or algorithm choice; performance claims require documented configuration.
- Local NVLink health does not establish end-to-end east-west cluster communication across NICs and switches.
Explanation
Correct Answer
C:This is the governing infrastructure principle: Environment overrides can change transport or algorithm choice; performance claims require documented configuration. Observed scenario: A job sets multiple contradictory fabric variables and then treats the result as default system behavior.
Incorrect Answers
A:That option concerns DCGM active single-node diagnostic suites. The acceptance condition is: Benchmark runs can be repeated with the same approved transport and explainable performance changes.
B:This tempting but unsafe shortcut is not a sufficient remediation for NCCL transport environment and benchmark reproducibility: Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings. A job sets multiple contradictory fabric variables and then treats the result as default system behavior. Environment overrides can change transport or algorithm choice; performance claims require documented configuration.
D:This alternative is relevant to Inter-node NCCL east-west RDMA readiness but does not directly resolve the current NCCL transport environment and benchmark reproducibility issue: Local NVLink health does not establish end-to-end east-west cluster communication across NICs and switches. Observed scenario: A job sets multiple contradictory fabric variables and then treats the result as default system behavior.
Question 827
In a professional AI infrastructure deployment, a technician observes: A job sets multiple contradictory fabric variables and then treats the result as default system behavior. Which diagnostic evidence should be obtained FIRST to substantiate the likely fault or configuration gap? Select ONE best answer.
- Inspect NCCL debug traces, selected network plugin, environment variables and host network topology.
- Inspect nccl-tests output verification flags, message sizes, GPU logs and reproducible error traces.
- Inspect node inventory, GPU and NIC UUIDs, firmware and driver versions, cabling records and test eligibility.
- Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings.
Explanation
Correct Answer
A:This is the direct operational evidence to investigate: Inspect NCCL debug traces, selected network plugin, environment variables and host network topology. Observed scenario: A job sets multiple contradictory fabric variables and then treats the result as default system behavior.
Incorrect Answers
B:This alternative is relevant to NCCL device buffers and data integrity checks but does not directly resolve the current NCCL transport environment and benchmark reproducibility issue: Inspect nccl-tests output verification flags, message sizes, GPU logs and reproducible error traces. Observed scenario: A job sets multiple contradictory fabric variables and then treats the result as default system behavior.
C:This alternative is relevant to Cluster-wide preflight hardware inventory but does not directly resolve the current NCCL transport environment and benchmark reproducibility issue: Inspect node inventory, GPU and NIC UUIDs, firmware and driver versions, cabling records and test eligibility. Observed scenario: A job sets multiple contradictory fabric variables and then treats the result as default system behavior.
D:This tempting but unsafe shortcut is not a sufficient remediation for NCCL transport environment and benchmark reproducibility: Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings. Observed scenario: A job sets multiple contradictory fabric variables and then treats the result as default system behavior. The governing mechanism is: Environment overrides can change transport or algorithm choice; performance claims require documented configuration. The proportionate action is: Capture and rationalize NCCL environment settings and selected interfaces with each repeatable benchmark.
Question 828
The cluster operations team needs to evaluate this situation: A job sets multiple contradictory fabric variables and then treats the result as default system behavior. After corrective work, which observable result BEST confirms that the requirement is met? Select ONE best answer.
- The collective returns numerically valid outputs across intended ranks at accepted latency and bandwidth.
- Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings.
- Benchmark runs can be repeated with the same approved transport and explainable performance changes.
- All intended GPUs participate in successful collectives with expected local throughput and no fabric faults.
Explanation
Correct Answer
C:This is an observable verified result, not merely a claimed configuration change: Benchmark runs can be repeated with the same approved transport and explainable performance changes. Observed scenario: A job sets multiple contradictory fabric variables and then treats the result as default system behavior.
Incorrect Answers
A:This alternative is relevant to NCCL device buffers and data integrity checks but does not directly resolve the current NCCL transport environment and benchmark reproducibility issue: The collective returns numerically valid outputs across intended ranks at accepted latency and bandwidth. Observed scenario: A job sets multiple contradictory fabric variables and then treats the result as default system behavior.
B:This tempting but unsafe shortcut is not a sufficient remediation for NCCL transport environment and benchmark reproducibility: Treat environment-driven NCCL transport differences as physical fabric faults without examining launch settings. Observed scenario: A job sets multiple contradictory fabric variables and then treats the result as default system behavior. The governing mechanism is: Environment overrides can change transport or algorithm choice; performance claims require documented configuration. The proportionate action is: Capture and rationalize NCCL environment settings and selected interfaces with each repeatable benchmark. A direct check is: Inspect NCCL debug traces, selected network plugin, environment variables and host network topology. The acceptance condition is: Benchmark runs can be repeated with the same approved transport and explainable performance changes.
D:That option concerns Intra-node NCCL all-reduce test scope. Environment overrides can change transport or algorithm choice; performance claims require documented configuration.
Question 829
At a multi-node AI infrastructure handoff, the team records: Every compute NIC reports link at full speed but simultaneous NCCL jobs bottleneck on shared spine uplinks. Which operational response is MOST appropriate to address the root issue? Select ONE best answer.
- Assert a nonblocking AI network because every endpoint NIC independently negotiates 400 Gb/s.
- Use multi-flow cluster-scale throughput tests to measure effective bisection and hotspot oversubscription.
- Capture a reproducible preflight inventory of node hardware, software, connections and expected acceptance tests.
- Run a controlled representative GPU stress with monitoring of temperatures, memory and power-limit behavior.
Explanation
Correct Answer
B:This is an appropriate correction for AI fabric bisection and oversubscription test: Use multi-flow cluster-scale throughput tests to measure effective bisection and hotspot oversubscription. Observed scenario: Every compute NIC reports link at full speed but simultaneous NCCL jobs bottleneck on shared spine uplinks.
Incorrect Answers
A:This tempting but unsafe shortcut is not a sufficient remediation for AI fabric bisection and oversubscription test: Assert a nonblocking AI network because every endpoint NIC independently negotiates 400 Gb/s.
C:This alternative is relevant to Cluster-wide preflight hardware inventory but does not directly resolve the current AI fabric bisection and oversubscription test issue: Capture a reproducible preflight inventory of node hardware, software, connections and expected acceptance tests. Observed scenario: Every compute NIC reports link at full speed but simultaneous NCCL jobs bottleneck on shared spine uplinks.
D:This alternative is relevant to GPU thermal power and memory single-node burn-in but does not directly resolve the current AI fabric bisection and oversubscription test issue: Run a controlled representative GPU stress with monitoring of temperatures, memory and power-limit behavior. Observed scenario: Every compute NIC reports link at full speed but simultaneous NCCL jobs bottleneck on shared spine uplinks.
Question 830
During an NVIDIA AI factory acceptance test, engineers discover: Every compute NIC reports link at full speed but simultaneous NCCL jobs bottleneck on shared spine uplinks. Which TWO complementary elements are needed: the correct technical action and the strongest independent diagnostic evidence? Select TWO answers.
- Run a controlled representative GPU stress with monitoring of temperatures, memory and power-limit behavior.
- Inspect per-tier utilization, congestion counters, full-rack NCCL measurements and ECMP distribution.
- Use multi-flow cluster-scale throughput tests to measure effective bisection and hotspot oversubscription.
- Inspect rank-to-device assignments, CPU binding, NUMA traffic, GPU topology and achieved HPL timing.
- Assert a nonblocking AI network because every endpoint NIC independently negotiates 400 Gb/s.
Explanation
Correct Answers
B:This is the direct operational evidence to investigate: Inspect per-tier utilization, congestion counters, full-rack NCCL measurements and ECMP distribution. Observed scenario: Every compute NIC reports link at full speed but simultaneous NCCL jobs bottleneck on shared spine uplinks.
C:This is an appropriate correction for AI fabric bisection and oversubscription test: Use multi-flow cluster-scale throughput tests to measure effective bisection and hotspot oversubscription. Observed scenario: Every compute NIC reports link at full speed but simultaneous NCCL jobs bottleneck on shared spine uplinks. The governing mechanism is: Simultaneous east-west traffic stresses shared fabric resources beyond individual host line-rate capability.
Incorrect Answers
A:This alternative is relevant to GPU thermal power and memory single-node burn-in but does not directly resolve the current AI fabric bisection and oversubscription test issue: Run a controlled representative GPU stress with monitoring of temperatures, memory and power-limit behavior. Observed scenario: Every compute NIC reports link at full speed but simultaneous NCCL jobs bottleneck on shared spine uplinks. The governing mechanism is: Simultaneous east-west traffic stresses shared fabric resources beyond individual host line-rate capability.
D:This alternative is relevant to Multi-process HPL rank placement and CPU affinity but does not directly resolve the current AI fabric bisection and oversubscription test issue: Inspect rank-to-device assignments, CPU binding, NUMA traffic, GPU topology and achieved HPL timing. Observed scenario: Every compute NIC reports link at full speed but simultaneous NCCL jobs bottleneck on shared spine uplinks.
E:This tempting but unsafe shortcut is not a sufficient remediation for AI fabric bisection and oversubscription test: Assert a nonblocking AI network because every endpoint NIC independently negotiates 400 Gb/s. Simultaneous east-west traffic stresses shared fabric resources beyond individual host line-rate capability.