- A
Set up a Cloud Monitoring alert for feature store entity count.
Why wrong: Entity count doesn't indicate freshness.
- B
Schedule a nightly BigQuery batch job to compare feature values.
Why wrong: Batch job is offline, not real-time monitoring.
- C
Create a custom metric in Cloud Monitoring that tracks the time since last feature update, and set an alert threshold.
Directly measures staleness.
- D
Enable detailed audit logs in Feature Store and export to BigQuery.
Why wrong: Audit logs show who accessed, not freshness.
Quick Answer
The answer is to create a custom metric in Cloud Monitoring that tracks the time since the last feature update and set an alert threshold. This approach is most effective because it directly measures feature freshness in the online store, which is critical for online predictions where stale features silently degrade model accuracy. Vertex AI Feature Store does not natively expose a freshness metric, so a custom metric allows you to capture the timestamp of the last write operation and alert when that timestamp exceeds your staleness tolerance. On the Google Professional Machine Learning Engineer exam, this question tests your understanding that monitoring for production ML systems must be real-time and feature-specific, not just infrastructure-level. A common trap is choosing nightly batch validation, which is too slow for online serving, or entity count monitoring, which measures volume not freshness. Remember the mnemonic: “Freshness needs a timestamp, not a count.”
PMLE Monitoring ML solutions Practice Question
This PMLE practice question tests your understanding of monitoring ml solutions. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.
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?
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.
Option C is correct because 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.
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.
- ✗
Set up a Cloud Monitoring alert for feature store entity count.
Why it's wrong here
Entity count doesn't indicate freshness.
- ✗
Schedule a nightly BigQuery batch job to compare feature values.
Why it's wrong here
Batch job is offline, not real-time 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
Directly measures staleness.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Enable detailed audit logs in Feature Store and export to BigQuery.
Why it's wrong here
Audit logs show who accessed, not freshness.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates 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.
Trap categories for this question
Command / output trap
Audit logs show who accessed, not freshness.
Detailed technical explanation
How to think about this question
Vertex AI Feature Store online stores use a key-value store (e.g., Cloud Bigtable or Redis) to serve features with low latency. A custom metric can be created by writing a Cloud Function or using the Feature Store's built-in `featurestore.googleapis.com/featurestore/online_store/feature_value_update_time` metric (if available) to emit the maximum age of feature values. Setting an alert threshold (e.g., > 1 hour) ensures that stale features are detected before they impact predictions, which is especially important for time-sensitive features like user session data or real-time inventory levels.
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 — study guide chapter
Learn the concepts, then practise the questions
- →
Monitoring 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?
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: Create a custom metric in Cloud Monitoring that tracks the time since last feature update, and set an alert threshold. — Option C is correct because 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.
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 →
Same concept, more angles
1 more ways this is tested on PMLE
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 team is using Vertex AI Feature Store to manage features for training and serving. They want to monitor the freshness of the features (i.e., how recently each feature was updated). Which approach should they take?
medium- A.Use Cloud Logging to track feature updates
- B.Use Vertex AI Feature Store's monitoring dashboard
- ✓ C.Create a custom Cloud Monitoring metric based on feature ingestion timestamps
- D.Use Cloud Audit Logs to monitor API calls
Why C: Vertex AI Feature Store does not provide a built-in monitoring dashboard for feature freshness. To track how recently each feature was updated, you must create a custom Cloud Monitoring metric based on feature ingestion timestamps, which allows you to define alerting thresholds and visualize freshness over time.
Last reviewed: Jun 24, 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.