Home / artificial-intelligence-machine-learning / NVIDIA-Certified Associate: Generative AI LLMs (NCA-GENL) / Cheat Sheet
NVIDIA-Certified Associate: Generative AI LLMs (NCA-GENL)

NCA-GENL Cheat Sheet

NCA-GENL Tests Text-Only LLM Judgement — Prompting vs. RAG vs. Fine-Tuning, Then Serving

An associate exam for developers joining LLM projects. Unlike NCA-GENM it stays on language models: know transformer internals, read loss and perplexity correctly, pick the cheapest customization that works, and place each NVIDIA tool in the stack.

Check Your Readiness →
Among the harder certs
Avg: Not published by NVIDIA
Pass: 750 / 1000
Most candidates understand NVIDIA-Certified Associate: Generative AI LLMs (NCA-GENL) concepts — and still fail. This exam tests how you apply knowledge under pressure.

NCA-GENL Domain Map (Jan 2025 study guide)

Fifty to sixty multiple-choice items in 60 minutes, at assist-a-senior-engineer level. Questions describe a model behaviour, metric table, training curve or deployment need and ask which concept or tool explains or fixes it. Light arithmetic appears, mainly weight-memory estimates.

  1. 01
    Core Machine Learning and AI Knowledge (30%) — attention, positional encoding, tokenization, encoder vs. decoder, RAG, prompting, sampling
  2. 02
    Software Development (24%) — TensorRT-LLM vs. Triton vs. NIM vs. NeMo, memory sizing, KV cache, parallelism, quantization
  3. 03
    Experimentation (22%) — LoRA, QLoRA, p-tuning, RLHF vs. DPO, deduplication with NeMo Curator, contamination, A/B tests
  4. 04
    Data Analysis (14%) — cross-entropy, perplexity, R-squared, precision/recall/F1, chart choice, leakage and confounders
  5. 05
    Trustworthy AI (10%) — NVIDIA's four principles, consent, PII redaction, NeMo Guardrails, disaggregated fairness checks

Wrong instinct vs correct approach

A team must customize a 13B model on a single memory-limited GPU
✕ Wrong instinct

Run full fine-tuning on all weights with a smaller batch

✓ Correct approach

All weights plus optimizer states will not fit. LoRA freezes the base and trains small low-rank adapters; QLoRA does this on a 4-bit quantized base, making single-GPU tuning practical. Prompt or p-tuning trains even fewer parameters.

A model too large for one GPU's memory must run across several GPUs
✕ Wrong instinct

Use data parallelism to spread it across the GPUs

✓ Correct approach

Data parallelism copies the whole model to every GPU, so it scales throughput, not model size. Tensor parallelism splits layers and needs fast NVLink; pipeline parallelism spreads very deep models across nodes.

A candidate model tops a public leaderboard and the team wants to ship it for an internal task
✕ Wrong instinct

Deploy it because the benchmark score is highest

✓ Correct approach

Public scores may be contaminated by test items in training data or unrelated to the task. Evaluate on a custom held-out set, then an A/B test that randomizes assignment and changes one variable at a time.

A sentiment classifier shows 96% accuracy on a dataset where one class makes up most of the labels
✕ Wrong instinct

Report the model as ready based on accuracy

✓ Correct approach

Predicting the majority class alone scores highly. Check per-class precision, recall and F1 and the confusion matrix. For fairness, disaggregate metrics by user group and use counterfactual tests, since averages hide gaps.

Know these cold

  • ▸ Self-attention cost grows roughly with the square of sequence length
  • ▸ Attention sees an unordered set; positional encoding supplies word order
  • ▸ Tokens are not words; prompt and generated output share one context window
  • ▸ BERT-style encoders classify and extract; GPT-style decoders generate; T5-style suits translation and summarization
  • ▸ Chunk with overlap; huge chunks dilute similarity and crowd the prompt
  • ▸ RLHF order — upervised fine-tuning, preference data, reward model, policy optimization; DPO skips the reward model
  • ▸ NeMo Curator filters, fuzzy-deduplicates and redacts PII; exact-match dedup alone misses near-duplicates
  • ▸ Never tune hyperparameters on the test set; it stops giving an unbiased estimate
  • ▸ NVIDIA trustworthy AI principles — rivacy, safety and security, transparency, nondiscrimination
  • ▸ Anonymized data still needs consent review for a new purpose; combined fields can re-identify

Can you answer these without checking your notes?

In this scenario: "A team must customize a 13B model on a single memory-limited GPU" — what should you do first?
All weights plus optimizer states will not fit. LoRA freezes the base and trains small low-rank adapters; QLoRA does this on a 4-bit quantized base, making single-GPU tuning practical. Prompt or p-tuning trains even fewer parameters.
In this scenario: "A model too large for one GPU's memory must run across several GPUs" — what should you do first?
Data parallelism copies the whole model to every GPU, so it scales throughput, not model size. Tensor parallelism splits layers and needs fast NVLink; pipeline parallelism spreads very deep models across nodes.
In this scenario: "A candidate model tops a public leaderboard and the team wants to ship it for an internal task" — what should you do first?
Public scores may be contaminated by test items in training data or unrelated to the task. Evaluate on a custom held-out set, then an A/B test that randomizes assignment and changes one variable at a time.

Common Exam Mistakes — What candidates get wrong

Choosing fine-tuning to keep an assistant current with weekly document changes

Retrieval-augmented generation adds fresh, citable facts at query time with no retraining. Fine-tuning changes behaviour, style or task skill. Try prompt engineering first, add RAG for knowledge, and fine-tune only when behaviour itself must change.

Sizing an LLM server from parameter count alone

Weights cost parameters times bytes: FP16 is 2 bytes, so 7B needs about 14 GB. The KV cache then grows with context length and concurrent requests, plus activations and runtime overhead, so long-context serving needs far more.

Treating TensorRT-LLM, Triton, NIM and NeMo as interchangeable

TensorRT-LLM builds optimized engines with in-flight batching, paged KV cache and quantization. Triton hosts models from many frameworks. NIM is the prebuilt microservice with an OpenAI-compatible API. NeMo trains and customizes and is not a serving layer.

Reading higher perplexity or cross-entropy loss as the better model

Perplexity is the exponential of cross-entropy, and both are lower-is-better. R-squared applies only to regression targets, never text generation. Falling training loss with rising validation loss signals overfitting, not success.

Expecting temperature to control accuracy or eliminate hallucination

Temperature only scales the sampling distribution: low gives repeatable output, high gives variety. A model can be consistently wrong at zero. Grounding with RAG and citations improves factual support; NeMo Guardrails enforce topic and jailbreak policy at runtime.

Resources to help you pass NVIDIA Generative AI LLMs Associate on your first attempt

NCA-GENL rewards choosing prompting, RAG or fine-tuning correctly. Check your LLM fundamentals now.