SaveMyCert
Log in
5 of 5 free questions left today·for 10 a day
GenAI Leader · Domain 3

Techniques to improve gen AI model output practice questions

Techniques to improve gen AI model output is worth 20% of the GenAI Leader exam — the 3rd-heaviest of the 4 domains. Overcoming foundation-model limitations, prompt engineering, and grounding techniques. Official (approximate) weighting ~20%. 6 fully worked examples are further down this page, answers included.

Exam weight
20%
the 3rd-heaviest of the 4 domains
Questions
93
across 3 topics
Free, no account
5/day
a free account allows 10 a day
Explanations
Every option
right and wrong

Build a practice session

5 free questions left today.

Domains

How many?

5 free questions left today.

Mode

Ready when you are

10 fresh questions drawn across 1 of 4 domains, in Learn mode.

Review what you missed

Every question you answer incorrectly, and every question you flag while practising, is saved here automatically. Finish a session and you can come back to re-drill just those.

6 sample Techniques to improve gen AI model output questions, fully explained

Questions from the GenAI Leader bank mapped to domain 3, with the answer key and the reasoning behind every option. None of them repeat the examples on the main GenAI Leader practice page.

Question 1Techniques to improve gen AI model output

A bank's customer chatbot occasionally quotes fee amounts that appear in no bank document. Its prompts are already clear and well structured, and the tone of its answers is fine. Which practice most directly reduces these fabricated figures?

Choose one.

  • a
    Fine-tune the model on last year's customer chat transcripts

    Tuning on old chat logs teaches style and patterns, and it can bake in outdated or wrong fees; it does not anchor each answer to the official figures.

  • b
    Ground responses in the current published fee schedule Correct

    Correct. Grounding supplies the authoritative fee schedule with each answer, so the model reports figures from a verifiable source instead of generating them.

  • c
    Add few-shot examples that demonstrate the preferred answer format

    Few-shot examples shape format and style, and the stem says prompting is already sound. Examples do not give the model the actual fees.

  • d
    Turn on drift monitoring for the chatbot's answer quality

    Drift monitoring can reveal that quality is slipping, but it detects problems rather than supplying the correct figures.

The concept

Grounding connects a model's responses to verifiable, authoritative data so that factual claims come from a source rather than from the model's trained memory. It is Google Cloud's main remedy for hallucinated facts.

Why that’s the answer

The problem is invented facts, and the stem rules out a prompting fix. Grounding the chatbot in the official fee schedule gives it the real numbers at answer time. Fine-tuning on old chats changes behaviour, not factual accuracy; few-shot examples change format; drift monitoring only observes.

How to reason it out
  1. Classify the failure: invented figures, which is a hallucination.
  2. Note the stated constraint: prompts and tone are already fine.
  3. Pick the practice that supplies verifiable facts at answer time: grounding.
  4. Discard practices that change style (tuning, examples) or only observe (monitoring).

Exam tip: When a model invents facts that should come from your records, ground it in those records.

Overcoming Foundation Model Limitations: Grounding, RAG, and HITL — the lesson that teaches this.

Question 2Techniques to improve gen AI model output

A director asks how fine-tuning a foundation model differs from prompt engineering when the goal is to improve its output. Which statement is accurate?

Choose one.

  • a
    Fine-tuning rewrites each prompt at request time; prompt engineering retrains the model

    This reverses the two: prompt engineering is the request-time technique and fine-tuning is the one that trains the model further.

  • b
    Both techniques update the model weights; fine-tuning simply uses more examples

    Prompt engineering never changes the weights; it only changes the instructions, context and examples sent with a request.

  • c
    Fine-tuning retrieves documents per request; prompt engineering filters unsafe outputs

    Retrieving documents at request time describes retrieval-augmented generation (RAG), not fine-tuning, and filtering unsafe outputs is the job of safety settings, not prompt engineering.

  • d
    Fine-tuning updates the model's weights; prompt engineering changes only the input Correct

    Correct. Fine-tuning trains the model further on examples, changing its parameters; prompt engineering shapes the request and leaves the model unchanged.

The concept

Fine-tuning and prompt engineering work at different levels: fine-tuning changes the model by training it further on examples, while prompt engineering changes the request and leaves the model as it is.

Why that’s the answer

The accurate contrast is weights versus input. This matters for leaders because prompt engineering is cheap and instant to change, while fine-tuning needs curated data, training effort and re-evaluation. The swapped and RAG-flavoured statements are common confusions.

How to reason it out
  1. Ask what each technique touches: the model or the request.
  2. Fine-tuning trains further, so it changes weights.
  3. Prompt engineering edits instructions, context and examples, so the model is unchanged.
  4. Reject statements that swap the two or describe retrieval (RAG).

Exam tip: Fine-tuning changes the model; prompt engineering changes the request.

Overcoming Foundation Model Limitations: Grounding, RAG, and HITL — the lesson that teaches this.

Question 3Techniques to improve gen AI model output

A program sponsor asks what a human-in-the-loop (HITL) design adds to a generative AI workflow. Which description is accurate?

Choose one.

  • a
    People write natural-language prompts instead of code to operate the model

    Writing prompts is simply how users interact with a generative model; it puts no checkpoint between the output and its use.

  • b
    People label the training data once, before the foundation model is trained

    Data labeling happens before training and is not part of the live workflow, so it cannot catch a bad output before it is used.

  • c
    People review, correct, or approve outputs at set points before they are used Correct

    Correct. HITL places human checkpoints inside the workflow so consequential outputs are checked and owned by a person before they take effect.

  • d
    People receive a notification after the model's answers have been sent

    A notification after the fact leaves no chance to stop a wrong output; the human must be in the loop before the output is acted on.

The concept

Human in the loop (HITL) places human review, correction or approval steps inside an AI workflow, especially where errors carry real consequences. Reviewer feedback also helps improve the system over time.

Why that’s the answer

The defining feature of HITL is timing and authority: a person checks the output before it is acted on and can change or reject it. Prompt writing, pre-training labeling and after-the-fact notifications all involve people, but none gives a human control before the output takes effect.

How to reason it out
  1. Recall what HITL is for: human judgment where errors matter.
  2. Look for a human checkpoint before the output is used.
  3. Reject roles that sit before training (labeling) or after release (notification).
  4. Reject ordinary usage (writing prompts), which adds no review.

Exam tip: HITL means a person can check and change the output before it is acted on.

Overcoming Foundation Model Limitations: Grounding, RAG, and HITL — the lesson that teaches this.

Question 4Techniques to improve gen AI model output

A pharmaceutical firm generates thousands of regulatory documents with a foundation model. Detailed prompt instructions and examples have helped, but outputs still slip from the firm's specialized terminology and house style across long runs. Which next step best fits?

Choose one.

  • a
    Ground the model with RAG over the firm's latest product documents

    RAG supplies current facts at answer time; the problem here is consistent terminology and style, which retrieved product documents do not fix.

  • b
    Add a longer system instruction that lists the preferred terms

    Prompting has already been tried and still falls short across long runs; a longer instruction is more of the same approach.

  • c
    Turn on drift monitoring to track terminology changes in outputs

    Monitoring would measure how often the style slips, but it does not change how the model writes.

  • d
    Fine-tune the model on approved samples of the firm's past filings Correct

    Correct. Fine-tuning on curated examples makes the vocabulary and style part of the model's default behaviour, which is the durable fix when prompting is not enough.

The concept

Fine-tuning trains a foundation model further on curated, domain-specific examples so specialized vocabulary, tone and style become the model's default behaviour. It is the step after prompt engineering when prompting cannot hold a pattern reliably.

Why that’s the answer

The firm needs durable behaviour (terminology and style), not fresh facts, and it has already tried the cheaper prompt-based fix. Google's recommended sequence is prompt engineering first, grounding for facts, and fine-tuning for persistent domain or style gaps. RAG targets the wrong problem, and monitoring only observes.

How to reason it out
  1. Classify the gap: behaviour and style, not factual knowledge.
  2. Note that prompting has already been tried and still falls short.
  3. Escalate to the technique that changes default behaviour: fine-tuning.
  4. Reject RAG (facts) and monitoring (observation only).

Exam tip: Facts that change call for RAG; a style or vocabulary that prompting cannot hold calls for fine-tuning.

Overcoming Foundation Model Limitations: Grounding, RAG, and HITL — the lesson that teaches this.

Question 5Techniques to improve gen AI model output

Six months after launch, a retailer's support assistant scores a little lower on answer quality each week. No model, prompt or code has changed, but customers now ask about new product lines and use new phrasing. Which practice is designed to surface this pattern?

Choose one.

  • a
    Drift monitoring that compares production inputs with the original baseline Correct

    Correct. Drift monitoring compares what production now looks like, in inputs and quality, with the conditions at launch, which is exactly the gradual shift described.

  • b
    Version tracking of which model and prompt are serving production traffic

    Versioning records what is deployed; the stem says nothing in the deployment changed, so version records would show no difference.

  • c
    A feature store that serves consistent feature values to the assistant

    A feature store keeps the input feature values the same across environments; it does not compare what customers ask today with what they asked at launch.

  • d
    Automatic model upgrades so the assistant runs the newest release

    Upgrades bring a newer model, but they do not measure how the questions have shifted, and the stem says the model has not changed.

The concept

Drift monitoring watches for gradual divergence between the conditions a model was built and evaluated for and what it now sees in production, such as new topics, products or phrasing.

Why that’s the answer

Quality falls slowly while the deployment stays the same and the input mix changes, which is the signature of drift. Detecting it lets the team refresh grounding data, prompts or tuning. Versioning would show nothing changed, a feature store keeps feature values consistent rather than tracking shifts in questions, and automatic upgrades change the model without measuring the inputs.

How to reason it out
  1. Note the trend: slow, steady decline rather than a sudden break.
  2. Note that the deployment itself is unchanged.
  3. Spot the cause: inputs have shifted from launch conditions.
  4. Match that to the practice that compares production with the baseline: drift monitoring.

Exam tip: Slow decline with nothing redeployed and new kinds of input means drift; drift monitoring is how you see it.

Overcoming Foundation Model Limitations: Grounding, RAG, and HITL — the lesson that teaches this.

Question 6Techniques to improve gen AI model output

A team builds an assistant on a model built mostly from English-language web text. It performs well in English but gives shallow, error-prone answers in several regional languages. Which limitation best explains the gap?

Choose one.

  • a
    The knowledge cutoff, since regional-language content was published recently

    The cutoff concerns when data was collected. Regional languages are not new, so timing does not explain weak performance across them.

  • b
    Data dependency, since those languages were thinly covered in training Correct

    Correct. A model can only be as good as its training data; languages with little coverage get weaker results.

  • c
    Prompt sensitivity, since users phrase requests differently across languages

    Different phrasing alone would not make answers shallow across whole languages; the model lacks the underlying data.

  • d
    The context window, since regional-language text needs more room per request

    The context window limits how much text the model can consider at once; it does not explain lower quality in specific languages.

The concept

Data dependency means a foundation model's knowledge, capabilities and biases all come from its training data. Thin or unbalanced coverage becomes weak or skewed behaviour in exactly those areas.

Why that’s the answer

The weakness follows the training mix: strong where data was plentiful (English) and weak where it was thin (regional languages). That is data dependency. Remedies include grounding in relevant content, fine-tuning on representative data, or choosing a model trained with broader coverage.

How to reason it out
  1. Notice that performance tracks what was in the training data.
  2. Rule out timing (cutoff), phrasing and context length, which do not follow language lines.
  3. Name the limitation: data dependency.

Exam tip: Weak results wherever training data was thin is data dependency.

Overcoming Foundation Model Limitations: Grounding, RAG, and HITL — the lesson that teaches this.

What GenAI Leader domain 3 tests, topic by topic

The official exam guide breaks Techniques to improve gen AI model output into 3 topics. The question bank follows the same split, so a weak topic shows up as a cluster of misses you can go back and read.

Published GenAI Leader practice questions per topic in Techniques to improve gen AI model output
TopicWhat it coversQuestions
Describe how to proactively overcome foundation model limitationsOfficial Gen AI Leader objective. Common limitations of foundation models (data dependency, knowledge cutoff, bias, fairness, hallucinations, edge cases); recommended practices to address them (grounding, retrieval-augmented generation, prompt engineering, fine-tuning, human in the loop); continuous monitoring and evaluation (automatic upgrades, KPIs, security patches, versioning, performance tracking, drift monitoring, Agent Platform Feature Store).31
Describe prompt engineering techniques and how they drive better resultsOfficial Gen AI Leader objective. Defining prompt engineering and its significance with LLMs; prompting techniques and use cases (zero-shot, one-shot, few-shot, role prompting, prompt chaining); advanced techniques and when to use them (chain-of-thought, ReAct).31
Identify grounding techniques and their use casesOfficial Gen AI Leader objective. Grounding in LLMs and differentiating first-party enterprise data, third-party data, and world data; how retrieval-augmented generation (RAG) affects output; Google Cloud grounding offerings (pre-built RAG with Agent Search, RAG APIs, grounding with Google Search); sampling parameters (token count, temperature, top-p, safety settings, output length).31
Total93

Revise Techniques to improve gen AI model output before you drill it

Other GenAI Leader domains

Techniques to improve gen AI model output: your questions

Techniques to improve gen AI model output is domain 3 of the GenAI Leader exam guide and carries 20% of the scored content — the 3rd-heaviest of the 4 domains. On a 55-question paper that works out to roughly 11 questions, though Google Cloud does not publish an exact per-domain count and individual exam forms vary.

Source

The domain weight and topic list on this page come from the official GenAI Leader exam guide.