NVIDIA NCP-AAI, MS AI-103, GenAI Leader: practice drill
10 realistic exam questions, graded as you go, with the exact rule or statute citation for every answer. Start free, no sign-up.
Timed mock exam
11 questions in 13 minutes, drawn from every topic. No answers shown until the end, then a full score breakdown, your weakest topics and a review of what you missed.
Prices are in US dollars, plus tax where it applies. Stripe, our payment processor, calculates tax at checkout.
All sales are final. If something is really wrong, such as a duplicate charge or a purchase that does not unlock what you bought, write to support@careerexampro.com and we will put it right.
One-time payment. Nothing renews.
You have an exam ticket for this practice test. Start the timed mock exam to use it.
Exam Snapshot & Official Blueprint
Official Exam Fee
$200 (NVIDIA / Certiverse proctored)
Format & Time Limit
60–70 MCQs · 120 minutes
Passing Standard
Scaled professional passing score
Typical Prep Incumbents
Brand-new 2026 NVIDIA Professional track — almost no third-party practice banks
Multi-Agent Patterns: Use Router/Supervisor for dynamic specialization, Graph/State Machine (LangGraph) for deterministic cycles/human checkpoints, and Evaluator-Optimizer loops for strict quality gates.
Hybrid RAG Pipeline: Combine sparse lexical retrieval (BM25) + dense vector similarity + cross-encoder reranking to fix exact-identifier lookup failures common in dense-only RAG.
Production Guardrails: Enforce strict JSON schema validation on tool arguments, max-iteration/token circuit breakers to stop infinite agent loops, and NeMo Guardrails for topical/safety boundaries.
Frequently Asked Questions
How does NVIDIA NCP-AAI differ from NCA-GENL?
NCA-GENL ($125) tests foundational LLM literacy, whereas NCP-AAI ($200) is a senior engineering exam focused on multi-agent orchestration, memory, tool calling, NIM/NeMo deployment, and trajectory evaluation.
Exact question counts, passing scores, and allowed reference materials vary by testing window and state/agency. Always confirm current rules with the official testing provider.
Sample questions
A financial research agent currently uses a single-model ReAct loop on a large frontier LLM, causing high latency and cost because it re-reasons over the entire growing conversation history after every simple API lookup. How does migrating to a Plan-and-Execute architecture address this bottleneck?
A planner creates a multi-step plan upfront, smaller workers execute steps, and replanning triggers only on exceptions.
It removes all tool-calling interfaces and pre-generates every analytical answer into a static cache before queries arrive.
It forces the frontier model to emit all intermediate observations inside hidden reasoning tokens without calling APIs.
It replaces structured reasoning with unguided zero-shot completion so every financial calculation completes in a single forward pass with fixed latency.
Show the answer
A. A planner creates a multi-step plan upfront, smaller workers execute steps, and replanning triggers only on exceptions.
Plan-and-Execute decouples high-level planning from step execution: a capable planner creates a structured step list upfront, lightweight/cheaper models execute independent steps (often concurrently), and the planner is re-invoked only when results require replanning. This sharply reduces redundant frontier-model calls and latency compared to step-by-step ReAct loops.
A multi-session customer operations agent needs to remember three distinct categories of state: (1) messages within the active troubleshooting thread, (2) confirmed account preferences and product entitlements, and (3) prior resolution trajectories that worked for similar outage tickets. How should these map to agent memory layers?
Store active messages in semantic memory, account preferences in GPU KV-cache memory, and prior trajectories solely in the model's fine-tuned weights.
Active messages in short-term working memory, account facts in semantic memory, and past trajectories in episodic memory.
Concatenate all three categories inside one static system prompt shared globally across every tenant session.
Store active messages in episodic memory, product entitlements in short-term scratchpad memory, and past trajectories in volatile browser cookies.
Show the answer
B. Active messages in short-term working memory, account facts in semantic memory, and past trajectories in episodic memory.
Agentic architectures separate short-term working memory (current thread state/checkpoint) from long-term memory, which subdivides into semantic memory (distilled facts, user preferences, entity graphs) and episodic memory (indexed past interaction trajectories and outcomes retrieved by task similarity to guide future decisions).
A healthcare benefits assistant built with NVIDIA NeMo Guardrails must block jailbreak attempts before model inference, drop retrieved chunks containing another member's PII prior to synthesis, and mask any accidental SSN in the final response. Which combination of programmable rail stages enforces these three controls?
Dialog rails for jailbreak detection, execution rails for chunk deduplication, and input rails for masking sensitive tokens in the final model output.
Input rails for jailbreak screening, retrieval rails for filtering unauthorized chunks before generation, and output rails for final PII redaction.
Output rails for blocking malicious prompts before inference, dialog rails for vector indexing, and retrieval rails for authenticating OAuth bearer tokens.
Execution rails for prompt moderation, embedding rails for stripping PII during model pre-training, and dialog rails for network TLS termination.
Show the answer
B. Input rails for jailbreak screening, retrieval rails for filtering unauthorized chunks before generation, and output rails for final PII redaction.
NVIDIA NeMo Guardrails defines distinct interception points across the agent lifecycle: input rails inspect user prompts for jailbreaks or off-topic requests prior to LLM invocation; retrieval rails inspect and filter RAG chunks before they enter the generator context; and output rails inspect generated responses for PII leakage, policy violations, or ungrounded claims before returning text to the user.