Generative AI Leader Practice Question: Business Strategies for Generative AI Solutions
A startup with limited budget wants to quickly test a generative AI use case for personalized email marketing. Which approach minimizes time-to-market and cost?
⚠ Common exam trap
Google Cloud often tests the misconception that fine-tuning (Option C) is always the fastest and cheapest path for customization, but the trap here is that fine-tuning still requires significant compute and data preparation, whereas prompt engineering on a managed API is truly zero-infrastructure and pay-per-use, making it the optimal choice for a quick, low-cost test.
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
✓
Use a managed API like the PaLM API with prompt engineering.
Using a managed API like the PaLM API with prompt engineering eliminates the need for infrastructure setup, model training, and data preparation. This approach leverages a pre-trained model via a simple REST API call, allowing the startup to iterate on prompts and achieve personalized email content in hours rather than weeks, minimizing both time-to-market and cost.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Hire a team of AI researchers to build a solution.
Why it's wrong here
Hiring researchers delivers bespoke model development, not a pre-trained foundation model accessed through an API, so it cannot produce a working prototype within weeks. It is tempting because custom research suits organisations needing proprietary architectures or novel capabilities unavailable off the shelf, where differentiation justifies the cost and long timeline.
- ✗
Develop a custom model from scratch.
Why it's wrong here
Training a model from scratch demands large labelled datasets, GPU clusters and ML engineering time, so it cannot deliver a quick, low-cost test. It is tempting because bespoke training suits organisations with proprietary data and strict control needs, where a unique domain model justifies the investment. Here, a pre-trained foundation model accessed via API satisfies the same use case far sooner.
- ✗
Fine-tune a large open-source model on internal data.
Why it's wrong here
Fine-tuning a large open-source model requires substantial GPU compute, labelled training data and ML engineering effort, so it cannot minimise cost or time-to-market for a quick test. It is tempting because fine-tuning genuinely improves domain-specific tone and accuracy once a use case is validated at scale.
- ✓
Use a managed API like the PaLM API with prompt engineering.
Why this is correct
A managed API such as the PaLM API removes infrastructure, training, and hosting overhead, letting the startup validate personalised email marketing through prompt engineering alone. This directly minimises both time-to-market and cost, matching the limited-budget constraint.
Go deeper
Related to this question
About these practice questions
This Generative AI Leader question is part of Courseiva's 1,008-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.