easyMultiple Choice
Generative AI Leader Practice Question: Deciding between using a pre-built GenAI API…
A company is deciding between using a pre-built GenAI API (like Gemini API) and building a custom fine-tuned model. Which factor would MOST strongly favor the custom fine-tuned model?
⚠ Common exam trap
Generative AI Leader often tests the misconception that custom fine-tuned models are always better for performance or cost, when in fact they are primarily justified by specialized domain knowledge needs, not by budget, latency, or low volume.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Need for specialized domain knowledge that general models lack
A custom fine-tuned model is most justified when the task requires deep, specialized domain knowledge that general-purpose models cannot reliably provide. Fine-tuning adapts a base model's weights to a narrow corpus (e.g., proprietary medical, legal, or industrial data), improving accuracy and style adherence beyond what prompt engineering alone can achieve. The other factors—budget, latency, and request volume—are operational constraints that typically favor pre-built APIs, not custom models.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Limited budget for AI development
Why it's wrong here
A limited budget favours the pre-built API's consumption pricing, since fine-tuning demands labelled data, training compute and ongoing hosting. It is tempting because custom models appear to avoid per-call fees, but those fees are typically cheaper than the fixed cost of building and maintaining a fine-tuned model.
- ✗
Low latency requirements for real-time responses
Why it's wrong here
A pre-built API can be hosted close to users and is engineered for low-latency serving; a custom fine-tuned model adds inference overhead and hosting complexity that can worsen response times. It is tempting because fine-tuning feels like control, but latency is addressed through deployment topology, not model customisation.
- ✗
Small volume of inference requests per day
Why it's wrong here
Low request volume favours the pre-built API's pay-per-call model, since a fine-tuned model's training and hosting costs cannot be amortised across few inferences. It is tempting because small scale feels controllable, but custom fine-tuning is justified by high, sustained inference demand or specialised domain behaviour.
- ✓
Need for specialized domain knowledge that general models lack
Why this is correct
Fine-tuning injects specialised domain knowledge that general models lack, satisfying the requirement for accuracy in niche terminology and context. Pre-built APIs cannot match this without extensive prompt engineering, so domain specificity most strongly favours the custom model.
Go deeper
Related to this question
About these practice questions
Courseiva writes every Generative AI Leader question from scratch — 1,008 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Google Cloud exam blueprint
This Generative AI Leader practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Generative AI Leader exam.