- A
Use a scheduled pipeline that always retrains
Why wrong: Wrong: Inefficient; retrains even without drift.
- B
Use Cloud Monitoring alerts on data drift to trigger retraining
Why wrong: Wrong: Requires custom implementation; not native.
- C
Use Vertex AI Model Monitoring to detect drift and trigger a pipeline
Correct: Native drift detection and retriggering.
- D
Use Cloud Functions on schedule to compare distributions
Why wrong: Wrong: Manual, less efficient, and not integrated.
Quick Answer
The answer is to use Vertex AI Model Monitoring to detect drift and trigger a pipeline. This is the most efficient approach because it eliminates unnecessary weekly retraining by only initiating a retrain when the new week’s data significantly changes the data distribution, directly addressing the core requirement of AutoML forecasting retrain on drift. On the Google Professional Machine Learning Engineer exam, this question tests your understanding of event-driven MLOps and cost optimization—a common trap is assuming scheduled retraining is always best, but the exam emphasizes triggering retraining only when statistical drift is detected. The key memory tip is “monitor first, trigger second”: think of Model Monitoring as the guard that opens the retraining gate only when the data distribution shifts, not on a fixed calendar.
PMLE Architecting low-code ML solutions Practice Question
This PMLE practice question tests your understanding of architecting low-code ml solutions. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 team is using Vertex AI AutoML to train a forecasting model. They need to retrain the model weekly and only if the new week's data significantly changes the data distribution. What is the most efficient way to achieve this?
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
Use Vertex AI Model Monitoring to detect drift and trigger a pipeline
Option C is correct because Vertex AI Model Monitoring can be configured to detect data drift on the model's input features, and when drift exceeds a threshold, it can trigger a Cloud Function or a Vertex AI pipeline to retrain the model. This approach avoids unnecessary retraining when the data distribution has not changed significantly, which is more efficient than always retraining. The integration with Cloud Functions or Pub/Sub allows for a serverless, event-driven retraining pipeline that only runs when needed.
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.
- ✗
Use a scheduled pipeline that always retrains
Why it's wrong here
Wrong: Inefficient; retrains even without drift.
- ✗
Use Cloud Monitoring alerts on data drift to trigger retraining
Why it's wrong here
Wrong: Requires custom implementation; not native.
- ✓
Use Vertex AI Model Monitoring to detect drift and trigger a pipeline
Why this is correct
Correct: Native drift detection and retriggering.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use Cloud Functions on schedule to compare distributions
Why it's wrong here
Wrong: Manual, less efficient, and not integrated.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the distinction between infrastructure monitoring (Cloud Monitoring) and model-specific monitoring (Vertex AI Model Monitoring), and candidates mistakenly choose Cloud Monitoring because they think it can detect data drift, but it lacks the statistical algorithms needed for feature-level distribution comparison.
Detailed technical explanation
How to think about this question
Vertex AI Model Monitoring uses the Jensen-Shannon divergence (JSD) or the L-infinity distance to compare the distribution of each feature in the serving data against a baseline training distribution. When the drift score exceeds a user-defined threshold, it can emit a Cloud Logging log entry, which can then be routed via Pub/Sub to trigger a Cloud Function or a Vertex AI pipeline. This event-driven architecture ensures that retraining is triggered only when statistically significant drift is detected, optimizing both cost and model freshness.
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.
- →
Architecting low-code ML solutions — study guide chapter
Learn the concepts, then practise the questions
- →
Architecting low-code ML solutions practice questions
Targeted practice on this topic area only
- →
All PMLE questions
506 questions across all exam domains
- →
Google Professional Machine Learning Engineer study guide
Full concept coverage aligned to exam objectives
- →
PMLE practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PMLE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Scaling prototypes into ML models practice questions
Practise PMLE questions linked to Scaling prototypes into ML models.
Automating and orchestrating ML pipelines practice questions
Practise PMLE questions linked to Automating and orchestrating ML pipelines.
Collaborating within and across teams to manage data and models practice questions
Practise PMLE questions linked to Collaborating within and across teams to manage data and models.
Architecting low-code ML solutions practice questions
Practise PMLE questions linked to Architecting low-code ML solutions.
Collaborating to manage data and models practice questions
Practise PMLE questions linked to Collaborating to manage data and models.
Serving and scaling models practice questions
Practise PMLE questions linked to Serving and scaling models.
Monitoring ML solutions practice questions
Practise PMLE questions linked to Monitoring ML solutions.
Solving business challenges with ML practice questions
Practise PMLE questions linked to Solving business challenges with ML.
PMLE fundamentals practice questions
Practise PMLE questions linked to PMLE fundamentals.
PMLE scenario practice questions
Practise PMLE questions linked to PMLE scenario.
PMLE troubleshooting practice questions
Practise PMLE questions linked to PMLE troubleshooting.
Practice this exam
Start a free PMLE practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this PMLE question test?
Architecting low-code ML solutions — This question tests Architecting low-code ML solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use Vertex AI Model Monitoring to detect drift and trigger a pipeline — Option C is correct because Vertex AI Model Monitoring can be configured to detect data drift on the model's input features, and when drift exceeds a threshold, it can trigger a Cloud Function or a Vertex AI pipeline to retrain the model. This approach avoids unnecessary retraining when the data distribution has not changed significantly, which is more efficient than always retraining. The integration with Cloud Functions or Pub/Sub allows for a serverless, event-driven retraining pipeline that only runs when needed.
What should I do if I get this PMLE 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 →
Last reviewed: Jun 30, 2026
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.
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.