mediumMultiple Choice
Generative AI Leader Practice Question: A startup with limited ML expertise wants to add…
A startup with limited ML expertise wants to add a GenAI feature to their SaaS application that can generate personalized email drafts for users. They need fast time-to-market and low maintenance. Which build-vs-buy decision is BEST?
⚠ Common exam trap
Generative AI Leader often tests the trade-off between customization and speed — candidates overvalue fine-tuning or custom builds for personalization, ignoring that prompt engineering on a managed API meets most personalization needs faster and cheaper.
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
✓
Buy a pre-built API such as the Gemini API and integrate it with prompt engineering for personalization
Buying a pre-built API like the Gemini API and using prompt engineering for personalization gives the startup fast time-to-market with minimal ML expertise and low maintenance, since Google manages the model infrastructure. Prompt engineering can tailor email drafts without training or fine-tuning, aligning with the need for speed and low operational overhead.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Select a model from Model Garden and deploy it on Vertex AI
Why it's wrong here
Deploying a model from Model Garden on Vertex AI requires the startup to manage model hosting, scaling, and prompt engineering, which contradicts their need for low maintenance and limited ML expertise. This option is tempting because it offers a curated library of pre-trained models for teams with some ML capability, and it would be correct if the startup had dedicated ML engineers to handle deployment and optimisation.
- ✗
Fine-tune an open-source model on a corpus of email drafts to create a custom model
Why it's wrong here
Fine-tuning demands curated training data, GPU compute and ongoing model maintenance, which exceeds a startup's limited ML expertise and contradicts the low-maintenance, fast time-to-market requirement. It is tempting because fine-tuning genuinely customises tone and domain vocabulary when you already possess labelled corpora and MLOps capacity.
- ✓
Buy a pre-built API such as the Gemini API and integrate it with prompt engineering for personalization
Why this is correct
A pre-built API delivers generative capability immediately, with no model training, hosting or tuning burden, meeting the fast time-to-market and low-maintenance constraints. Prompt engineering supplies the personalisation, so the startup avoids building and operating its own model infrastructure.
- ✗
Build a custom transformer model from scratch
Why it's wrong here
Training a transformer from scratch demands large labelled datasets, GPU infrastructure, and specialist ML staff the startup lacks, so it cannot meet fast time-to-market or low maintenance. It suits organisations with mature ML teams and a need for proprietary model behaviour, not a SaaS feature needing rapid delivery.
Go deeper
Related to this question
About these practice questions
One of 1,008 original Generative AI Leader practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.