cert
cert-1
cert-2

Pass NVIDIA NCP-AII Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
NCP-AII Exam - Verified By Experts
NCP-AII Premium File

NCP-AII Premium File

$89.99
$98.99
  • Premium File 170 Questions & Answers. Last Update: Nov 06, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$98.99
$89.99
accept 14 downloads in the last 7 days
block-screenshots
NVIDIA NCP-AII Practice Test 24

Question 230

During an NVIDIA AI factory acceptance test, engineers discover: A compute partition launches all-to-all operations but its InfiniBand topology has insufficient inter-tier links. Which TWO complementary elements are needed: the correct technical action and the strongest independent diagnostic evidence? Select TWO answers.

  1. Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification.
  2. Compare planned leaf/spine port ratios, route distribution, switch counters and all-to-all benchmark results.
  3. Check supported CDU supply, flow, leak detection and interlock behavior, then demonstrate controlled thermal response before production.
  4. Validate fabric topology, end-to-end capacity, routing and oversubscription against representative collective communication patterns.
  5. Inspect TPM ownership and event logs, secure-boot state, signed firmware path and expected PCR measurements.

Explanation

Correct Answers

B:

This is the direct operational evidence to investigate: Compare planned leaf/spine port ratios, route distribution, switch counters and all-to-all benchmark results. Observed scenario: A compute partition launches all-to-all operations but its InfiniBand topology has insufficient inter-tier links.

D:

This is an appropriate correction for InfiniBand fat-tree and bisection planning: Validate fabric topology, end-to-end capacity, routing and oversubscription against representative collective communication patterns. Observed scenario: A compute partition launches all-to-all operations but its InfiniBand topology has insufficient inter-tier links. The governing mechanism is: InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity.

Incorrect Answers

A:

This tempting but unsafe shortcut is not a sufficient remediation for InfiniBand fat-tree and bisection planning: Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification. InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity.

C:

This alternative is relevant to Liquid cooling supply and leak interlocks but does not directly resolve the current InfiniBand fat-tree and bisection planning issue: Check supported CDU supply, flow, leak detection and interlock behavior, then demonstrate controlled thermal response before production. Observed scenario: A compute partition launches all-to-all operations but its InfiniBand topology has insufficient inter-tier links. The governing mechanism is: InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity.

E:

This alternative is relevant to TPM state and measured secure boot but does not directly resolve the current InfiniBand fat-tree and bisection planning issue: Inspect TPM ownership and event logs, secure-boot state, signed firmware path and expected PCR measurements. Observed scenario: A compute partition launches all-to-all operations but its InfiniBand topology has insufficient inter-tier links.

Question 231

A production GPU cluster review identifies this condition: A compute partition launches all-to-all operations but its InfiniBand topology has insufficient inter-tier links. Which diagnostic evidence should be obtained FIRST to substantiate the likely fault or configuration gap? Select ONE best answer.

  1. Inspect management API target paths, access scopes, sensor values, chassis actions and independent host inventory.
  2. Compare planned leaf/spine port ratios, route distribution, switch counters and all-to-all benchmark results.
  3. Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification.
  4. Inspect CDU telemetry, coolant specifications, alarm contacts, flow and pressure records and documented fail-safe test results.

Explanation

Correct Answer

B:

This is the direct operational evidence to investigate: Compare planned leaf/spine port ratios, route distribution, switch counters and all-to-all benchmark results. Observed scenario: A compute partition launches all-to-all operations but its InfiniBand topology has insufficient inter-tier links. The governing mechanism is: InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity.

Incorrect Answers

A:

This alternative is relevant to Redfish inventory and IPMI management boundaries but does not directly resolve the current InfiniBand fat-tree and bisection planning issue: Inspect management API target paths, access scopes, sensor values, chassis actions and independent host inventory. Observed scenario: A compute partition launches all-to-all operations but its InfiniBand topology has insufficient inter-tier links.

C:

This tempting but unsafe shortcut is not a sufficient remediation for InfiniBand fat-tree and bisection planning: Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification. A compute partition launches all-to-all operations but its InfiniBand topology has insufficient inter-tier links.

D:

This alternative is relevant to Liquid cooling supply and leak interlocks but does not directly resolve the current InfiniBand fat-tree and bisection planning issue: Inspect CDU telemetry, coolant specifications, alarm contacts, flow and pressure records and documented fail-safe test results. Observed scenario: A compute partition launches all-to-all operations but its InfiniBand topology has insufficient inter-tier links.

Question 232

In a professional AI infrastructure deployment, a technician observes: A compute partition launches all-to-all operations but its InfiniBand topology has insufficient inter-tier links. After corrective work, which observable result BEST confirms that the requirement is met? Select ONE best answer.

  1. Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification.
  2. The commissioned node produces a verifiable boot integrity record and disallowed boot changes are detected or blocked.
  3. Cluster-scale communication meets approved performance targets without repeated congestion at an undersized tier.
  4. Electrical inspection approves the rack and sensitive boards are installed without ESD or grounding exceptions.

Explanation

Correct Answer

C:

This is an observable verified result, not merely a claimed configuration change: Cluster-scale communication meets approved performance targets without repeated congestion at an undersized tier. Observed scenario: A compute partition launches all-to-all operations but its InfiniBand topology has insufficient inter-tier links.

Incorrect Answers

A:

This tempting but unsafe shortcut is not a sufficient remediation for InfiniBand fat-tree and bisection planning: Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification. A compute partition launches all-to-all operations but its InfiniBand topology has insufficient inter-tier links. InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity.

B:

This alternative is relevant to TPM state and measured secure boot but does not directly resolve the current InfiniBand fat-tree and bisection planning issue: The commissioned node produces a verifiable boot integrity record and disallowed boot changes are detected or blocked. Observed scenario: A compute partition launches all-to-all operations but its InfiniBand topology has insufficient inter-tier links.

D:

That option concerns Rack bonding grounding and ESD handling. InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity.

Question 233

The cluster operations team needs to evaluate this situation: A rack adds leaf switches without sizing spine ports and now experiences systematic congestion during collectives. Which operational response is MOST appropriate to address the root issue? Select ONE best answer.

  1. Restore planned airflow direction, containment and intake clearance, and validate inlet thermal conditions at loaded nodes.
  2. Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification.
  3. Validate fabric topology, end-to-end capacity, routing and oversubscription against representative collective communication patterns.
  4. Provision unique BMC addresses on protected out-of-band management, rotate initial credentials and test access separately from host networking.

Explanation

Correct Answer

C:

This is an appropriate correction for InfiniBand fat-tree and bisection planning: Validate fabric topology, end-to-end capacity, routing and oversubscription against representative collective communication patterns. Observed scenario: A rack adds leaf switches without sizing spine ports and now experiences systematic congestion during collectives.

Incorrect Answers

A:

This alternative is relevant to Cold aisle inlet air and thermal envelope but does not directly resolve the current InfiniBand fat-tree and bisection planning issue: Restore planned airflow direction, containment and intake clearance, and validate inlet thermal conditions at loaded nodes. Observed scenario: A rack adds leaf switches without sizing spine ports and now experiences systematic congestion during collectives.

B:

This tempting but unsafe shortcut is not a sufficient remediation for InfiniBand fat-tree and bisection planning: Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification. A rack adds leaf switches without sizing spine ports and now experiences systematic congestion during collectives.

D:

This alternative is relevant to BMC network bring-up and out-of-band separation but does not directly resolve the current InfiniBand fat-tree and bisection planning issue: Provision unique BMC addresses on protected out-of-band management, rotate initial credentials and test access separately from host networking. Observed scenario: A rack adds leaf switches without sizing spine ports and now experiences systematic congestion during collectives.

Question 234

At a multi-node AI infrastructure handoff, the team records: A rack adds leaf switches without sizing spine ports and now experiences systematic congestion during collectives. Which underlying infrastructure principle BEST explains the issue? Select ONE best answer.

  1. InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity.
  2. Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification.
  3. AI compute power demand varies with accelerator utilization and can exceed idle or average measurements during parallel jobs.
  4. Power redundancy depends on independent supply paths and properly sized capacity, not merely on the number of power cords.

Explanation

Correct Answer

A:

This is the governing infrastructure principle: InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity. Observed scenario: A rack adds leaf switches without sizing spine ports and now experiences systematic congestion during collectives.

Incorrect Answers

B:

This tempting but unsafe shortcut is not a sufficient remediation for InfiniBand fat-tree and bisection planning: Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification. A rack adds leaf switches without sizing spine ports and now experiences systematic congestion during collectives. InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity.

C:

That option concerns GPU node peak power budgeting. The acceptance condition is: Cluster-scale communication meets approved performance targets without repeated congestion at an undersized tier.

D:

That option concerns Dual-feed rack power and PDU mapping. The acceptance condition is: Cluster-scale communication meets approved performance targets without repeated congestion at an undersized tier.

Question 235

During an NVIDIA AI factory acceptance test, engineers discover: A rack adds leaf switches without sizing spine ports and now experiences systematic congestion during collectives. Which diagnostic evidence should be obtained FIRST to substantiate the likely fault or configuration gap? Select ONE best answer.

  1. Check controller address configuration, switch OOB paths, login records, firmware identity and host-off connectivity.
  2. Compare planned leaf/spine port ratios, route distribution, switch counters and all-to-all benchmark results.
  3. Review rack load calculations, platform dimensions, rail kits, equipment placement plan and recorded installation inspections.
  4. Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification.

Explanation

Correct Answer

B:

This is the direct operational evidence to investigate: Compare planned leaf/spine port ratios, route distribution, switch counters and all-to-all benchmark results. Observed scenario: A rack adds leaf switches without sizing spine ports and now experiences systematic congestion during collectives.

Incorrect Answers

A:

This alternative is relevant to BMC network bring-up and out-of-band separation but does not directly resolve the current InfiniBand fat-tree and bisection planning issue: Check controller address configuration, switch OOB paths, login records, firmware identity and host-off connectivity. Observed scenario: A rack adds leaf switches without sizing spine ports and now experiences systematic congestion during collectives.

C:

That option concerns DGX rack load and rail placement. InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity.

D:

This tempting but unsafe shortcut is not a sufficient remediation for InfiniBand fat-tree and bisection planning: Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification. Observed scenario: A rack adds leaf switches without sizing spine ports and now experiences systematic congestion during collectives. The governing mechanism is: InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity. The proportionate action is: Validate fabric topology, end-to-end capacity, routing and oversubscription against representative collective communication patterns.

Question 236

A production GPU cluster review identifies this condition: A rack adds leaf switches without sizing spine ports and now experiences systematic congestion during collectives. After corrective work, which observable result BEST confirms that the requirement is met? Select ONE best answer.

  1. Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification.
  2. The commissioned node produces a verifiable boot integrity record and disallowed boot changes are detected or blocked.
  3. A planned single-feed isolation leaves required servers within power limits and serving their intended workloads.
  4. Cluster-scale communication meets approved performance targets without repeated congestion at an undersized tier.

Explanation

Correct Answer

D:

This is an observable verified result, not merely a claimed configuration change: Cluster-scale communication meets approved performance targets without repeated congestion at an undersized tier. Observed scenario: A rack adds leaf switches without sizing spine ports and now experiences systematic congestion during collectives.

Incorrect Answers

A:

This tempting but unsafe shortcut is not a sufficient remediation for InfiniBand fat-tree and bisection planning: Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification. Observed scenario: A rack adds leaf switches without sizing spine ports and now experiences systematic congestion during collectives. The governing mechanism is: InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity. The proportionate action is: Validate fabric topology, end-to-end capacity, routing and oversubscription against representative collective communication patterns. A direct check is: Compare planned leaf/spine port ratios, route distribution, switch counters and all-to-all benchmark results. The acceptance condition is: Cluster-scale communication meets approved performance targets without repeated congestion at an undersized tier.

B:

This alternative is relevant to TPM state and measured secure boot but does not directly resolve the current InfiniBand fat-tree and bisection planning issue: The commissioned node produces a verifiable boot integrity record and disallowed boot changes are detected or blocked. Observed scenario: A rack adds leaf switches without sizing spine ports and now experiences systematic congestion during collectives.

C:

That option concerns Dual-feed rack power and PDU mapping. InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity.

Question 237

In a professional AI infrastructure deployment, a technician observes: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed. Which operational response is MOST appropriate to address the root issue? Select ONE best answer.

  1. Validate fabric topology, end-to-end capacity, routing and oversubscription against representative collective communication patterns.
  2. Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification.
  3. Check supported CDU supply, flow, leak detection and interlock behavior, then demonstrate controlled thermal response before production.
  4. Use approved authenticated BMC inventory endpoints, distinguish read-only calls from power actions and corroborate returned component state.

Explanation

Correct Answer

A:

This is an appropriate correction for InfiniBand fat-tree and bisection planning: Validate fabric topology, end-to-end capacity, routing and oversubscription against representative collective communication patterns. Observed scenario: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed.

Incorrect Answers

B:

This tempting but unsafe shortcut is not a sufficient remediation for InfiniBand fat-tree and bisection planning: Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification. An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed.

C:

This alternative is relevant to Liquid cooling supply and leak interlocks but does not directly resolve the current InfiniBand fat-tree and bisection planning issue: Check supported CDU supply, flow, leak detection and interlock behavior, then demonstrate controlled thermal response before production. Observed scenario: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed.

D:

This alternative is relevant to Redfish inventory and IPMI management boundaries but does not directly resolve the current InfiniBand fat-tree and bisection planning issue: Use approved authenticated BMC inventory endpoints, distinguish read-only calls from power actions and corroborate returned component state. Observed scenario: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed.

Question 238

The cluster operations team needs to evaluate this situation: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed. Which underlying infrastructure principle BEST explains the issue? Select ONE best answer.

  1. Liquid cooling integrity and appropriate flow are part of accelerator availability and hardware safety, not optional performance tuning.
  2. Heavy GPU systems require rated mechanical support and correct mounting; a rack-unit count alone does not establish safe physical deployment.
  3. Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification.
  4. InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity.

Explanation

Correct Answer

D:

This is the governing infrastructure principle: InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity. Observed scenario: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed.

Incorrect Answers

A:

That option concerns Liquid cooling supply and leak interlocks. The acceptance condition is: Cluster-scale communication meets approved performance targets without repeated congestion at an undersized tier.

B:

That option concerns DGX rack load and rail placement. The acceptance condition is: Cluster-scale communication meets approved performance targets without repeated congestion at an undersized tier.

C:

This tempting but unsafe shortcut is not a sufficient remediation for InfiniBand fat-tree and bisection planning: Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification. An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed. InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity.

Question 239

At a multi-node AI infrastructure handoff, the team records: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed. Which diagnostic evidence should be obtained FIRST to substantiate the likely fault or configuration gap? Select ONE best answer.

  1. Inspect TPM ownership and event logs, secure-boot state, signed firmware path and expected PCR measurements.
  2. Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification.
  3. Review inlet and exhaust sensor trends, aisle containment, rack occupancy, fan telemetry and thermal throttling events.
  4. Compare planned leaf/spine port ratios, route distribution, switch counters and all-to-all benchmark results.

Explanation

Correct Answer

D:

This is the direct operational evidence to investigate: Compare planned leaf/spine port ratios, route distribution, switch counters and all-to-all benchmark results. Observed scenario: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed.

Incorrect Answers

A:

This alternative is relevant to TPM state and measured secure boot but does not directly resolve the current InfiniBand fat-tree and bisection planning issue: Inspect TPM ownership and event logs, secure-boot state, signed firmware path and expected PCR measurements. Observed scenario: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed.

B:

This tempting but unsafe shortcut is not a sufficient remediation for InfiniBand fat-tree and bisection planning: Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification. Observed scenario: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed. The governing mechanism is: InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity. The proportionate action is: Validate fabric topology, end-to-end capacity, routing and oversubscription against representative collective communication patterns.

C:

This alternative is relevant to Cold aisle inlet air and thermal envelope but does not directly resolve the current InfiniBand fat-tree and bisection planning issue: Review inlet and exhaust sensor trends, aisle containment, rack occupancy, fan telemetry and thermal throttling events. Observed scenario: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed.

Question 240

During an NVIDIA AI factory acceptance test, engineers discover: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed. Which TWO complementary elements are needed: the correct technical action and the strongest independent diagnostic evidence? Select TWO answers.

  1. Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification.
  2. Compare planned leaf/spine port ratios, route distribution, switch counters and all-to-all benchmark results.
  3. Validate fabric topology, end-to-end capacity, routing and oversubscription against representative collective communication patterns.
  4. Check controller address configuration, switch OOB paths, login records, firmware identity and host-off connectivity.
  5. Use approved authenticated BMC inventory endpoints, distinguish read-only calls from power actions and corroborate returned component state.

Explanation

Correct Answers

B:

This is the direct operational evidence to investigate: Compare planned leaf/spine port ratios, route distribution, switch counters and all-to-all benchmark results. Observed scenario: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed. The governing mechanism is: InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity.

C:

This is an appropriate correction for InfiniBand fat-tree and bisection planning: Validate fabric topology, end-to-end capacity, routing and oversubscription against representative collective communication patterns. Observed scenario: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed. The governing mechanism is: InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity.

Incorrect Answers

A:

This tempting but unsafe shortcut is not a sufficient remediation for InfiniBand fat-tree and bisection planning: Declare any InfiniBand leaf-spine network nonblocking solely from a single adapter's line-rate specification. Observed scenario: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed. The governing mechanism is: InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity. The proportionate action is: Validate fabric topology, end-to-end capacity, routing and oversubscription against representative collective communication patterns. A direct check is: Compare planned leaf/spine port ratios, route distribution, switch counters and all-to-all benchmark results. The acceptance condition is: Cluster-scale communication meets approved performance targets without repeated congestion at an undersized tier.

D:

This alternative is relevant to BMC network bring-up and out-of-band separation but does not directly resolve the current InfiniBand fat-tree and bisection planning issue: Check controller address configuration, switch OOB paths, login records, firmware identity and host-off connectivity. Observed scenario: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed.

E:

This alternative is relevant to Redfish inventory and IPMI management boundaries but does not directly resolve the current InfiniBand fat-tree and bisection planning issue: Use approved authenticated BMC inventory endpoints, distinguish read-only calls from power actions and corroborate returned component state. Observed scenario: An infrastructure diagram calls the fabric nonblocking merely because each NIC reports the highest advertised port speed. The governing mechanism is: InfiniBand endpoint link speed does not establish aggregate bisection bandwidth or acceptable fabric path diversity.

NCP-AI Infrastructure (NCP-AII) Practice Tests