Free NVIDIA NCP-AII Practice Exam with Questions & Answers | Set: 3

The correct answer is mig-parted. NVIDIA MIG Partition Editor, commonly called mig-parted, is designed to automate and manage Multi-Instance GPU partitioning profiles, especially in environments where repeatable MIG layouts are required. An H100 GPU can be divided into multiple isolated GPU instances, and a seven-slice configuration is a common profile pattern for maximizing the number of smaller MIG instances on a single GPU. While nvidia-smi can enable MIG mode and manually create or destroy GPU instances, mig-parted is better suited when an administrator needs to apply defined MIG profiles consistently across HGX systems or multiple nodes. nvcc is the CUDA compiler and has no role in configuring MIG partitions. nvlink-config is not the correct utility for MIG profile configuration. In NVIDIA AI infrastructure, MIG configuration must be controlled carefully because Kubernetes device plugins, GPU Operator, Slurm GRES configuration, and tenant scheduling depend on consistent GPU instance layouts. Using mig-parted helps reduce manual errors and supports repeatable server bring-up for shared inference or multi-tenant AI environments.

Updating an NVIDIA DGX system (like the H100) is a multi-layered process because the system contains numerous programmable logic devices, including CPLDs, FPGAs, and the EROT (Electrically Resilient Root of Trust) modules. Many of these low-level hardware components cannot be updated via a simple operating system reboot. NVIDIA ' s official firmware update procedure requires a specific sequence to " commit " the new images to the hardware. First, the update utility (like nvfwupd) writes the images to the flash memory. To activate them, a " Cold Power Cycle " (removing and restoring power) is necessary to force the hardware to reload from the newly written flash blocks. Furthermore, because the BMC (Baseboard Management Controller) orchestrates the power-on sequence and monitors the EROT, it must be reset (Option D) to synchronize its state with the new component versions. Finally, an " AC Power Cycle " ensures that even the standby-power components, such as the power delivery controllers and CPLDs, undergo a full hardware reset. Skipping these steps can result in " Incomplete " or " Mismatched " firmware versions, where the OS reports one version while the hardware continues to run old, potentially buggy code in the background.

In an NVIDIA DGX BasePOD or SuperPOD environment, " Cluster Health " is a binary state: either the entire fabric and all compute resources are ready, or the cluster is considered degraded. Using the Bright Cluster Manager (BCM) shell (cmsh), administrators can aggregate telemetry from every node in the cluster. For a system to be considered " Production Ready, " every single GPU across the multi-node deployment must report a status of Health = OK. This verification ensures that the hardware is communicating correctly over the PCIe bus, the NVLink fabric is initialized, and no ECC (Error Correction Code) memory errors are present. If even a single GPU in a 32-node cluster is unhealthy, collective communication libraries like NCCL may hang or experience significant performance penalties during " All-Reduce " operations, as the entire job typically scales to the speed of the slowest/unhealthiest component. Therefore, seeing Status_Health = OK for every device is the mandatory exit criterion for the bring-up phase.

Managing a large-scale AI fabric requires centralized visibility into the physical layer. The NVIDIA Unified Fabric Manager (UFM) provides a comprehensive Dashboard for InfiniBand networks. To check transceiver firmware—which is critical for ensuring feature parity and stability across the fabric—the administrator can use the UFM Enterprise GUI. By navigating to the " Devices " section and selecting a specific switch, the " Cables " tab will aggregate telemetry for every occupied port. This view displays the manufacturer, part number, and the specific firmware version of the transceivers (LinkX) or Active Optical Cables (AOC). This consolidated view is far more efficient than manual CLI queries (Option C) for 200+ ports. Maintaining uniform firmware across transceivers ensures that optimizations like Adaptive Routing and Congestion Control perform consistently across the entire 400G or 200G fabric.

In NVIDIA networking environments, specifically those utilizing InfiniBand or high-speed Ethernet via ConnectX adapters, monitoring the physical link quality is critical for preventing packet loss and RDMA retransmissions. The mlxlink tool is part of the NVIDIA Firmware Tools (MFT) package and is the primary utility for checking the status and health of the physical link. Using the -d flag specifies the device (e.g., /dev/mst/mt4123_pciconf0), while the -c (counters) and -e (error counters/BER) flags provide a detailed readout of the link ' s performance. Bit Error Rate (BER) is a fundamental metric for signal integrity. NVIDIA systems typically distinguish between " Raw BER " (errors before Forward Error Correction) and " Effective BER " (errors remaining after FEC). A high BER often points to a failing transceiver, a dirty fiber connector, or a marginal DAC cable. While ethtool can show general statistics in Ethernet mode, mlxlink is the verified method for granular BER measurement across InfiniBand and high-speed fabrics, allowing engineers to determine if a link meets the " Error-Free " operation standards required for large-scale AI collective communications like NCCL.

For the " North-South " and " Management/Storage " Ethernet fabrics in an NVIDIA AI Factory, high availability is paramount. Unlike the InfiniBand compute fabric, which uses its own routing logic, the Ethernet side relies on standard data center protocols. To provide true hardware redundancy and double the available bandwidth (Load Balancing), NVIDIA recommends MLAG (Multi-Chassis Link Aggregation). MLAG allows two physical switches to appear as a single logical unit to the DGX nodes. The DGX can then bond its two Ethernet NICs (e.g., in an 802.3ad LACP bond) and connect one cable to each switch. This configuration provides several benefits: if one switch fails, the traffic seamlessly stays on the other link without the slow convergence times associated with Spanning Tree Protocol (Option A). Furthermore, it allows the cluster to utilize the combined bandwidth of both links for heavy storage traffic (like NFS or S3 ingestion). Using a single switch (Option C) or unmanaged hardware (Option D) creates single points of failure and lacks the traffic isolation (VLANs) required for secure AI infrastructure.

The correct actions are to download and verify the BCM ISO, and to set time zone and NTP synchronization during installation. NVIDIA DGX BasePOD deployment guidance for BCM head nodes instructs administrators to download the appropriate BCM ISO and validate the downloaded file by verifying its checksum. This ensures the installation media has not been corrupted or replaced. The same guidance also expects the head node installation to be performed from valid installation media, often using virtual media through the appliance BMC. Time zone and NTP configuration are essential in cluster control-plane environments because logs, certificates, scheduler events, monitoring data, authentication, and distributed troubleshooting depend on accurate and consistent time. Configuring compute-node PXE boot before the head node OS installation is premature because the head node and BCM services usually provide the management foundation for provisioning compute nodes. Legacy BIOS boot is not the recommended approach for modern DGX and BCM deployments; NVIDIA guidance for appliance preparation shows UEFI boot mode. A reliable BCM control plane starts with validated installation media and correct time synchronization.

The correct answer is D because adding GPUs to an existing server requires validation of physical, electrical, thermal, and platform compatibility requirements before installation. The server must have available PCIe slot allocation with the correct mechanical size, electrical lane support, and platform topology so the GPU can operate at the expected bandwidth. It must also have compatible hardware, including supported risers, power cables, firmware, BIOS settings, chassis airflow design, and driver support. Adequate rack power is mandatory because modern NVIDIA data center GPUs can significantly increase node and rack power draw under AI workloads. NVIDIA DGX SuperPOD data center guidance emphasizes that DGX rack density must fit within available power and cooling capacity, and NVIDIA-Certified Systems guidance notes that optimal PCIe server configuration depends on workload and system design. Cooling is equally critical because insufficient airflow or data center cooling can cause thermal throttling, instability, or hardware shutdowns. Storage and networking are important for workload design, but they are not the core server installation requirements for physically adding GPUs.

In an InfiniBand-based AI cluster, the " transport retry count exceeded " error is a critical indicator of physical layer instability within the fabric. When the NVIDIA Collective Communications Library (NCCL) attempts to move data between GPUs across nodes, it relies on the Reliable Connection (RC) transport of InfiniBand. If a packet is corrupted or lost due to signal integrity issues, the hardware attempts to retransmit the data. If the number of failed retransmissions exceeds the hardware-defined " Retry Count, " the connection is torn down, and NCCL reports this error. While software workarounds like increasing timeouts (Option C) might mask the symptom briefly, they do not fix the root cause: a failing physical component. The verified troubleshooting procedure involves using tools like ibqueryerrors, ibdiagnet, or mlxlink to inspect the link quality metrics, specifically looking for high Bit Error Rates (BER) and Symbol Errors. These errors are typically caused by dirty fiber connectors, poorly seated transceivers, or marginal DAC cables that cannot maintain the signal-to-noise ratio required for 200G (HDR) or 400G (NDR) speeds. Replacing the identified faulty cable or cleaning the optics is the only way to restore the " lossless " environment required for high-performance AI training.

The correct answer is to ensure stability, bandwidth, and compatibility across the cluster. In high-speed NVIDIA AI fabrics, optical transceivers and active cables are not passive details; they participate in link training, signal quality behavior, firmware-controlled operation, diagnostics, and compatibility with switches and adapters. If transceiver firmware versions are inconsistent across a fabric, links may negotiate differently, report inconsistent telemetry, show intermittent errors, or underperform under sustained workloads. This matters greatly for AI training because NCCL collectives are sensitive to latency, retransmissions, and bandwidth variation. While inventory reporting is useful, it is not the main reason to align firmware. Heterogeneous transceiver firmware is not desirable simply for discovery, and it can make troubleshooting harder. GPU memory consumption is unrelated to switch transceiver firmware. During physical-layer validation, engineers should confirm supported transceiver models, firmware versions, link speed, error counters, BER health, and port stability before approving the fabric for production. Firmware alignment helps create a predictable and supportable baseline across the entire AI cluster.