How to Detect Feature Distribution Drift on a Vertex AI Endpoint?
You are training and deploying updated versions of a regression model with tabular data by using Vertex AI Pipelines, Vertex AI Training, Vertex AI Experiments, and Vertex AI Endpoints. The model is deployed in a Vertex AI endpoint, and your users call the model by using the Vertex AI endpoint. You want to receive an email when the feature data distribution changes significantly, so you can retrigger the training pipeline and deploy an updated version of your model. What should you do?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests whether you recognize that Vertex AI Model Monitoring natively provides prediction drift detection and alerting on endpoints, without needing custom logging or infrastructure.
For detecting significant feature data distribution changes on a deployed Vertex AI model, the recommended solution is Vertex AI Model Monitoring with prediction drift monitoring and email notifications. Community consensus strongly supports Option A as the purpose-built, out-of-the-box service for this requirement.
Choosing Cloud Logging/Cloud Monitoring or custom BigQuery/Cloud Function pipelines is the most common mistake because these services can monitor data, but they lack the specialized, automated drift detection and threshold alerting that Vertex AI Model Monitoring provides, making them unnecessarily complex and less effective.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Vertex AI Model Monitoring is the dedicated Google Cloud service designed to monitor machine learning models deployed on Vertex AI Endpoints. It can automatically detect prediction drift, which is the change in the distribution of feature values or labels over time, and it supports configuring notification channels such as email. Option A correctly combines enabling prediction drift monitoring on the endpoint with specifying a notification email, fulfilling the requirement with minimal setup and no custom code.
Why the Other Options Are Wrong
Option B suggests creating a logs-based alert from Vertex AI endpoint logs. While Cloud Logging can monitor logs, prediction drift is not inherently available as a simple log signal; it requires statistical analysis of model prediction data, which Vertex AI Model Monitoring already performs. Option C similarly relies on Cloud Monitoring logs-based metrics and threshold alerts, but this approach demands manually defining drift metrics and thresholds, duplicating the functionality provided natively by Vertex AI Model Monitoring. Option D is even more complex: exporting container logs to BigQuery, writing SQL queries, and using Cloud Functions plus Cloud Scheduler is an unnecessarily heavy solution for a feature that is integrated into Vertex AI Model Monitoring out of the box.
Community Comment Notes
Commenters overwhelmingly support Option A with 100% of votes. One comment highlights that Vertex AI Model Monitoring is specifically designed for this purpose and provides out-of-the-box functionality for monitoring the data distribution of predictions, automatically detecting drift and triggering alerts. Another commenter points out that Options B and C lack the specialized focus on prediction drift and would require more complex setup, while Option D is time-consuming and less efficient. A useful link was shared to the official Google Cloud blog post about monitoring model training-serving skew using Vertex AI, reinforcing that this service is the right choice.
Official Reference
Exam Strategy
When a question asks about detecting drift or skew on a deployed Vertex AI model, immediately look for the option that mentions Vertex AI Model Monitoring. Avoid overengineering solutions that require log exports, SQL queries, or custom alerting pipelines, as Google Cloud provides a managed service specifically for this scenario.
Related Analysis
Practice All PMLE Questions
Access 65 questions with complete answers and detailed explanations.
View Full PMLE Practice Test →