Generative AI Leader Fundamentals of Generative AI Practice Question
A large enterprise runs a production application that uses the Gemini API on Vertex AI for real-time content moderation. They are experiencing occasional 429 (Too Many Requests) errors during peak hours. Their current quota is 1000 requests per minute (RPM) and they are hitting around 950 RPM on average, with spikes up to 1050. They have already implemented exponential backoff and retry logic. They need to reduce the error rate without reducing the quality of moderation. Which additional measure should they take?
⚠ Common exam trap
Google Cloud often tests the misconception that scaling infrastructure (Option A) or switching models (Option B) solves API quota issues, when the real constraint is the API rate limit itself, which requires reducing the number of calls through caching or other client-side optimizations.
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
✓
Implement a local caching layer for common moderation queries.
Implementing a local caching layer for common moderation queries reduces the number of identical requests sent to the Gemini API, directly lowering the effective RPM without compromising moderation quality. Since the enterprise is already using exponential backoff and retry logic, caching addresses the root cause of hitting quota limits by eliminating redundant API calls, which is a standard pattern for rate-limit mitigation in production AI workloads.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Deploy the model on a dedicated Vertex AI endpoint with autoscaling.
Why it's wrong here
Dedicated endpoints are for custom models, not the API; autoscaling does not reduce request volume.
- ✗
Switch to a lower-tier model like Gemini 1.0 Pro to reduce quota consumption.
Why it's wrong here
Lower-tier models may have reduced accuracy or capabilities, impacting moderation quality.
- ✓
Implement a local caching layer for common moderation queries.
Why this is correct
Caching eliminates duplicate requests, reducing the request rate and errors.
- ✗
Request a quota increase from Google Cloud support.
Why it's wrong here
Quota increases can take time and may not be granted immediately; also increases potential cost.
Go deeper
Related to this question
About these practice questions
Courseiva writes every Generative AI Leader question from scratch — 683 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 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.