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 43

Question 420

During an NVIDIA AI factory acceptance test, engineers discover: An operator creates an isolated GPU slice but overlooks associated compute-instance configuration for workload execution. Which TWO complementary elements are needed: the correct technical action and the strongest independent diagnostic evidence? Select TWO answers.

  1. Choose supported MIG GPU-instance profiles and create matching compute instances with validated resource assignments.
  2. Inspect GPU model and MIG support, available profile geometry, GPU instance and compute instance listings and CUDA visibility.
  3. Assume that toggling MIG mode alone automatically allocates a usable instance to every new container.
  4. Inspect DPU hardware generation, BFB package provenance, BMC job records, Arm boot logs and firmware versions.
  5. Select supported BlueField operation mode to match host and embedded-control ownership, then validate policy and recovery.

Explanation

Correct Answers

A:

This is an appropriate correction for MIG GPU and compute instance partition profiles: Choose supported MIG GPU-instance profiles and create matching compute instances with validated resource assignments. Observed scenario: An operator creates an isolated GPU slice but overlooks associated compute-instance configuration for workload execution. The governing mechanism is: MIG divides compatible GPUs into supported isolated resource profiles; enabling the mode is not equivalent to provisioning usable devices.

B:

This is the direct operational evidence to investigate: Inspect GPU model and MIG support, available profile geometry, GPU instance and compute instance listings and CUDA visibility. Observed scenario: An operator creates an isolated GPU slice but overlooks associated compute-instance configuration for workload execution. The governing mechanism is: MIG divides compatible GPUs into supported isolated resource profiles; enabling the mode is not equivalent to provisioning usable devices.

Incorrect Answers

C:

This tempting but unsafe shortcut is not a sufficient remediation for MIG GPU and compute instance partition profiles: Assume that toggling MIG mode alone automatically allocates a usable instance to every new container. Observed scenario: An operator creates an isolated GPU slice but overlooks associated compute-instance configuration for workload execution. The governing mechanism is: MIG divides compatible GPUs into supported isolated resource profiles; enabling the mode is not equivalent to provisioning usable devices. The proportionate action is: Choose supported MIG GPU-instance profiles and create matching compute instances with validated resource assignments. A direct check is: Inspect GPU model and MIG support, available profile geometry, GPU instance and compute instance listings and CUDA visibility. The acceptance condition is: Each authorized tenant sees only the intended MIG devices and runs a test workload within its assigned profile.

D:

This alternative is relevant to BlueField boot image BFB provisioning and BMC but does not directly resolve the current MIG GPU and compute instance partition profiles issue: Inspect DPU hardware generation, BFB package provenance, BMC job records, Arm boot logs and firmware versions. Observed scenario: An operator creates an isolated GPU slice but overlooks associated compute-instance configuration for workload execution. The governing mechanism is: MIG divides compatible GPUs into supported isolated resource profiles; enabling the mode is not equivalent to provisioning usable devices.

E:

This alternative is relevant to BlueField DPU embedded versus NIC ownership but does not directly resolve the current MIG GPU and compute instance partition profiles issue: Select supported BlueField operation mode to match host and embedded-control ownership, then validate policy and recovery. Observed scenario: An operator creates an isolated GPU slice but overlooks associated compute-instance configuration for workload execution. The governing mechanism is: MIG divides compatible GPUs into supported isolated resource profiles; enabling the mode is not equivalent to provisioning usable devices.

Question 421

A production GPU cluster review identifies this condition: A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs. Which operational response is MOST appropriate to address the root issue? Select ONE best answer.

  1. Coordinate MIG reconfiguration with workload draining, persistent desired-state recreation and scheduler resource discovery.
  2. Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation.
  3. Select supported BlueField operation mode to match host and embedded-control ownership, then validate policy and recovery.
  4. Choose supported MIG GPU-instance profiles and create matching compute instances with validated resource assignments.

Explanation

Correct Answer

A:

This is an appropriate correction for MIG lifecycle and workload scheduling persistence: Coordinate MIG reconfiguration with workload draining, persistent desired-state recreation and scheduler resource discovery. Observed scenario: A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs.

Incorrect Answers

B:

This tempting but unsafe shortcut is not a sufficient remediation for MIG lifecycle and workload scheduling persistence: Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation.

C:

This alternative is relevant to BlueField DPU embedded versus NIC ownership but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: Select supported BlueField operation mode to match host and embedded-control ownership, then validate policy and recovery. Observed scenario: A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs.

D:

This alternative is relevant to MIG GPU and compute instance partition profiles but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: Choose supported MIG GPU-instance profiles and create matching compute instances with validated resource assignments. Observed scenario: A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs.

Question 422

In a professional AI infrastructure deployment, a technician observes: A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs. Which underlying infrastructure principle BEST explains the issue? Select ONE best answer.

  1. BlueField-based services depend on a compatible host and embedded software stack; NIC link state alone is inadequate.
  2. BlueField embedded software provisioning is a controlled device lifecycle separate from the host's ordinary OS image.
  3. MIG instance topology and scheduler-visible resources must agree; some MIG instance state requires explicit recreation after reboot.
  4. Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation.

Explanation

Correct Answer

C:

This is the governing infrastructure principle: MIG instance topology and scheduler-visible resources must agree; some MIG instance state requires explicit recreation after reboot. Observed scenario: A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs.

Incorrect Answers

A:

This alternative is relevant to DOCA and BlueField host driver interoperability but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: BlueField-based services depend on a compatible host and embedded software stack; NIC link state alone is inadequate. Observed scenario: A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs.

B:

That option concerns BlueField boot image BFB provisioning and BMC. The acceptance condition is: After maintenance the expected GPU slices are recreated and queued workloads receive only valid assigned devices.

D:

This tempting but unsafe shortcut is not a sufficient remediation for MIG lifecycle and workload scheduling persistence: Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation. MIG instance topology and scheduler-visible resources must agree; some MIG instance state requires explicit recreation after reboot.

Question 423

The cluster operations team needs to evaluate this situation: A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs. Which diagnostic evidence should be obtained FIRST to substantiate the likely fault or configuration gap? Select ONE best answer.

  1. Inspect running process ownership, postboot instance layout, device plugin or GRES inventory and schedule placement receipts.
  2. Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation.
  3. Review installed DOCA packages, release compatibility, firmware, host drivers and service launch logs.
  4. Inspect GPU model and MIG support, available profile geometry, GPU instance and compute instance listings and CUDA visibility.

Explanation

Correct Answer

A:

This is the direct operational evidence to investigate: Inspect running process ownership, postboot instance layout, device plugin or GRES inventory and schedule placement receipts. Observed scenario: A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs.

Incorrect Answers

B:

This tempting but unsafe shortcut is not a sufficient remediation for MIG lifecycle and workload scheduling persistence: Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation. A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs.

C:

This alternative is relevant to DOCA and BlueField host driver interoperability but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: Review installed DOCA packages, release compatibility, firmware, host drivers and service launch logs. Observed scenario: A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs.

D:

This alternative is relevant to MIG GPU and compute instance partition profiles but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: Inspect GPU model and MIG support, available profile geometry, GPU instance and compute instance listings and CUDA visibility. Observed scenario: A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs.

Question 424

At a multi-node AI infrastructure handoff, the team records: A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs. After corrective work, which observable result BEST confirms that the requirement is met? Select ONE best answer.

  1. The intended DOCA service and packet processing function pass documented functional and failover tests.
  2. Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation.
  3. Each authorized tenant sees only the intended MIG devices and runs a test workload within its assigned profile.
  4. After maintenance the expected GPU slices are recreated and queued workloads receive only valid assigned devices.

Explanation

Correct Answer

D:

This is an observable verified result, not merely a claimed configuration change: After maintenance the expected GPU slices are recreated and queued workloads receive only valid assigned devices. Observed scenario: A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs.

Incorrect Answers

A:

This alternative is relevant to DOCA and BlueField host driver interoperability but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: The intended DOCA service and packet processing function pass documented functional and failover tests. Observed scenario: A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs.

B:

This tempting but unsafe shortcut is not a sufficient remediation for MIG lifecycle and workload scheduling persistence: Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation. A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs. MIG instance topology and scheduler-visible resources must agree; some MIG instance state requires explicit recreation after reboot.

C:

This alternative is relevant to MIG GPU and compute instance partition profiles but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: Each authorized tenant sees only the intended MIG devices and runs a test workload within its assigned profile. Observed scenario: A node reboot erases its manually configured MIG slice arrangement and the scheduler assigns nonexistent device IDs.

Question 425

During an NVIDIA AI factory acceptance test, engineers discover: A training team changes GPU partition geometry while long-running jobs still own instances. Which operational response is MOST appropriate to address the root issue? Select ONE best answer.

  1. Coordinate MIG reconfiguration with workload draining, persistent desired-state recreation and scheduler resource discovery.
  2. Use the supported BFB deployment path with verified image compatibility, approved credentials and postboot checks.
  3. Align supported DOCA runtime, host driver and BlueField firmware versions and retest relevant application capabilities.
  4. Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation.

Explanation

Correct Answer

A:

This is an appropriate correction for MIG lifecycle and workload scheduling persistence: Coordinate MIG reconfiguration with workload draining, persistent desired-state recreation and scheduler resource discovery. Observed scenario: A training team changes GPU partition geometry while long-running jobs still own instances.

Incorrect Answers

B:

This alternative is relevant to BlueField boot image BFB provisioning and BMC but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: Use the supported BFB deployment path with verified image compatibility, approved credentials and postboot checks. Observed scenario: A training team changes GPU partition geometry while long-running jobs still own instances.

C:

This alternative is relevant to DOCA and BlueField host driver interoperability but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: Align supported DOCA runtime, host driver and BlueField firmware versions and retest relevant application capabilities. Observed scenario: A training team changes GPU partition geometry while long-running jobs still own instances.

D:

This tempting but unsafe shortcut is not a sufficient remediation for MIG lifecycle and workload scheduling persistence: Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation. A training team changes GPU partition geometry while long-running jobs still own instances.

Question 426

A production GPU cluster review identifies this condition: A training team changes GPU partition geometry while long-running jobs still own instances. Which underlying infrastructure principle BEST explains the issue? Select ONE best answer.

  1. In embedded DPU mode the Arm environment can control network functionality; NIC mode changes that ownership model and capabilities.
  2. BlueField-based services depend on a compatible host and embedded software stack; NIC link state alone is inadequate.
  3. Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation.
  4. MIG instance topology and scheduler-visible resources must agree; some MIG instance state requires explicit recreation after reboot.

Explanation

Correct Answer

D:

This is the governing infrastructure principle: MIG instance topology and scheduler-visible resources must agree; some MIG instance state requires explicit recreation after reboot. Observed scenario: A training team changes GPU partition geometry while long-running jobs still own instances.

Incorrect Answers

A:

That option concerns BlueField DPU embedded versus NIC ownership. The acceptance condition is: After maintenance the expected GPU slices are recreated and queued workloads receive only valid assigned devices.

B:

This alternative is relevant to DOCA and BlueField host driver interoperability but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: BlueField-based services depend on a compatible host and embedded software stack; NIC link state alone is inadequate. Observed scenario: A training team changes GPU partition geometry while long-running jobs still own instances.

C:

This tempting but unsafe shortcut is not a sufficient remediation for MIG lifecycle and workload scheduling persistence: Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation. A training team changes GPU partition geometry while long-running jobs still own instances. MIG instance topology and scheduler-visible resources must agree; some MIG instance state requires explicit recreation after reboot.

Question 427

In a professional AI infrastructure deployment, a technician observes: A training team changes GPU partition geometry while long-running jobs still own instances. Which diagnostic evidence should be obtained FIRST to substantiate the likely fault or configuration gap? Select ONE best answer.

  1. Inspect running process ownership, postboot instance layout, device plugin or GRES inventory and schedule placement receipts.
  2. Inspect mode configuration, embedded OS status, host-visible functions, network policy and mode-transition logs.
  3. Review installed DOCA packages, release compatibility, firmware, host drivers and service launch logs.
  4. Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation.

Explanation

Correct Answer

A:

This is the direct operational evidence to investigate: Inspect running process ownership, postboot instance layout, device plugin or GRES inventory and schedule placement receipts. Observed scenario: A training team changes GPU partition geometry while long-running jobs still own instances.

Incorrect Answers

B:

This alternative is relevant to BlueField DPU embedded versus NIC ownership but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: Inspect mode configuration, embedded OS status, host-visible functions, network policy and mode-transition logs. Observed scenario: A training team changes GPU partition geometry while long-running jobs still own instances.

C:

This alternative is relevant to DOCA and BlueField host driver interoperability but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: Review installed DOCA packages, release compatibility, firmware, host drivers and service launch logs. Observed scenario: A training team changes GPU partition geometry while long-running jobs still own instances.

D:

This tempting but unsafe shortcut is not a sufficient remediation for MIG lifecycle and workload scheduling persistence: Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation. Observed scenario: A training team changes GPU partition geometry while long-running jobs still own instances. The governing mechanism is: MIG instance topology and scheduler-visible resources must agree; some MIG instance state requires explicit recreation after reboot. The proportionate action is: Coordinate MIG reconfiguration with workload draining, persistent desired-state recreation and scheduler resource discovery.

Question 428

The cluster operations team needs to evaluate this situation: A training team changes GPU partition geometry while long-running jobs still own instances. After corrective work, which observable result BEST confirms that the requirement is met? Select ONE best answer.

  1. After maintenance the expected GPU slices are recreated and queued workloads receive only valid assigned devices.
  2. The intended DOCA service and packet processing function pass documented functional and failover tests.
  3. Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation.
  4. Host and DPU traffic follows the intended control model after restart, with reachable protected management access.

Explanation

Correct Answer

A:

This is an observable verified result, not merely a claimed configuration change: After maintenance the expected GPU slices are recreated and queued workloads receive only valid assigned devices. Observed scenario: A training team changes GPU partition geometry while long-running jobs still own instances.

Incorrect Answers

B:

This alternative is relevant to DOCA and BlueField host driver interoperability but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: The intended DOCA service and packet processing function pass documented functional and failover tests. Observed scenario: A training team changes GPU partition geometry while long-running jobs still own instances.

C:

This tempting but unsafe shortcut is not a sufficient remediation for MIG lifecycle and workload scheduling persistence: Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation. Observed scenario: A training team changes GPU partition geometry while long-running jobs still own instances. The governing mechanism is: MIG instance topology and scheduler-visible resources must agree; some MIG instance state requires explicit recreation after reboot. The proportionate action is: Coordinate MIG reconfiguration with workload draining, persistent desired-state recreation and scheduler resource discovery. A direct check is: Inspect running process ownership, postboot instance layout, device plugin or GRES inventory and schedule placement receipts. The acceptance condition is: After maintenance the expected GPU slices are recreated and queued workloads receive only valid assigned devices.

D:

This alternative is relevant to BlueField DPU embedded versus NIC ownership but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: Host and DPU traffic follows the intended control model after restart, with reachable protected management access. Observed scenario: A training team changes GPU partition geometry while long-running jobs still own instances.

Question 429

At a multi-node AI infrastructure handoff, the team records: A cluster's scheduler advertises full physical GPUs while the nodes expose only MIG partition devices. Which operational response is MOST appropriate to address the root issue? Select ONE best answer.

  1. Choose supported MIG GPU-instance profiles and create matching compute instances with validated resource assignments.
  2. Coordinate MIG reconfiguration with workload draining, persistent desired-state recreation and scheduler resource discovery.
  3. Align supported DOCA runtime, host driver and BlueField firmware versions and retest relevant application capabilities.
  4. Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation.

Explanation

Correct Answer

B:

This is an appropriate correction for MIG lifecycle and workload scheduling persistence: Coordinate MIG reconfiguration with workload draining, persistent desired-state recreation and scheduler resource discovery. Observed scenario: A cluster's scheduler advertises full physical GPUs while the nodes expose only MIG partition devices.

Incorrect Answers

A:

This alternative is relevant to MIG GPU and compute instance partition profiles but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: Choose supported MIG GPU-instance profiles and create matching compute instances with validated resource assignments. Observed scenario: A cluster's scheduler advertises full physical GPUs while the nodes expose only MIG partition devices.

C:

This alternative is relevant to DOCA and BlueField host driver interoperability but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: Align supported DOCA runtime, host driver and BlueField firmware versions and retest relevant application capabilities. Observed scenario: A cluster's scheduler advertises full physical GPUs while the nodes expose only MIG partition devices.

D:

This tempting but unsafe shortcut is not a sufficient remediation for MIG lifecycle and workload scheduling persistence: Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation. A cluster's scheduler advertises full physical GPUs while the nodes expose only MIG partition devices.

Question 430

During an NVIDIA AI factory acceptance test, engineers discover: A cluster's scheduler advertises full physical GPUs while the nodes expose only MIG partition devices. Which TWO complementary elements are needed: the correct technical action and the strongest independent diagnostic evidence? Select TWO answers.

  1. Choose supported MIG GPU-instance profiles and create matching compute instances with validated resource assignments.
  2. Coordinate MIG reconfiguration with workload draining, persistent desired-state recreation and scheduler resource discovery.
  3. Inspect running process ownership, postboot instance layout, device plugin or GRES inventory and schedule placement receipts.
  4. Inspect DPU hardware generation, BFB package provenance, BMC job records, Arm boot logs and firmware versions.
  5. Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation.

Explanation

Correct Answers

B:

This is an appropriate correction for MIG lifecycle and workload scheduling persistence: Coordinate MIG reconfiguration with workload draining, persistent desired-state recreation and scheduler resource discovery. Observed scenario: A cluster's scheduler advertises full physical GPUs while the nodes expose only MIG partition devices. The governing mechanism is: MIG instance topology and scheduler-visible resources must agree; some MIG instance state requires explicit recreation after reboot.

C:

This is the direct operational evidence to investigate: Inspect running process ownership, postboot instance layout, device plugin or GRES inventory and schedule placement receipts. Observed scenario: A cluster's scheduler advertises full physical GPUs while the nodes expose only MIG partition devices.

Incorrect Answers

A:

This alternative is relevant to MIG GPU and compute instance partition profiles but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: Choose supported MIG GPU-instance profiles and create matching compute instances with validated resource assignments. Observed scenario: A cluster's scheduler advertises full physical GPUs while the nodes expose only MIG partition devices. The governing mechanism is: MIG instance topology and scheduler-visible resources must agree; some MIG instance state requires explicit recreation after reboot.

D:

This alternative is relevant to BlueField boot image BFB provisioning and BMC but does not directly resolve the current MIG lifecycle and workload scheduling persistence issue: Inspect DPU hardware generation, BFB package provenance, BMC job records, Arm boot logs and firmware versions. Observed scenario: A cluster's scheduler advertises full physical GPUs while the nodes expose only MIG partition devices.

E:

This tempting but unsafe shortcut is not a sufficient remediation for MIG lifecycle and workload scheduling persistence: Treat MIG slice identifiers and scheduling availability as immutable across resets without checking instance recreation. A cluster's scheduler advertises full physical GPUs while the nodes expose only MIG partition devices. MIG instance topology and scheduler-visible resources must agree; some MIG instance state requires explicit recreation after reboot.

NCP-AI Infrastructure (NCP-AII) Practice Tests