In a resource-constrained AI cluster, a job scheduler (e.g., Slurm) efficiently allocates limited resources (GPUs, CPUs) to workloads, optimizing utilization and job execution time. It prioritizes based on policies, not just first-come-first-served, and doesn’t add resources or run all jobs simultaneously, focusing instead on resource optimization.

(Reference: NVIDIA AI Infrastructure and Operations Study Guide, Section on Job Scheduling Importance)

Reinforcement learning is the correct answer because the robot learns through interaction with an environment and improves behavior based on feedback. NVIDIA Isaac Lab documentation states: “In reinforcement learning, the robot interacts with its environment, trying different actions and receiving feedback in the form of rewards or penalties. The goal is to maximize the cumulative reward over time.” NVIDIA also states that reinforcement learning is foundational for many sim-to-real robotics approaches, enabling robots to learn complex behaviors in simulated environments before transferring those skills to the real world.

Why the other options are incorrect: Clustering is unsupervised learning used to group data, not to train an agent through actions and rewards. Supervised learning uses labeled examples, but the question describes an autonomous robot learning actions through real-world interaction and task completion, which matches reinforcement learning.

NVIDIA vGPU (Virtual GPU) software enables GPU virtualization by partitioning a physical GPU into multiple virtual instances, assignable to virtual machines or containers for accelerated workloads. Horizon is a VMware product, and “virtGPU” isn’t an NVIDIA offering, confirming vGPU as the correct solution.

(Reference: NVIDIA vGPU Documentation, Overview Section)

InfiniBand’s advantage over Ethernet lies in its lower latency, achieved through a streamlined protocol and hardware offloads, delivering microsecond-scale communication critical for AI clusters. While InfiniBand often offers high bandwidth, Ethernet can match or exceed it (e.g., 400 GbE), and Ethernet supports RDMA via RoCE, making latency the standout differentiator.

(Reference: NVIDIA Networking Documentation, Section on InfiniBand vs. Ethernet)

Training neural networks for self-driving cars requires immense computational power and high-bandwidth memory to process vast datasets (e.g., sensor data, video). NVIDIA H100 GPUs, with their cutting-edge architecture and massive throughput, are ideal for these demanding workloads. L4 GPUs are optimized for inference and efficiency, while DRIVE Orin targets in-vehicle inference, not training, making H100 the best choice.

(Reference: NVIDIA AI Infrastructure and Operations Study Guide, Section on GPU Selection for Training)

A GPU’s architecture is designed for massive parallelism, featuring thousands of lightweight cores that execute simple instructions across vast data elements simultaneously—ideal for tasks like AI training. In contrast, a CPU has fewer, complex cores optimized for sequential execution and branching logic. GPUs don’t function as PCIe controllers (a hardware role), nor are they single-core designs, making the parallel execution focus the key differentiator.

(Reference: NVIDIA GPU Architecture Whitepaper, Section on GPU Design Principles)

The Transformer model is the foundational architecture for modern large language models (LLMs). Introduced in the paper "Attention is All You Need," it uses stacked layers of self-attention mechanisms and feed-forward networks, often in encoder-decoder or decoder-only configurations, to efficiently capture long-range dependencies in text. While BERT (a specific Transformer-based model) and attention mechanisms (a component of Transformers) are related, the Transformer itself is the core concept. State space models are an alternative approach, not the primary basis for LLMs.

(Reference: NVIDIA AI Infrastructure and Operations Study Guide, Section on Large Language Models)

Training architectures are designed to maximize computational throughput and accelerate model convergence, often by leveraging distributed systems with multiple GPUs or specialized accelerators to process large datasets efficiently. This focus on performance ensures that models can be trained quickly and effectively. In contrast, inference architectures prioritize minimizing response latency to deliver real-time or near-real-time predictions, frequently employing techniques such as model optimization (e.g., pruning, quantization), batching strategies, and deployment on edge devices or optimized servers. These differing priorities mean that while there may be some overlap, the architectures are tailored to their specific goals—performance for training and low latency for inference.

(Reference: NVIDIA AI Infrastructure and Operations Study Guide, Section on Infrastructure Considerations for AI Workloads; NVIDIA Documentation on Training and Inference Optimization)

NVIDIA GPUDirect Storage is used to create a direct data path between storage and GPU memory. NVIDIA’s GPUDirect Storage Overview Guide states: “GPUDirect® Storage (GDS) enables a direct data path for direct memory access (DMA) transfers between GPU memory and storage, which avoids a bounce buffer through the CPU.” It also says this direct path can relieve system bandwidth bottlenecks and reduce CPU latency and utilization load.

NVIDIA’s GPUDirect Storage technical blog further explains that GPUDirect Storage enables “a direct data path between local or remote storage, like NVMe or NVMe over Fabric (NVMe-oF), and GPU memory.” Therefore, the correct answer is C: it enables peer-to-peer memory transfers between GPUs and NVMe storage.

Why the other options are incorrect: GPUDirect Storage is not primarily about TCP/IP transmission between GPUs and CPUs. It does simplify and bypass parts of the traditional CPU-centric storage path, but the more precise answer is direct GPU-memory-to-storage transfer. It does not increase GPU clock rates.

The correct answer is B because edge AI performs computation near where the data is created instead of sending everything to a centralized cloud or data center. NVIDIA explains that edge AI is called “edge AI” because “the AI computation is done near the user at the edge of the network, close to where the data is located, rather than centrally in a cloud computing facility or private data center.” NVIDIA’s edge computing page also states that edge devices collect data and that bringing AI to those devices lets edge computing “process this data locally,” reducing the need to transmit it to the cloud or data center and enabling real-time decision-making.

Why the other options are incorrect: Edge AI does not eliminate network management. It also does not rely solely on CPUs; NVIDIA edge AI commonly uses GPUs and accelerated computing. Edge deployments do not necessarily require higher-capacity GPUs at every site; the defining characteristic is local or near-source processing.