hardMultiple Select
Data Drift Detection and Mitigation on Vertex AI
Which TWO actions are recommended to detect and mitigate data drift in a production ML system on Vertex AI?
Quick Answer
The answer is to set up Vertex AI Model Monitoring for alerting on feature distribution changes and to configure automated retraining triggered by drift thresholds. These two actions work together because Model Monitoring continuously tracks input feature statistics using divergence metrics like Jensen-Shannon divergence or L-infinity distance, detecting when the production data deviates from the training baseline. When drift exceeds a predefined threshold, the automated retraining pipeline can be triggered to adapt the model without manual intervention, ensuring sustained performance. On the Google Professional Machine Learning Engineer exam, this question tests your understanding of MLOps operationalization—specifically, the distinction between detection (monitoring alerts) and mitigation (automated retraining). A common trap is confusing manual retraining with automated pipelines, or overlooking that monitoring alone does not mitigate drift. Remember the mnemonic: “Monitor to detect, retrain to correct.”
⚠ Common exam trap
Google Cloud often tests the distinction between drift detection (monitoring input distributions) and model performance monitoring (tracking prediction errors or confidence), leading candidates to confuse E with a valid drift mitigation technique.
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
✓
Automatically retrain the model when drift exceeds thresholds
Option D is correct because Vertex AI Model Monitoring is the purpose-built service for detecting data drift in production; it continuously analyzes incoming prediction requests against a baseline and alerts when feature distribution changes (e.g., training-serving skew or drift) exceed configured thresholds. Option C is correct because automated retraining triggered when drift exceeds thresholds is the recommended mitigation action, closing the loop from detection to remediation so the model stays aligned with current data. Together, D provides detection and C provides mitigation, which is exactly what the question asks for. Option A is not recommended because ensembling multiple models addresses prediction variance/accuracy, not data drift detection or mitigation. Option B is not recommended because manual daily review does not scale and cannot reliably quantify distributional drift. Option E is not recommended because monitoring prediction errors or low confidence detects performance degradation but does not specifically identify feature distribution drift or mitigate it.
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 multiple models and use an ensemble to average predictions
Why it's wrong here
Ensembling averages predictions to raise accuracy; it neither measures nor corrects input distribution shift, so drift goes undetected. Ensembles suit reducing variance or improving robustness on stable data. Detecting drift requires Vertex AI Model Monitoring comparing serving feature distributions against the training baseline.
- ✗
Manually review model predictions daily
Why it's wrong here
Manual daily review does not scale and cannot quantify drift statistically; Vertex AI Model Monitoring computes distribution skew and drift metrics against a training baseline automatically, triggering alerts. Human inspection suits low-volume spot checks or validating a suspected anomaly, not continuous drift detection across production traffic.
- ✓
Automatically retrain the model when drift exceeds thresholds
Why this is correct
Automated retraining directly satisfies the mitigation requirement: when Vertex AI Model Monitoring flags drift beyond configured thresholds, a triggered pipeline retrains on recent data, restoring alignment between the model and the shifted production distribution. Detection alone is insufficient; this closes the loop by acting on the drift signal rather than merely reporting it.
- ✓
Set up Vertex AI Model Monitoring to alert on feature distribution changes
Why this is correct
Vertex AI Model Monitoring continuously computes feature distribution statistics and compares them against the training baseline, triggering alerts when skew or drift exceeds configured thresholds. This directly satisfies the requirement to detect data drift in production, enabling timely retraining or mitigation before prediction quality degrades.
- ✗
Monitor prediction errors and flag when confidence is low
Why it's wrong here
Low confidence flags individual uncertain predictions, not shifts in the input feature distribution, so gradual drift stays hidden. Confidence monitoring suits catching out-of-distribution single inferences or routing to human review. Drift detection needs Vertex AI Model Monitoring comparing serving distributions against the training baseline.
Go deeper
Related to this question
About these practice questions
One of 775 original PMLE 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 →
Same concept, more angles
1 more way this is tested on PMLE
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A data scientist deployed a classification model on Vertex AI Endpoints. After a week, the model's accuracy drops significantly from 92% to 78%. The data scientist suspects training-serving skew. What is the first step to confirm this?
medium- A.Look for data leakage in the training pipeline
- ✓ B.Compare feature distributions between training and serving data using Vertex AI Model Monitoring
- C.Examine the feature importance of the model
- D.Check the prediction confidence over time
Why B: Vertex AI Model Monitoring provides a built-in capability to automatically detect training-serving skew by comparing feature distributions between the training data and the live serving data. This is the most direct and efficient first step to confirm whether the accuracy drop is due to a shift in the input data distribution, which is the hallmark of training-serving skew. The data scientist can set up monitoring jobs that compute statistical distance metrics (e.g., Jensen-Shannon divergence) and alert when significant deviations occur.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PMLE 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 PMLE exam.