The answer is to enable Vertex AI Model Monitoring for feature drift and configure alerts to trigger a Vertex AI Pipelines retraining run. This is correct because Vertex AI Model Monitoring is purpose-built to detect drift and trigger retraining by comparing live inference data against a training baseline, automatically identifying when the production data distribution has shifted—exactly the scenario causing the 15% accuracy drop. On the Google Professional Data Engineer exam, this tests your understanding of MLOps automation: the key trap is choosing a manual monitoring solution or a separate retraining service that lacks integrated drift detection, whereas Vertex AI Model Monitoring directly feeds into Pipelines for a closed-loop retraining workflow. Remember the memory tip: “Monitor for drift, then Pipelines for the lift”—the monitoring detects the shift, and the pipeline handles the retraining automatically.
PDE Operationalizing machine learning models Practice Question
This PDE practice question tests your understanding of operationalizing machine learning models. Compare every option against the stated constraints before choosing — the best answer satisfies all requirements, not just the most obvious one. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A data science team deploys a TensorFlow image classification model to Vertex AI Prediction. The model performs well in offline evaluation but shows a 15% drop in accuracy in production. The production data distribution has shifted compared to the training data. The team needs to continuously monitor and retrain the model. Which solution is most appropriate for detecting drift and triggering retraining?
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 Model Monitoring for feature drift; configure alerts to trigger a Vertex AI Pipelines retraining run.
Vertex AI Model Monitoring is purpose-built for detecting feature drift in production ML models by comparing live inference data against a baseline distribution. When drift is detected, it can directly trigger a Vertex AI Pipelines retraining run, creating an automated, end-to-end MLOps loop that addresses the production accuracy drop without manual intervention.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Enable Vertex AI Model Monitoring for feature drift; configure alerts to trigger a Vertex AI Pipelines retraining run.
Why this is correct
Vertex AI Model Monitoring detects drift and can trigger automated retraining.
Related concept
Read the scenario before looking for a memorised answer.
✗
Export production predictions to Cloud Logging, then use Log Analytics to compare distributions.
Why it's wrong here
Logging is not designed for distribution analysis.
✗
Store predictions in BigQuery and run scheduled SQL queries to detect drift; trigger retraining via Cloud Functions.
Why it's wrong here
BigQuery is a storage/query service, not a drift detection tool.
✗
Use Cloud Monitoring to track prediction latency and error rates; manually retrain when errors increase.
Why it's wrong here
Monitoring latency/errors does not detect data drift.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the distinction between operational monitoring (latency, errors) and data-quality monitoring (feature drift), leading candidates to mistakenly choose Cloud Monitoring (Option D) because they confuse production health metrics with model-specific distribution shifts.
Detailed technical explanation
How to think about this question
Vertex AI Model Monitoring uses the Jensen-Shannon divergence or L-infinity distance to compare the feature distribution of recent predictions against a training baseline, with configurable alert thresholds. Under the hood, it samples prediction requests from the deployed model endpoint and computes these metrics in near real-time, enabling early detection of drift before accuracy degrades significantly. In a real-world scenario, a retail recommendation model might see a sudden shift in user demographics due to a marketing campaign, and Vertex AI Model Monitoring would automatically flag the drift and trigger a retraining pipeline that incorporates the new data distribution.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Operationalizing machine learning models — This question tests Operationalizing machine learning models — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Enable Vertex AI Model Monitoring for feature drift; configure alerts to trigger a Vertex AI Pipelines retraining run. — Vertex AI Model Monitoring is purpose-built for detecting feature drift in production ML models by comparing live inference data against a baseline distribution. When drift is detected, it can directly trigger a Vertex AI Pipelines retraining run, creating an automated, end-to-end MLOps loop that addresses the production accuracy drop without manual intervention.
What should I do if I get this PDE question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
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. You have deployed a classification model on Vertex AI Endpoints. The model's training data had a balanced class distribution, but over time, the production data has shifted such that one class appears 90% of the time. The model's overall accuracy remains high, but the recall for the minority class has dropped significantly. What is the best approach to detect and address this issue?
medium
A.Retrain the model daily on the entire historical dataset
✓ B.Set up Vertex AI Model Monitoring to detect skew and drift, and retrain using a sliding window of recent data
C.Increase the number of replicas on the endpoint to reduce latency
D.Adjust the decision threshold to improve minority class recall
Why B: Vertex AI Model Monitoring is specifically designed to detect skew and drift between training and serving data. In this scenario, the production data has shifted to 90% of one class, which is a clear case of data drift. By setting up monitoring, you can be alerted to this drift and then retrain the model using a sliding window of recent data, which adapts to the new distribution without requiring full retraining on the entire historical dataset. This approach directly addresses the root cause—the shift in class distribution—rather than just treating symptoms.
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This PDE 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 PDE exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.