mediumMultiple Choice
PMLE Practice Question: Your ML pipeline uses Vertex AI Feature Store to…
Your ML pipeline uses Vertex AI Feature Store to serve features for online predictions. You need to monitor the freshness of features in the online store. Which approach is most effective?
⚠ Common exam trap
Test-takers frequently confuse monitoring entity count (a capacity metric) with freshness, or assume that batch comparison or audit logs provide real-time monitoring, when only a custom staleness metric with alerting directly addresses the requirement.
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
✓
Create a custom metric in Cloud Monitoring that tracks the time since last feature update, and set an alert threshold.
Cloud Monitoring custom metrics allow you to track the timestamp of the last feature update in Vertex AI Feature Store and set an alert threshold for staleness. This directly measures feature freshness, which is critical for online predictions where stale features can degrade model accuracy. Other options either measure unrelated metrics (entity count), are too slow (nightly batch), or focus on auditing rather than real-time monitoring.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set up a Cloud Monitoring alert for feature store entity count.
Why it's wrong here
Entity count reports how many entities exist, not when their feature values were last written, so staleness goes undetected. It is tempting because Cloud Monitoring metrics suit capacity and volume tracking; it would be the right choice for alerting on unexpected entity growth or quota consumption in the online store.
- ✗
Schedule a nightly BigQuery batch job to compare feature values.
Why it's wrong here
A nightly batch comparison detects staleness only once daily, missing freshness degradation between runs for online predictions. It tempts because BigQuery jobs are familiar for scheduled checks, and would be correct for offline batch validation, but online serving needs continuous timestamp-based monitoring.
- ✓
Create a custom metric in Cloud Monitoring that tracks the time since last feature update, and set an alert threshold.
Why this is correct
Feature freshness is a temporal property not exposed by default Vertex AI Feature Store metrics. A custom Cloud Monitoring metric recording time since the last feature update, paired with an alert threshold, directly detects stale online values before they degrade predictions.
- ✗
Enable detailed audit logs in Feature Store and export to BigQuery.
Why it's wrong here
Audit logs record administrative and API activity, not feature value timestamps, so they cannot reveal staleness. It tempts because audit logging is a standard monitoring tool, and would be correct for tracking who changed a featurestore, but freshness requires comparing ingestion timestamps against serving time.
Go deeper
Related to this question
About these practice questions
One of 775 original PMLE practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.