NVIDIA Generative AI Multimodal NCA-GENM Exam Questions

Answer : A

Representativeness bias occurs when a training dataset systematically over- or under-samples subpopulations relative to the population the deployed system will actually encounter --- for example, a facial recognition dataset skewed toward lighter-skinned faces, or a multimodal medical dataset drawn predominantly from one demographic group. Because models learn statistical patterns from their training distribution, an unrepresentative dataset produces a model whose accuracy, calibration, and fairness properties degrade for underrepresented groups, even when aggregate accuracy metrics look acceptable.

This is precisely why aggregate accuracy is an insufficient safeguard: option B's framing --- that bias doesn't matter 'as long as predictions are accurate' --- conflates overall accuracy with subgroup accuracy, and a model can post strong aggregate numbers while systematically failing specific populations. Option D is factually false; AI systems have no inherent neutrality --- they inherit and can amplify whatever patterns (including societal biases) exist in their training data and objective function. Option C is also incorrect: mitigating representativeness bias is significantly cheaper and more effective when addressed at the data-collection and curation stage --- through stratified sampling, bias audits, and diverse data sourcing --- than after deployment, when it becomes a retraining and remediation problem, and by then real-world harm may have already occurred.

Answer : D

CNNs are the standard architecture for image classification because their convolutional layers exploit the spatial locality and translation invariance inherent to image data: learned filters detect local patterns (edges, textures, shapes) that compose hierarchically into higher-level features (parts, objects) as depth increases, without requiring the manual feature engineering that traditional models would need to reach comparable accuracy on raw pixel data. Pooling layers further provide a degree of spatial invariance, and parameter sharing across the image keeps the model tractable relative to a fully connected network operating on raw pixels.

Logistic Regression (A) is a linear classifier that operates on flattened feature vectors; applied directly to raw pixels of a 3-class image problem, it cannot capture the non-linear spatial structure needed to separate cats, dogs, and birds reliably, though it could serve as a baseline or as the final classification head atop CNN-extracted features. K-Means (B) is an unsupervised clustering algorithm --- inappropriate here because the task is supervised classification with labeled classes. Linear Regression (C) predicts continuous outputs and is not designed for categorical class prediction at all.

For 10,000 labeled images, a CNN (potentially fine-tuned from a pretrained backbone via transfer learning, given the modest dataset size) is the appropriate and industry-standard choice.

Answer : D

Zero-shot learning describes a model's capacity to correctly perform a task it was never explicitly trained or fine-tuned on, relying instead on knowledge and generalization ability acquired during broader pretraining. For LLMs, this typically means the model is given only a natural-language instruction or prompt describing the task --- with no task-specific labeled examples provided in the prompt at all --- and is expected to produce a reasonable response by generalizing from its pretraining. This is directly analogous to CLIP's zero-shot image classification (covered elsewhere in this set): a model trained broadly can be applied to a new, specific task purely through how the task is described to it, without additional task-specific training.

Option A is a subtly incorrect paraphrase: zero-shot learning is not about the model 'learning from zero examples' during a training process --- it's about applying a model that was never trained for the specific task at all, at inference time. The model isn't learning in the zero-shot moment; it's generalizing from prior training. Option B misapplies 'zero' to training time rather than to task-specific examples --- an unrelated concept. Option C directly contradicts the definition; zero-shot specifically refers to performance *without* task-specific training, not performance *after* extensive training on that task.

Zero-shot is typically contrasted with few-shot learning, where a small number of task-specific examples are included in the prompt to guide the model's response without updating its weights.

Answer : C

A box plot (box-and-whisker plot) summarizes the distribution of a numeric variable --- median, interquartile range, and outliers --- as a single compact glyph, and critically, multiple box plots can be placed side by side to compare distributions across categorical groupings. This makes it well suited to the scenario described: comparing the spread and central tendency of performance scores across several models, further faceted by modality, in one readable figure. Box plots make skew, variance, and outlier prevalence immediately comparable across groups in a way a single summary statistic (like mean accuracy) cannot.

A histogram (B) shows the distribution of a single variable well but does not scale cleanly to side-by-side comparison across many model/modality combinations without becoming visually cluttered. A heatmap (A) is excellent for showing a matrix of values (e.g., mean score per model modality pair) but represents point estimates, not distributions --- it cannot convey variance or spread. A pie chart (D) is inappropriate for any continuous performance metric.

In practice, a violin plot --- which overlays a kernel density estimate on the box plot's summary statistics --- is often preferred when the underlying distribution's shape (e.g., bimodality) matters, but among the given options, the box plot is the correct choice for distributional comparison across groups.

Answer : B

Transfer learning takes a model already trained on a large, general-purpose dataset (e.g., ImageNet for vision, or a large text corpus for language models) and adapts it to a new, typically smaller and more specific target task --- either by fine-tuning some or all of the pretrained weights, or by freezing the pretrained backbone and training only new task-specific layers on top. Because the pretrained model has already learned general-purpose, reusable features (edge and texture detectors in early CNN layers, syntactic and semantic structure in language model layers), the target task requires substantially less labeled data and less compute than training a comparable model from random initialization.

Prompt engineering (C) is a related but distinct technique specific to large language and generative models: it adapts a *frozen* pretrained model's behavior through the design of the input prompt alone, without any weight updates --- a lighter-weight technique than transfer learning, applicable only where a sufficiently capable pretrained model already exists. Options A and D are not standard, well-defined ML techniques matching this description; 'state management and composition' and 'neural network integration' are generic software-engineering-sounding terms without a specific technical meaning in this context, making them straightforward distractors to eliminate.

Answer : D

Batch size has a direct, proportional relationship with VRAM consumption during both training and inference: each sample in a batch requires its own memory allocation for input tensors, intermediate activations at every layer, and output tensors, all of which must reside in GPU memory simultaneously while the batch is being processed. Decreasing the batch size means fewer samples occupy memory concurrently, directly reducing peak VRAM consumption --- this is precisely why reducing batch size is one of the first, most common remedies when a model run fails with an out-of-memory (OOM) error on a GPU with limited VRAM.

Option C states the inverse of the correct relationship and is a genuinely important misconception to correct: increasing batch size increases VRAM consumption, not decreases it --- parallelism across the batch means more simultaneous memory occupancy, not less. It's true that larger batches improve GPU compute *utilization* and *throughput* (better amortizing fixed kernel-launch overhead and better exploiting parallel hardware) up to the point VRAM allows, but that throughput benefit is a separate effect from, and does not reduce, memory consumption. Options A and B both incorrectly claim batch size is memory-neutral, when it is in fact one of the most direct, easily controlled levers for managing VRAM usage --- alongside model precision (quantization, mixed precision) and activation checkpointing, covered in the Performance Optimization domain elsewhere in this set.

Answer : A

Mixed-precision training performs the bulk of computation --- matrix multiplications and convolutions --- in a lower-precision floating-point format (typically FP16 or BF16 on NVIDIA Tensor Cores) while maintaining a master copy of weights and accumulating certain sensitive operations (like loss scaling and gradient accumulation) in FP32 to preserve numerical stability. The result is substantially faster training throughput and reduced memory footprint, since lower-precision arithmetic runs at higher effective FLOPS on hardware with dedicated Tensor Cores, without a meaningful loss of final model accuracy when combined with techniques like dynamic loss scaling to prevent gradient underflow.

Note that option A's specific mention of 'double-precision' (FP64) is not how mixed precision is practiced in modern deep learning --- production mixed-precision training combines FP16/BF16 with FP32, not FP64, since FP64 offers no throughput advantage on Tensor Core hardware and is rarely used in training pipelines. Despite that imprecision in the option's wording, A is still the only choice capturing the correct underlying concept: combining multiple numeric precision levels within one training run. Options B, C, and D all misdescribe mixed precision as a *data-type* or *modality* strategy, confusing numerical precision (a performance/optimization concept) with data modality (a multimodal-data concept) --- a distinction the exam tests directly.