NVIDIA NCA-AIIO - NVIDIA-Certified Associate AI Infrastructure and Operations

The correct answer is B because model drift is an operational issue where production model performance changes as data, user behavior, or business conditions change. NVIDIA’s recommender systems best-practices documentation states that production modules should be continuously monitored: “Modules are continuously monitored so that the quality of the recommendation can be measured in real time through a range of KPIs.” It further explains that these modules “trigger full retraining should model drift occur, such as when certain KPIs fall below known established baselines.”

NVIDIA’s TAO Toolkit guidance also supports retraining as the correct response to drift: “To avoid model drift or to accommodate changing business requirements, retrain your model regularly.”

Why the other options are incorrect: Increasing hardware resources may improve throughput or latency, but it does not fix degraded model accuracy caused by drift. Permitting input distributions to change without controls is a cause of drift, not a mitigation. Assuming a model will generalize to any data is not a valid AI operations practice. The verified best practice is to monitor deployed models and retrain or update them with fresh, representative data.

DCGM is the correct answer because NVIDIA DCGM stands for Data Center GPU Manager and is built for monitoring and managing NVIDIA GPUs in data center and cluster environments. NVIDIA’s DCGM documentation states that DCGM provides “continuous GPU telemetry at very low performance overheads” and provides mechanisms to gather, group, and analyze data at the job level.

NVIDIA’s DCGM documentation also states that DCGM-Exporter “allows users to gather GPU metrics and understand workload behavior or monitor GPUs in clusters,” exposing GPU metrics for monitoring tools such as Prometheus. Therefore, DCGM is the NVIDIA tool used for data center GPU monitoring and management.

Why the other options are incorrect: TensorRT is for optimizing and running inference. Clara is NVIDIA’s healthcare and medical imaging platform. Mellanox Insight is not the primary NVIDIA data center GPU monitoring and management tool referenced for GPU operations; DCGM is.

The nvidia-smi (System Management Interface) command is the primary tool for checking GPU utilization on NVIDIA systems, including the DGX H100. It provides real-time metrics like utilization percentage, memory usage, and power draw. NVML (NVIDIA Management Library) is an API, not a command, and ctop is unrelated, solidifying nvidia-smi as the standard.

(Reference: NVIDIA DGX H100 System Documentation, Monitoring Section)

The correct answer is A because memory-transfer bottlenecks are addressed by GPU memory-system features such as high-bandwidth memory, shared memory, cache, and high-bandwidth interconnects or buses. NVIDIA’s Blackwell tuning guide describes the GPU memory system and states that the NVIDIA B200 GPU supports HBM3 and HBM3e high-bandwidth memory with capacity up to 180 GB. NVIDIA’s CUDA tuning documentation also describes shared memory as an important architectural resource available per streaming multiprocessor, which helps reduce slower memory traffic when used effectively.

Why the other options are incorrect: GPUs are not normally wired as main disk controllers. Increasing generic PCIe I/O ports does not directly solve simulation memory-transfer bottlenecks inside GPU execution. Dedicated inference ASICs are not the general NVIDIA GPU architectural feature used to address memory-transfer performance in simulation workloads.

NVIDIA identifies RAPIDS as the correct product for data preparation. NVIDIA AI Enterprise documentation describes NVIDIA RAPIDS as “GPU-accelerated data science libraries for data preparation, machine learning, and graph analytics.”

RAPIDS is therefore the correct answer because it accelerates data science and data preparation workflows on GPUs. DOCA is primarily for data center infrastructure and DPU software development, while DLSS is an AI-powered graphics rendering technology, not a data-preparation product for AI workflows.

The NVIDIA H100 GPU supports up to 7 Multi-Instance GPU (MIG) partitions, allowing it to be divided into seven isolated instances for multi-tenant or mixed workloads. This capability leverages the H100’s architecture to maximize resource flexibility and efficiency, with 7 being the documented maximum.

(Reference: NVIDIA H100 GPU Documentation, MIG Section)

InfiniBand is renowned for three key features: low latency (microsecond-scale communication), high bandwidth (100 Gb/s and beyond), and CPU offloads (via RDMA), which shift data transfer tasks to the network hardware, boosting system efficiency. High latency contradicts InfiniBand’s design, and GPU offloads are not a core networking feature, making low latency, high bandwidth, and CPU offloads the definitive trio.

(Reference: NVIDIA Networking Documentation, Section on InfiniBand Features)

Training architecture generally requires more data storage because training uses large datasets, repeated data access, and checkpointing. NVIDIA DGX SuperPOD storage architecture documentation explains that storage performance requirements vary by model and dataset, and it specifically highlights training workloads, datasets, and checkpoint files as important storage design considerations. For large model use cases, NVIDIA notes that “peak performance for reads and writes are needed for creating and reading checkpoint files” and that training stops during checkpoint operations. NVIDIA also states that storage solutions for AI factories must support “large-scale AI training, fine-tuning, inference, KV cache, and retrieval-augmented generation,” showing that storage is relevant across the lifecycle but especially demanding for training and fine-tuning.

Inference architecture typically stores the deployed model, runtime components, and sometimes cache or retrieval data. Training architecture must store training datasets, intermediate outputs, logs, and checkpoints, so it generally has the greater storage requirement.

CUDA (Compute Unified Device Architecture) is NVIDIA’s foundational parallel computing platform and programming model. It enables developers to harness GPU parallelism by extending popular languages such as C, C++, and Fortran with parallelism-specific constructs (e.g., kernel launches, thread management). CUDA also provides bindings for languages like Python (via libraries like PyCUDA), making it versatile for a wide range of developers. In contrast, CUML and CUGRAPH are higher-level libraries built on CUDA for specific machine learning and graph analytics tasks, not general-purpose programming models.

(Reference: NVIDIA CUDA Programming Guide, Introduction)