NVIDIA Updated NCA-GENM Exam Questions and Answers by margo

Quantization reduces the numerical precision used to represent model weights and activations — for example, converting FP32 weights to INT8 — which decreases memory bandwidth requirements and allows hardware accelerators (GPU Tensor Cores, dedicated INT8 inference engines) to execute more operations per cycle, directly speeding up both training (in its mixed-precision form) and, especially, inference. Post-training quantization and quantization-aware training are the two dominant approaches, with the latter simulating quantization effects during training to better preserve accuracy at reduced bit-widths. NVIDIA's TensorRT relies heavily on quantization (alongside layer fusion and kernel auto-tuning) to accelerate deployed inference.

The distractors describe techniques that serve entirely different purposes: data augmentation (B) increases training data diversity to improve generalization, not computational speed — it typically adds preprocessing overhead rather than reducing it. Model enlargement (C) does the opposite of speeding up computation; larger models require more FLOPS and memory, increasing latency. Dropout (D) is a regularization technique applied during training to prevent overfitting by randomly zeroing activations — it has no role in inference-time speed (and is typically disabled at inference) and does not meaningfully accelerate training compute either.

Quantization is frequently paired with pruning and kernel/operator fusion as the three core techniques for hardware-accelerated performance optimization.

CLIP (Contrastive Language-Image Pretraining) trains a vision encoder and a text encoder jointly on large-scale image-caption pairs using a contrastive objective. For each batch, the model computes cosine similarity between every image embedding and every text embedding, then optimizes so that the similarity between correctly paired image-text embeddings is maximized while similarity between all mismatched pairs in the batch is minimized (an InfoNCE-style loss). The result is a shared embedding space where semantically related images and text land close together, regardless of modality.

This is why CLIP generalizes to zero-shot classification: given a new image and a set of candidate text labels (e.g., "a photo of a dog," "a photo of a cat"), the model simply picks the label whose embedding is closest to the image embedding — no task-specific fine-tuning required. This same mechanism underlies CLIP's role as the text-image alignment backbone in generative pipelines like Stable Diffusion's guidance mechanism.

Options A and C describe mechanisms CLIP does not use — there is no frequency-domain transform or image-to-text translation step — and D describes a static lookup system, which would not generalize beyond its predefined database. Contrastive learning's dual-encoder, shared-embedding-space design is the defining architectural feature to remember.

Valid model evaluation requires measuring performance on held-out data the model has not seen during training — this is the foundational principle behind train/validation/test splits and cross-validation, and it exists specifically to estimate how the model will generalize to genuinely new data, rather than how well it memorized patterns specific to its training set. Option B correctly describes this: sampling from a portion of the dataset explicitly excluded from training and calculating accuracy on it.

Options C and D both violate this principle by evaluating on the training set itself, which produces optimistically biased performance estimates: a model — particularly an overparameterized deep learning model — can achieve very high training accuracy or very low training loss simply by memorizing training examples (overfitting) without that performance transferring to new data at all. Reporting training-set accuracy (C) or training-set loss (D) as an evaluation of "performance" conflates fit-to-training-data with generalization, the central failure mode that held-out evaluation is designed to catch. Option A describes a qualitative, subjective process — interviewing developers — that provides no quantitative, reproducible performance measurement and is not a recognized model evaluation methodology.

This principle extends further in rigorous experimentation: a validation set used repeatedly for hyperparameter tuning can itself become "leaked" through repeated selection, which is why a separate, untouched test set is typically reserved for final, one-time performance reporting.

Padding behaves in a genuinely counter-intuitive, and often confused, way between standard convolution and transposed convolution, which is exactly why this pairing is tested together. In standard convolution, adding padding to the input before the kernel slides across it effectively increases the input's spatial extent, which — for a fixed kernel size and stride — increases (or, in "same" padding, preserves) the resulting output feature map's spatial dimensions relative to the unpadded case; padding this way also allows the kernel to be centered properly over boundary/edge pixels, which would otherwise be under-sampled compared to interior pixels (option C's first half).

In transposed convolution (sometimes called "deconvolution," used for upsampling in decoder/generator architectures), padding operates on the *output* side after the input has already been expanded by inserting stride-related spacing between elements: the padding parameter specifies how many rows/columns to *remove* from the perimeter of that expanded, computed output — meaning padding in transposed convolution shrinks rather than grows the resulting output dimensions, the reverse of its effect in standard convolution. This gives option A's directional claim and option C's second half.

Option B reverses which operation padding applies to (input vs. output) for each case. Option D is incorrect — padding's purpose is spatial-dimension and boundary handling, not memory/compute reduction (padding, if anything, typically adds slightly more computation). Option E states an artificial, non-standard usage rule that doesn't reflect how padding is actually applied in practice.