How to Configure Vertex AI Retraining to Balance Cost and Accuracy?
Short answer
D Enable model monitoring on the Vertex AI endpoint. Configure Pub/Sub to call the Cloud Function when feature drift is detected
Question
Key Takeaways
This question tests the ability to select the most efficient trigger for automated retraining pipelines, distinguishing between time-based, data-availability-based, and drift-based strategies.
To balance model accuracy with cost efficiency in Vertex AI, use feature drift detection to trigger retraining pipelines. The community agrees that monitoring for data distribution changes ensures the model stays relevant without unnecessary computational expense.
Common mistake: A common mistake is choosing Option B (Cloud Scheduler) because it is simple, but fixed-frequency retraining wastes resources when data hasn't changed.
Expert Analysis
Why the Answer Is Correct
Option D is correct because feature drift specifically identifies when the statistical distribution of the input data has shifted. Retraining only upon detecting this shift satisfies the requirement to keep the model up-to-date (by reacting to changes) while minimizing costs (by avoiding training runs when the model is still valid).
Why the Other Options Are Wrong
Option A is inefficient because new data does not always mean the data distribution has changed. Option B (Cloud Scheduler) is rigid and may trigger costly retraining when unnecessary or fail to trigger when rapid changes occur. Option C focuses on anomalies (outliers), which might indicate data quality issues rather than a need to retrain the entire model on a new distribution.
Community Comment Notes
Comments highlight that D is the most scalable approach. Users emphasize that "data-driven retraining" via drift detection is the key to balancing accuracy and cost, as noted by user [1] who explicitly mentions avoiding unnecessary training runs.
Official Reference
https://cloud.google.com/vertex-ai/docs/model-monitoring/overview
This link opens the official vendor documentation in a new tab.
Exam Strategy
Look for keywords like "minimize cost" or "up-to-date" in MLOps questions. These usually point away from scheduled jobs and towards event-driven triggers like drift detection.
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 5 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 5
-
fitri001 👍 3 Answered DData-driven Retraining: Monitoring for feature drift identifies significant changes in the underlying data distribution used to train the model. Retraining based on drift detection ensures the model stays relevant to evolving data patterns, prioritizing model accuracy. Reduced Cost: Triggering retraining only when drift is detected avoids unnecessary training runs, minimizing costs associated with Vertex AI training jobs.
-
ddogg 👍 2 Answered DD) Makes the most sense and scales
-
pikachu007 👍 1 Answered DIt proactively triggers retraining when feature drift is detected, ensuring the model adapts to changing data patterns and maintains accuracy.
-
b1a8fae 👍 1 Answered DKeep the model up to date -> monitoring drift (distribution of production data doesnt change wildly). Only rerun training when necessary.
-
winston9 👍 1 Answered Dfeature drifting detecting to trigger retraining
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All PMLE Questions
Access 65 questions with complete answers and detailed explanations.
View Full PMLE Practice Test →