The correct approach is to analyze the prediction output distribution using Vertex AI Model Monitoring for prediction drift and compare it to a baseline. This is the right technique because a drop in click-through rate (CTR) without input data drift or skew indicates that the model’s predictions themselves have shifted—the distribution of output scores is now different from the training baseline, even though the incoming features look normal. On the Google Professional Machine Learning Engineer exam, this scenario tests your understanding that prediction drift monitoring in Vertex AI catches subtle model behavior changes that data drift misses; a common trap is to focus on the increased latency as the root cause, but latency is a symptom, not the driver of CTR decline. Remember the key distinction: data drift checks inputs, prediction drift checks outputs—when performance drops but inputs are stable, always suspect prediction drift.
PMLE Monitoring ML solutions Practice Question
This PMLE practice question tests your understanding of monitoring ml solutions. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
An e-commerce company uses a Vertex AI endpoint for product recommendations. Recently, the click-through rate (CTR) dropped significantly. Model monitoring shows no significant data drift or skew. Logs show increased latency but no errors. Which technique should the engineer use to diagnose the issue?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Analyze the prediction output distribution using Vertex AI Model Monitoring for prediction drift and compare to a baseline.
Option D is correct because the drop in CTR despite no data drift or skew suggests that the model's predictions have shifted in distribution (prediction drift), even if the input features remain stable. Vertex AI Model Monitoring can compare the current prediction output distribution against a baseline to detect such drift, which directly explains the CTR decline. The increased latency is a symptom, not the root cause, and fixing latency alone would not restore CTR.
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.
✗
Increase the endpoint's request timeout value to accommodate the higher latency.
Why it's wrong here
Does not address the CTR drop.
✗
Enable autoscaling on the endpoint to reduce latency by adding more nodes.
Why it's wrong here
Helps with latency but not CTR.
✗
Retrain the model with the most recent user interaction data.
Why it's wrong here
May introduce new issues without understanding root cause.
✓
Analyze the prediction output distribution using Vertex AI Model Monitoring for prediction drift and compare to a baseline.
Why this is correct
Prediction drift can directly impact CTR even without data drift.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the distinction between data drift (input distribution changes) and prediction drift (output distribution changes), and candidates mistakenly assume that no data drift means the model is fine, overlooking that the model's predictions can still degrade due to concept drift.
Detailed technical explanation
How to think about this question
Prediction drift occurs when the model's output probabilities shift over time due to changes in the underlying relationship between features and labels (concept drift), even if input features remain unchanged. Vertex AI Model Monitoring for prediction drift uses statistical tests like the Kolmogorov-Smirnov test or Jensen-Shannon divergence to compare the current prediction distribution against a baseline. In practice, this can happen when user preferences evolve (e.g., seasonal trends) without corresponding changes in input features, causing the model to recommend irrelevant items and reducing CTR.
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.
Monitoring ML solutions — This question tests Monitoring ML solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Analyze the prediction output distribution using Vertex AI Model Monitoring for prediction drift and compare to a baseline. — Option D is correct because the drop in CTR despite no data drift or skew suggests that the model's predictions have shifted in distribution (prediction drift), even if the input features remain stable. Vertex AI Model Monitoring can compare the current prediction output distribution against a baseline to detect such drift, which directly explains the CTR decline. The increased latency is a symptom, not the root cause, and fixing latency alone would not restore CTR.
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 →
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 financial services company uses a custom container to serve a fraud detection model on Vertex AI Endpoints. The model requires a feature store lookup for each prediction. Recently, the feature store (Cloud Bigtable) experienced a brief outage, causing some predictions to fail. After the outage resolved, the endpoint's CPU utilization dropped significantly, and prediction latency improved. However, the model's false positive rate increased sharply. The ML engineer suspects the model is using stale features because the feature store outage caused missing lookups. Cloud Monitoring for the endpoint shows no errors after the outage, but the number of feature store read requests per prediction decreased by 30%. Which metric should the engineer use to confirm the hypothesis of stale features?
medium
A.Monitor the prediction request latency to see if it remains low.
✓ B.Use Vertex AI Model Monitoring to compare the prediction distribution before and after the outage; significant drift indicates stale features.
C.Verify the feature store's read throughput and latency metrics to ensure it is healthy.
D.Check the error rate for the endpoint; if no errors, then features were retrieved correctly.
Why B: Option B is correct because Vertex AI Model Monitoring can detect prediction distribution drift, which directly indicates that the model is receiving different input features than expected. A significant drift after the outage, combined with the 30% drop in feature store read requests, confirms that stale or default features were substituted for missing lookups, causing the false positive rate to spike.
Variation 2. A financial services company uses a custom deep learning model on Vertex AI to automatically approve or reject credit card transactions. The model is explainable using Vertex Explainable AI, and the company monitors feature attribution drift with thresholds defined per feature. Last week, the monitoring system flagged that the mean absolute attribution score for the 'transaction_amount' feature increased from 0.35 to 0.55. The overall model accuracy, measured on a daily batch of labeled transactions, has remained around 97%. The operations team is concerned about potential compliance issues due to changing model behavior. What should the data scientist do?
medium
A.Tune the alert threshold for 'transaction_amount' to 0.6 to avoid future false alarms.
B.Retrain the model by increasing regularization to reduce the importance of the 'transaction_amount' feature.
✓ C.Investigate whether there has been a shift in the distribution of 'transaction_amount' values in the recent transaction data, which could explain the attribution change.
D.Disable the feature attribution drift monitoring for 'transaction_amount' since the model accuracy is stable.
Why C: Option C is correct because a shift in the distribution of the 'transaction_amount' feature (e.g., due to seasonality or a new customer segment) can naturally cause its attribution score to change without indicating model degradation. Vertex Explainable AI computes feature attributions relative to the current data distribution; if the input values shift, the model's reliance on that feature may legitimately increase. Investigating the distribution shift is the first diagnostic step before adjusting thresholds or retraining, as stable accuracy does not rule out data drift that could lead to compliance issues.
Last reviewed: Jun 30, 2026
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.
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.