PMLE Monitoring ML Solutions Practice Question

An ML engineer has deployed a tabular binary classification model to a Vertex AI Endpoint. After enabling Vertex AI Model Monitoring with training-serving skew detection, the engineer notices that the feature 'customer_age' is flagged as skewed. The feature values at serving time appear to be shifted upward by about 10 years compared to the training data. Which of the following is the most likely root cause?

⚠ Common exam trap

The trap here is assuming that model monitoring skew alerts are caused by model bias or data quality issues, when they actually detect distribution differences between training and serving data.

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

✓

The training dataset contained a different feature distribution than the serving data because the model was trained on historical data from an older customer base.

Training-serving skew detection compares the distribution of feature values in production against the training baseline. A systematic upward shift in 'customer_age' indicates that the serving population is older than the training population. This is a common scenario when a model is trained on historical data and deployed later, as demographic shifts occur.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
The endpoint is receiving malformed requests that contain incorrect age values.
Why it's wrong here
Malformed requests would likely cause errors or invalid values, but the scenario states the values are shifted upward by about 10 years, which is a systematic shift, not random corruption. Malformed data would typically produce missing or out-of-range values, not a consistent distribution shift.
✗
The model's predictions are biased, causing the monitoring system to misinterpret the feature values.
Why it's wrong here
Model monitoring for skew compares feature distributions, not predictions. Prediction bias does not affect feature-level skew detection. The monitoring system analyzes the input features directly, so a biased model would not cause a feature to be flagged as skewed.
✗
The monitoring configuration uses an incorrect sampling rate, leading to a false positive alert.
Why it's wrong here
Sampling rate affects the number of requests analyzed, but a consistent 10-year shift in the feature distribution is unlikely to be a sampling artifact. A low sampling rate might increase variance, but it would not produce a systematic bias of that magnitude.
✓
The training dataset contained a different feature distribution than the serving data because the model was trained on historical data from an older customer base.
Why this is correct
Training-serving skew occurs when the feature distribution in production differs from the training data. If the model was trained on an older customer base, the 'customer_age' distribution would naturally be lower than the current serving population, causing the skew alert. This is a classic example of data drift due to changing population.

Go deeper

PMLE Monitoring ML Solutions Practice Question

Why each option matters

Option-by-option breakdown

Related to this question