NVIDIA Updated NCA-GENM Exam Questions and Answers by frances

CLIP's core contribution to text-to-image pipelines is a shared, aligned embedding space in which semantically related text and images map to nearby vectors. In generative pipelines such as Stable Diffusion, CLIP's text encoder converts a prompt into an embedding that conditions the diffusion model's denoising process (often via cross-attention layers), steering the iterative noise-removal toward images whose CLIP embedding would be close to the prompt's embedding. In DALL-E 2's unCLIP approach, a "prior" model additionally maps text embeddings to plausible image embeddings within this same CLIP space before a decoder renders the final image.

Option B is subtly wrong: CLIP's text encoder produces a text embedding, not an "image embedding" — the point is that both modalities land in the *same* space, not that text is literally converted into an image representation. Option A confuses CLIP with an image-captioning model (a different task using an image encoder plus a text decoder, e.g., BLIP), and option D misattributes a data-augmentation role CLIP does not perform; CLIP is a representation/alignment model, not an augmentation tool.

Because CLIP was trained contrastively on hundreds of millions of image-text pairs, its embedding space also carries useful semantic structure (compositionality, style, attributes) that generative models exploit for prompt fidelity.

Data cleansing (or data cleaning) operates on data you already have: it identifies and resolves quality issues within an existing dataset — handling missing values (A), removing duplicate records (D), correcting formatting or type inconsistencies (B), fixing structural errors, and standardizing units or encodings. Collecting additional data (C) belongs to a conceptually earlier and separate phase of the pipeline: data acquisition or data collection, which determines what data enters the pipeline in the first place, rather than what is done to improve the quality of data already collected.

This distinction matters operationally: a cleansing step is typically deterministic and reversible against the existing dataset (you can inspect, log, and audit exactly which rows were dropped or imputed), whereas collecting more data is a scoping decision that may require new labeling budgets, new consent/privacy review, or new data-source integration — a materially different workflow with different stakeholders.

That said, insufficient data volume discovered *during* cleansing (e.g., after removing corrupted records the sample size becomes too small for the target class) can trigger a decision to go back and collect more — but that action itself is not classified as a cleansing step; it is the trigger for restarting an earlier pipeline stage.

The standard ML project lifecycle proceeds: data collection first, since you need raw data before anything else can happen; data preprocessing next, to clean, transform, and prepare that raw data (handling missing values, normalization, encoding, splitting into train/validation/test sets) into a form a model can consume; model training next, where the algorithm learns patterns from the preprocessed training data; and model evaluation last, where the trained model's performance is measured on held-out data it did not see during training. Each stage depends on the output of the one before it — you cannot preprocess data you haven't collected, train on data that hasn't been cleaned and split, or evaluate a model that hasn't been trained — which is what makes B the only internally consistent ordering among the four options.

Options A, C, and D each place a downstream step before its prerequisite: A attempts preprocessing before collection (nothing to preprocess yet); C and D both place evaluation before training and, in D's case, before data even exists — evaluation requires a trained model to assess, so it cannot logically precede training or the data-collection/preprocessing steps that training itself depends on.

In practice this pipeline is iterative rather than strictly linear — evaluation results often send you back to preprocessing (feature engineering) or even data collection (targeted collection to address weak subgroups) — but the canonical forward sequence for a first pass remains collection → preprocessing → training → evaluation.

In a denoising diffusion probabilistic model (DDPM), the U-Net serves as the noise-prediction network at the core of the iterative generation process: at each reverse-diffusion timestep, the U-Net takes the current noisy image (and typically a timestep embedding, plus conditioning information like a CLIP text embedding in text-to-image models) as input and predicts the noise component present at that step. Subtracting this predicted noise incrementally, over many timesteps starting from pure Gaussian noise, progressively denoises the input into a coherent image — the mechanism by which DDPMs generate new images from pure noise. U-Net's architecture — a contracting encoder path paired with an expanding decoder path, connected by skip connections at matching resolutions — is well suited to this role because the skip connections preserve fine-grained spatial detail that would otherwise be lost through the network's downsampling bottleneck, which matters for producing sharp, high-fidelity denoised output at each step.

Options B, C, and D describe discriminative tasks — classification, detection, and segmentation — that describe *other* legitimate applications of U-Net-style architectures (originally developed for biomedical image segmentation) but do not describe its function specifically *within* the diffusion generative process. Within a DDPM pipeline specifically, U-Net's role is generative noise prediction supporting image synthesis from noise, not classification or detection of any kind.