NVIDIA Updated NCA-GENM Exam Questions and Answers by frances

Word Error Rate is the standard evaluation metric for ASR systems. It measures the edit distance between the model's transcription and a human reference transcript, computed as (Substitutions + Deletions + Insertions) / Number of reference words, expressed as a percentage. Lower WER indicates better transcription accuracy. Its character-level analogue, Character Error Rate (CER), is used for languages without clear word boundaries or for morphologically complex languages.

The distractors target common confusions: CTC (Connectionist Temporal Classification) Loss (A) is a *training* objective used to align variable-length audio input with variable-length text output in ASR models like DeepSpeech — it optimizes the model but is not itself a post-hoc evaluation metric on held-out accuracy. F1 Score (B) evaluates classification tasks with defined positive/negative classes, such as keyword spotting or wake-word detection, not full transcription. Mean Opinion Score (C) is a subjective, human-rated metric used to evaluate speech *synthesis* quality (TTS) or perceived audio naturalness — the inverse task of ASR — not transcription accuracy.

On NVIDIA's Riva and NeMo ASR pipelines, WER is the benchmark reported against datasets like LibriSpeech, and it remains the figure typically referenced in the exam's Multimodal Data and Experimentation domains when discussing speech model evaluation.

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.

A/B testing in an ML engineering context is a controlled experimental methodology where two (or more) model variants — for example, a current production model (A) and a candidate replacement (B) — are deployed simultaneously to randomly assigned, statistically comparable segments of live traffic, and their real-world performance is compared on business or task-relevant metrics (conversion rate, click-through rate, task accuracy, latency-adjusted engagement). This provides causal evidence of which model performs better under actual production conditions, which offline evaluation on static held-out datasets cannot fully capture, since production data distributions shift and downstream user behavior interacts with model outputs in ways offline metrics miss.

Option A narrows A/B testing incorrectly to UI changes alone; while A/B testing originated in and remains common for UI/UX experimentation, its application in ML engineering explicitly extends to comparing model versions, algorithms, and feature sets — not just interface elements. Option B misattributes a distinct methodology (systematic hyperparameter search, covered in the previous question) to A/B testing, which evaluates already-trained model variants rather than searching a hyperparameter space. Option C is simply incorrect — A/B testing is a cornerstone of responsible ML deployment and MLOps practice, gating rollout decisions before full production release.

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.