Home › Certifications › GCP Professional ML Engineer › Monitoring, Drift and Generative AI Evaluation
24 multiple-choice questions and 8 flashcards on Monitoring, Drift and Generative AI Evaluation, about 8% of the GCP Professional ML Engineer bank. Every one carries a written rationale.
Monitoring, Drift and Generative AI Evaluation is one of 8 chapters in CoStudy's GCP Professional ML Engineer bank, and it holds 24 of the bank's 300 multiple-choice questions — roughly 8% of the total. That proportion is not arbitrary: chapters follow the certifying body's published exam outline, and the number of questions in each is set by that domain's published weight, so the share of your practice time this chapter takes matches the share of the real exam it accounts for.
Studying by chapter is worth doing once you have a diagnostic score. A single overall percentage tells you whether you are close; it does not tell you which domain is dragging. Working a weak chapter in isolation, and re-testing it in isolation, is the fastest way to move a score that has stalled — and it is why the mock exams in CoStudy report by domain rather than as one number.
3 questions drawn from this chapter, with the full rationale shown — the controlling principle behind the right answer, and why each wrong option tempts and fails.
Half-right monitoring: team monitors only top features and ignores rare-but-critical features. Risk?
Answer: C — Rare high-impact features can shift undetected; prioritize by importance
C) The controlling idea is that frequency and importance are different axes: a feature that appears rarely can still drive the decisions that matter most, so coverage should follow attribution-based importance. A tempts because top features usually do dominate on average, but averages hide the critical tail. B tempts because narrower monitoring is genuinely faster, yet speed is not the risk being asked about. D tempts for the same reason, trading a real blind spot for a small saving.
Vertex AI Model Monitoring detects:
Answer: B — Feature, prediction, and concept drift in serving
A) Infrastructure availability is a Cloud Monitoring concern. B) Correct — the managed model monitoring service compares live input and output distributions against a training baseline and alerts when they diverge. C) Error Reporting surfaces exceptions. D) Budgets and alerts live in billing.
Half-right monitoring: team monitors data drift but not model performance (accuracy, AUC, etc.). Risk?
Answer: A — Drift can be benign or severe; without ground truth you cannot tell either way
A) The controlling idea is that input drift is a leading indicator, not a verdict: only labelled outcomes reveal whether accuracy or AUC actually degraded. B tempts because drift magnitude feels informative, but large shifts can be harmless and small ones can be fatal. C tempts because skipping metrics is faster, yet training duration is unrelated to production monitoring. D tempts by framing the omission as savings, but the saving is trivial next to the blind spot.
1 cards from the 8 in this chapter.
Vertex AI Model Monitoring?
Detect drift in features + prediction outputs. Compare production samples to training baseline. Alert via Cloud Logging.
These are a sample. The full Monitoring, Drift and Generative AI Evaluation chapter runs 32 items with per-chapter progress tracking, on the web and in the iOS app.
Open GCP Professional ML Engineer in CoStudy →