NVIDIA NCA-GENM Exam Questions

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.

CNNs remain the standard architecture for image classification tasks of this kind, for the same structural reasons covered elsewhere in this set: convolutional layers exploit spatial locality and translation invariance in image data, learning hierarchical features --- edges and textures in early layers, parts and objects in deeper layers --- directly from labeled pixel data, without requiring hand-engineered features. With thousands of labeled cat/dog images, a CNN (trained from scratch or, more efficiently given the modest dataset size, fine-tuned from a pretrained backbone via transfer learning) is the practical, industry-standard choice.

Decision Trees (A) can technically be applied to hand-engineered image features, but they scale poorly to raw high-dimensional pixel input and cannot learn spatial hierarchies the way convolutional architectures do --- they're a reasonable choice for structured/tabular data, not raw image classification. K-Means Clustering (B) is unsupervised and would group images by similarity without using the provided labels at all, making it unsuitable for a labeled classification task where you already have ground-truth cat/dog annotations to learn from directly. Linear Regression (D) predicts continuous numeric outputs and is not designed for categorical classification; even logistic regression, its classification-oriented cousin, would struggle on raw pixels without the feature-learning capacity a CNN provides.

This mirrors a nearly identical question earlier in this set (10,000 cats/dogs/birds) --- expect the exam to test this CNN-for-images association repeatedly, sometimes with different distractor combinations.

Bias evaluation for facial recognition centers on measuring whether the model's accuracy --- true positive rate, false positive rate, false match rate --- is consistent across demographic subgroups (race, gender, age), rather than assuming a single aggregate accuracy figure represents performance fairly for all groups. This concern is well grounded empirically: independent benchmarking, including NIST's Face Recognition Vendor Test studies, has repeatedly documented substantial accuracy disparities across demographic groups in widely deployed facial recognition systems, with error rates for some subgroups measured many times higher than for others --- a direct consequence of training data underrepresentation and the representativeness-bias issue covered elsewhere in this domain.

Processing speed (A) is a performance/latency engineering concern, not a bias or fairness concern --- a model could process all demographic groups at identical speed while still exhibiting severe accuracy disparities between them. Facial expression recognition capability (C) addresses a different task dimension (emotion/expression classification) than the identity-recognition bias question being asked. Operating system compatibility (D) is a software-deployment/engineering concern entirely unrelated to model fairness.

Subgroup accuracy disparities in facial recognition carry serious real-world consequences --- misidentification risk in law enforcement or access-control contexts --- which is why disaggregated (per-subgroup) evaluation, not just aggregate accuracy, is considered a baseline requirement under Trustworthy AI bias auditing practice.

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.

The Hugging Face Hub is a community-driven platform hosting hundreds of thousands of pretrained models --- spanning NLP, computer vision, audio, and multimodal tasks --- along with the accompanying `transformers` library that provides a standardized API to load, fine-tune, and run these models. Its role in the ML development workflow is discovery and access: developers can find a pretrained checkpoint suited to their task, download it with a few lines of code, and fine-tune or deploy it, dramatically lowering the barrier to applying transfer learning without training models from scratch.

This is explicitly distinct from deployment infrastructure: option A describes Triton Server's role (production-scale, multi-framework serving), a different layer of the ML stack than a model repository --- Hugging Face models are commonly *exported to* and served *through* Triton in production pipelines, making them complementary rather than equivalent. Option B incorrectly ties Hugging Face specifically to NVIDIA's NeMo framework --- Hugging Face is an independent, framework-agnostic ecosystem, not built on or limited to NeMo, though NeMo can import from and export to Hugging Face formats. Option C conflates Hugging Face with the NVIDIA SDK stack (Riva, NeMo, Triton, ACE) entirely --- Hugging Face is not an NVIDIA product; it is a separate open-source and commercial company/platform in the ML ecosystem.