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)

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.
Reference: NVIDIA Blog - What Is Edge AI and How Does It Work?; NVIDIA Edge Computing Solutions.

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.
Reference: NVIDIA GPUDirect Storage Overview Guide; NVIDIA Developer Blog - A Direct Path Between Storage and GPU Memory.

NVIDIA defines an AI factory as "a specialized computing infrastructure designed to create value from data by managing the entire AI life cycle, from data ingestion to training, fine-tuning, and high-volume AI inference." NVIDIA also says the NVIDIA Enterprise AI Factory is a validated design that provides full-stack guidance for "building and deploying an on-premises AI factory" and that it "simplifies deployment, mitigates risk, and accelerates the path to production AI." This confirms that NVIDIA AI Factories are not just storage expansions, backup systems, or manual test environments. They are designed to support the full AI lifecycle, including data ingestion/preparation, training or fine-tuning, deployment, and production inference.
Reference: NVIDIA AI Factory Glossary; NVIDIA Enterprise AI Factory solution page.

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)