Get NVIDIA NCA-GENM Exam Practice Questions - Real and Updated

Answer : D

Reviewer note: Marked answer (D, pie chart) is inconsistent with standard data-visualization practice for year-by-year, multi-region comparison; a line chart (B) is the technically defensible choice.

I need to flag this one directly: the marked answer (D, pie chart) does not hold up technically, and I won't present it as correct just because it's what the answer key says. A pie chart shows the proportional breakdown of a whole at a single point in time --- it has no mechanism for representing a trend across ten years, and using ten overlapping pie charts (one per year) to compare regional performance would be one of the least readable choices available, not the most appropriate.

The technically correct choice is a line chart (B): with ten years of data per region, a line chart plots each region as a separate series across a shared time axis, making year-over-year trends, growth rates, inflection points, and cross-region divergence immediately visible --- exactly the 'year-by-year' comparison the question specifies. A grouped/clustered bar chart (C) is a reasonable secondary choice if the emphasis is discrete year-to-year comparison rather than continuous trend, but it becomes visually cluttered with ten years multiple regions. A scatter plot (A) is better suited to examining the relationship between two continuous variables (e.g., sales vs. marketing spend) than to a time-series comparison across categories.

If this exact answer appears on a live exam or official material, treat D with skepticism --- this explanation reflects standard data visualization practice, not the source document's marked key.

Answer : D

BLEU (Bilingual Evaluation Understudy) is the standard automatic metric for evaluating machine translation quality. It measures n-gram precision --- the overlap of contiguous word sequences (unigrams through typically 4-grams) between the model's translated output and one or more human reference translations --- combined with a brevity penalty to discourage overly short translations that could otherwise achieve artificially high precision. BLEU scores range from 0 to 1 (or 0-100 as a percentage), with higher scores indicating closer alignment to reference translations.

The distractors represent metrics standard to other task families: F1 score (A) evaluates classification tasks by balancing precision and recall over discrete positive/negative predictions, ill-suited to open-ended text generation where there is no fixed set of 'correct' tokens. Accuracy (B) similarly assumes a discrete correct/incorrect judgment, inappropriate for translation where multiple valid phrasings can convey the same meaning. Mean Absolute Error (C) is a regression metric measuring average magnitude of numeric prediction error, irrelevant to text output evaluation entirely.

It's worth noting BLEU has known limitations --- it correlates imperfectly with human judgments of fluency and can penalize valid paraphrases --- which has motivated complementary metrics like METEOR, ROUGE (more common for summarization), and learned metrics like BERTScore, though BLEU remains the benchmark most commonly referenced for translation specifically.

Answer : B

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.

Answer : B

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.

Answer : A, C

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.