Generative AI Leader Practice Question: Business Strategies for Generative AI Solutions
A global logistics firm wants to add a generative AI feature that drafts replies to customer shipment inquiries. The team must prove business value to executives within one quarter, keep engineering effort low, and later swap in a different model without rewriting the application. Which design decision best supports those goals?
⚠ Common exam trap
The trap here is equating rapid delivery with tight coupling to one model's SDK, when the stated requirement to swap models later makes that coupling a liability.
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
✓
Call Gemini through the Vertex AI API and isolate prompt construction and model selection behind an internal abstraction layer.
Using a managed Vertex AI endpoint for Gemini accelerates delivery and removes infrastructure work, while an internal abstraction layer for prompts and model selection decouples the application from any single provider. That combination lets the firm demonstrate value quickly and later change models by adjusting one integration point rather than rewriting business logic.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Embed model-specific SDK calls directly in the application so each provider's latest features are immediately available.
Why it's wrong here
Direct SDK coupling makes the first integration quick but hard-wires provider-specific request formats, authentication, and response parsing into the codebase. Swapping models later would require rewriting those call sites and retesting, which contradicts the stated goal of changing models without application rework.
- ✗
Deploy an open-weights model on a single virtual machine and expose it through a custom REST endpoint.
Why it's wrong here
A single-VM deployment lacks the scalability and availability expected for customer-facing inquiry handling, and building a custom REST layer adds work that a managed API already provides. It also locks the team into one model family, undermining the requirement to switch models later without rewriting the application.
- ✓
Call Gemini through the Vertex AI API and isolate prompt construction and model selection behind an internal abstraction layer.
Why this is correct
Vertex AI provides a managed, enterprise-ready endpoint for Gemini, and placing prompt building and model selection behind an internal abstraction lets the team change models or parameters with minimal application changes. This keeps initial engineering effort low while preserving future flexibility, supporting a one-quarter value demonstration.
- ✗
Train a bespoke language model on historical shipment correspondence and serve it from a self-managed GPU cluster.
Why it's wrong here
Training a bespoke model demands substantial data preparation, GPU capacity, and MLOps effort that cannot realistically deliver executive-visible value in one quarter. It also increases switching cost rather than reducing it, since the custom model and its serving stack become a long-term dependency.
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.