Generative AI Leader Fundamentals of Generative AI Practice Question
A financial institution deploys a chatbot using Gemini Pro in Vertex AI. Compliance requires logging all user inputs and model outputs for audit. Which approach meets this requirement?
⚠ Common exam trap
It's easy for candidates to confuse Cloud Logging sinks or Cloud Monitoring with the specific Vertex AI feature that must be explicitly enabled on the endpoint, assuming that default logging captures request-response payloads when it does not.
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
✓
Enable Vertex AI Endpoint request-response logging
Vertex AI Endpoint request-response logging captures both the user's input prompt and the model's generated output, which is precisely what compliance auditing requires. This feature logs the exact payloads sent to and received from the deployed model, ensuring a complete audit trail without additional configuration.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Capture logs via Cloud Monitoring
Why it's wrong here
Cloud Monitoring records metrics, traces and dashboards, not the full prompt and response payloads auditors require. It is tempting because it is the default observability surface in Google Cloud, and it would be correct for tracking latency, error rates and resource health rather than content-level audit logging.
- ✓
Enable Vertex AI Endpoint request-response logging
Why this is correct
Endpoint request-response logging captures the full prompt and completion payloads for every prediction, storing them in Cloud Logging for audit retrieval. This directly satisfies the compliance constraint to log all user inputs and model outputs without altering application code.
- ✗
Use Cloud Logging sink with a filter for Vertex AI requests
Why it's wrong here
Cloud Logging sinks export platform-level request metadata, not the full prompt and response payloads compliance demands. It is tempting because sinks are the standard mechanism for routing Vertex AI audit logs, and would suffice where only API call records, not conversation content, require retention.
- ✗
Enable Vertex AI Model Registry logging
Why it's wrong here
Model Registry stores model versions, artefacts and metadata, not runtime request or response payloads, so no user inputs or outputs are captured. It is tempting because Registry is the natural place to track model lineage, and would be correct for auditing which model version served traffic.
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 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.