NVIDIA NCP-AII Practice Test 42
Question 410
During an NVIDIA AI factory acceptance test, engineers discover: A multi-tenant cluster enables MIG mode but creates no compute instances and users see no usable CUDA devices. Which TWO complementary elements are needed: the correct technical action and the strongest independent diagnostic evidence? Select TWO answers.
- Select supported BlueField operation mode to match host and embedded-control ownership, then validate policy and recovery.
- Inspect GPU model and MIG support, available profile geometry, GPU instance and compute instance listings and CUDA visibility.
- Choose supported MIG GPU-instance profiles and create matching compute instances with validated resource assignments.
- Assume that toggling MIG mode alone automatically allocates a usable instance to every new container.
- Inspect running process ownership, postboot instance layout, device plugin or GRES inventory and schedule placement receipts.
Explanation
Correct Answers
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: A multi-tenant cluster enables MIG mode but creates no compute instances and users see no usable CUDA devices.
C: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: A multi-tenant cluster enables MIG mode but creates no compute instances and users see no usable CUDA devices. 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
A: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: A multi-tenant cluster enables MIG mode but creates no compute instances and users see no usable CUDA devices.
D: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. 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 MIG lifecycle and workload scheduling persistence but does not directly resolve the current MIG GPU and compute instance partition profiles issue: Inspect running process ownership, postboot instance layout, device plugin or GRES inventory and schedule placement receipts. Observed scenario: A multi-tenant cluster enables MIG mode but creates no compute instances and users see no usable CUDA devices.
Question 411
A production GPU cluster review identifies this condition: A multi-tenant cluster enables MIG mode but creates no compute instances and users see no usable CUDA devices. Which diagnostic evidence should be obtained FIRST to substantiate the likely fault or configuration gap? Select ONE best answer.
- Assume that toggling MIG mode alone automatically allocates a usable instance to every new container.
- Inspect running process ownership, postboot instance layout, device plugin or GRES inventory and schedule placement receipts.
- Inspect mode configuration, embedded OS status, host-visible functions, network policy and mode-transition logs.
- Inspect GPU model and MIG support, available profile geometry, GPU instance and compute instance listings and CUDA visibility.
Explanation
Correct Answer
D: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: A multi-tenant cluster enables MIG mode but creates no compute instances and users see no usable CUDA devices. 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
A: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. A multi-tenant cluster enables MIG mode but creates no compute instances and users see no usable CUDA devices.
B:This alternative is relevant to MIG lifecycle and workload scheduling persistence but does not directly resolve the current MIG GPU and compute instance partition profiles issue: Inspect running process ownership, postboot instance layout, device plugin or GRES inventory and schedule placement receipts. Observed scenario: A multi-tenant cluster enables MIG mode but creates no compute instances and users see no usable CUDA devices. The governing mechanism is: MIG divides compatible GPUs into supported isolated resource profiles; enabling the mode is not equivalent to provisioning usable devices.
C: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: Inspect mode configuration, embedded OS status, host-visible functions, network policy and mode-transition logs. Observed scenario: A multi-tenant cluster enables MIG mode but creates no compute instances and users see no usable CUDA devices.
Question 412
In a professional AI infrastructure deployment, a technician observes: A multi-tenant cluster enables MIG mode but creates no compute instances and users see no usable CUDA devices. After corrective work, which observable result BEST confirms that the requirement is met? Select ONE best answer.
- Assume that toggling MIG mode alone automatically allocates a usable instance to every new container.
- Each authorized tenant sees only the intended MIG devices and runs a test workload within its assigned profile.
- After maintenance the expected GPU slices are recreated and queued workloads receive only valid assigned devices.
- The DPU boots its expected software, responds on approved management paths and exposes intended host functions.
Explanation
Correct Answer
B:This is an observable verified result, not merely a claimed configuration change: Each authorized tenant sees only the intended MIG devices and runs a test workload within its assigned profile. Observed scenario: A multi-tenant cluster enables MIG mode but creates no compute instances and users see no usable CUDA devices.
Incorrect Answers
A: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. A multi-tenant cluster enables MIG mode but creates no compute instances and users see no usable CUDA devices. MIG divides compatible GPUs into supported isolated resource profiles; enabling the mode is not equivalent to provisioning usable devices.
C:This alternative is relevant to MIG lifecycle and workload scheduling persistence but does not directly resolve the current MIG GPU and compute instance partition profiles issue: After maintenance the expected GPU slices are recreated and queued workloads receive only valid assigned devices. Observed scenario: A multi-tenant cluster enables MIG mode but creates no compute instances and users see no usable CUDA devices.
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: The DPU boots its expected software, responds on approved management paths and exposes intended host functions. Observed scenario: A multi-tenant cluster enables MIG mode but creates no compute instances and users see no usable CUDA devices.
Question 413
The cluster operations team needs to evaluate this situation: A scheduling administrator requests a partition size unsupported by the installed GPU model. Which operational response is MOST appropriate to address the root issue? Select ONE best answer.
- Align supported DOCA runtime, host driver and BlueField firmware versions and retest relevant application capabilities.
- Choose supported MIG GPU-instance profiles and create matching compute instances with validated resource assignments.
- Assume that toggling MIG mode alone automatically allocates a usable instance to every new container.
- Coordinate MIG reconfiguration with workload draining, persistent desired-state recreation and scheduler resource discovery.
Explanation
Correct Answer
B: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: A scheduling administrator requests a partition size unsupported by the installed GPU model.
Incorrect Answers
A:This alternative is relevant to DOCA and BlueField host driver interoperability but does not directly resolve the current MIG GPU and compute instance partition profiles issue: Align supported DOCA runtime, host driver and BlueField firmware versions and retest relevant application capabilities. Observed scenario: A scheduling administrator requests a partition size unsupported by the installed GPU model.
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. A scheduling administrator requests a partition size unsupported by the installed GPU model.
D:This alternative is relevant to MIG lifecycle and workload scheduling persistence but does not directly resolve the current MIG GPU and compute instance partition profiles issue: Coordinate MIG reconfiguration with workload draining, persistent desired-state recreation and scheduler resource discovery. Observed scenario: A scheduling administrator requests a partition size unsupported by the installed GPU model.
Question 414
At a multi-node AI infrastructure handoff, the team records: A scheduling administrator requests a partition size unsupported by the installed GPU model. Which underlying infrastructure principle BEST explains the issue? Select ONE best answer.
- BlueField embedded software provisioning is a controlled device lifecycle separate from the host's ordinary OS image.
- MIG divides compatible GPUs into supported isolated resource profiles; enabling the mode is not equivalent to provisioning usable devices.
- Assume that toggling MIG mode alone automatically allocates a usable instance to every new container.
- BlueField-based services depend on a compatible host and embedded software stack; NIC link state alone is inadequate.
Explanation
Correct Answer
B:This is the governing infrastructure principle: MIG divides compatible GPUs into supported isolated resource profiles; enabling the mode is not equivalent to provisioning usable devices. Observed scenario: A scheduling administrator requests a partition size unsupported by the installed GPU model.
Incorrect Answers
A:That option concerns BlueField boot image BFB provisioning and BMC. The acceptance condition is: Each authorized tenant sees only the intended MIG devices and runs a test workload within its assigned profile.
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. A scheduling administrator requests a partition size unsupported by the installed GPU model. MIG divides compatible GPUs into supported isolated resource profiles; enabling the mode is not equivalent to provisioning usable devices.
D:This alternative is relevant to DOCA and BlueField host driver interoperability but does not directly resolve the current MIG GPU and compute instance partition profiles issue: BlueField-based services depend on a compatible host and embedded software stack; NIC link state alone is inadequate. Observed scenario: A scheduling administrator requests a partition size unsupported by the installed GPU model.
Question 415
During an NVIDIA AI factory acceptance test, engineers discover: A scheduling administrator requests a partition size unsupported by the installed GPU model. Which diagnostic evidence should be obtained FIRST to substantiate the likely fault or configuration gap? Select ONE best answer.
- Inspect GPU model and MIG support, available profile geometry, GPU instance and compute instance listings and CUDA visibility.
- Inspect DPU hardware generation, BFB package provenance, BMC job records, Arm boot logs and firmware versions.
- Assume that toggling MIG mode alone automatically allocates a usable instance to every new container.
- Review installed DOCA packages, release compatibility, firmware, host drivers and service launch logs.
Explanation
Correct Answer
A: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: A scheduling administrator requests a partition size unsupported by the installed GPU model.
Incorrect Answers
B: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: A scheduling administrator requests a partition size unsupported by the installed GPU model.
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: A scheduling administrator requests a partition size unsupported by the installed GPU model. 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.
D:This alternative is relevant to DOCA and BlueField host driver interoperability but does not directly resolve the current MIG GPU and compute instance partition profiles issue: Review installed DOCA packages, release compatibility, firmware, host drivers and service launch logs. Observed scenario: A scheduling administrator requests a partition size unsupported by the installed GPU model.
Question 416
A production GPU cluster review identifies this condition: A scheduling administrator requests a partition size unsupported by the installed GPU model. After corrective work, which observable result BEST confirms that the requirement is met? Select ONE best answer.
- The intended DOCA service and packet processing function pass documented functional and failover tests.
- Assume that toggling MIG mode alone automatically allocates a usable instance to every new container.
- Each authorized tenant sees only the intended MIG devices and runs a test workload within its assigned profile.
- Host and DPU traffic follows the intended control model after restart, with reachable protected management access.
Explanation
Correct Answer
C:This is an observable verified result, not merely a claimed configuration change: Each authorized tenant sees only the intended MIG devices and runs a test workload within its assigned profile. Observed scenario: A scheduling administrator requests a partition size unsupported by the installed GPU model.
Incorrect Answers
A:This alternative is relevant to DOCA and BlueField host driver interoperability but does not directly resolve the current MIG GPU and compute instance partition profiles issue: The intended DOCA service and packet processing function pass documented functional and failover tests. Observed scenario: A scheduling administrator requests a partition size unsupported by the installed GPU model.
B: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: A scheduling administrator requests a partition size unsupported by the installed GPU model. 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 DPU embedded versus NIC ownership but does not directly resolve the current MIG GPU and compute instance partition profiles issue: Host and DPU traffic follows the intended control model after restart, with reachable protected management access. Observed scenario: A scheduling administrator requests a partition size unsupported by the installed GPU model.
Question 417
In a professional AI infrastructure deployment, a technician observes: An operator creates an isolated GPU slice but overlooks associated compute-instance configuration for workload execution. Which operational response is MOST appropriate to address the root issue? Select ONE best answer.
- Choose supported MIG GPU-instance profiles and create matching compute instances with validated resource assignments.
- Assume that toggling MIG mode alone automatically allocates a usable instance to every new container.
- Coordinate MIG reconfiguration with workload draining, persistent desired-state recreation and scheduler resource discovery.
- Select supported BlueField operation mode to match host and embedded-control ownership, then validate policy and recovery.
Explanation
Correct Answer
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.
Incorrect Answers
B: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. An operator creates an isolated GPU slice but overlooks associated compute-instance configuration for workload execution.
C:This alternative is relevant to MIG lifecycle and workload scheduling persistence but does not directly resolve the current MIG GPU and compute instance partition profiles issue: Coordinate MIG reconfiguration with workload draining, persistent desired-state recreation and scheduler resource discovery. Observed scenario: An operator creates an isolated GPU slice but overlooks associated compute-instance configuration for workload execution.
D: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.
Question 418
The cluster operations team needs to evaluate this situation: An operator creates an isolated GPU slice but overlooks associated compute-instance configuration for workload execution. Which underlying infrastructure principle BEST explains the issue? Select ONE best answer.
- Assume that toggling MIG mode alone automatically allocates a usable instance to every new container.
- MIG divides compatible GPUs into supported isolated resource profiles; enabling the mode is not equivalent to provisioning usable devices.
- BlueField-based services depend on a compatible host and embedded software stack; NIC link state alone is inadequate.
- In embedded DPU mode the Arm environment can control network functionality; NIC mode changes that ownership model and capabilities.
Explanation
Correct Answer
B:This is the governing infrastructure principle: MIG divides compatible GPUs into supported isolated resource profiles; enabling the mode is not equivalent to provisioning usable devices. Observed scenario: An operator creates an isolated GPU slice but overlooks associated compute-instance configuration for workload execution.
Incorrect Answers
A: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. An operator creates an isolated GPU slice but overlooks associated compute-instance configuration for workload execution. MIG divides compatible GPUs into supported isolated resource profiles; enabling the mode is not equivalent to provisioning usable devices.
C:This alternative is relevant to DOCA and BlueField host driver interoperability but does not directly resolve the current MIG GPU and compute instance partition profiles issue: BlueField-based services depend on a compatible host and embedded software stack; NIC link state alone is inadequate. Observed scenario: An operator creates an isolated GPU slice but overlooks associated compute-instance configuration for workload execution.
D:That option concerns BlueField DPU embedded versus NIC ownership. The acceptance condition is: Each authorized tenant sees only the intended MIG devices and runs a test workload within its assigned profile.
Question 419
At a multi-node AI infrastructure handoff, the team records: An operator creates an isolated GPU slice but overlooks associated compute-instance configuration for workload execution. Which diagnostic evidence should be obtained FIRST to substantiate the likely fault or configuration gap? Select ONE best answer.
- Inspect GPU model and MIG support, available profile geometry, GPU instance and compute instance listings and CUDA visibility.
- Inspect running process ownership, postboot instance layout, device plugin or GRES inventory and schedule placement receipts.
- Assume that toggling MIG mode alone automatically allocates a usable instance to every new container.
- Inspect DPU hardware generation, BFB package provenance, BMC job records, Arm boot logs and firmware versions.
Explanation
Correct Answer
A: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.
Incorrect Answers
B:This alternative is relevant to MIG lifecycle and workload scheduling persistence but does not directly resolve the current MIG GPU and compute instance partition profiles issue: Inspect running process ownership, postboot instance layout, device plugin or GRES inventory and schedule placement receipts. Observed scenario: An operator creates an isolated GPU slice but overlooks associated compute-instance configuration for workload execution.
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.
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.
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.
- Choose supported MIG GPU-instance profiles and create matching compute instances with validated resource assignments.
- Inspect GPU model and MIG support, available profile geometry, GPU instance and compute instance listings and CUDA visibility.
- Assume that toggling MIG mode alone automatically allocates a usable instance to every new container.
- Inspect DPU hardware generation, BFB package provenance, BMC job records, Arm boot logs and firmware versions.
- 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.