Question 478 of 506
Monitoring ML solutionsmediumMultiple ChoiceObjective-mapped

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.

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?

Question 1mediummultiple choice
Full question →

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 compare the prediction distribution before and after the outage; significant drift indicates stale features.

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.

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.

  • Monitor the prediction request latency to see if it remains low.

    Why it's wrong here

    Low latency is a symptom, not a confirmation of stale features.

  • Use Vertex AI Model Monitoring to compare the prediction distribution before and after the outage; significant drift indicates stale features.

    Why this is correct

    Drift detection directly reveals changes in model behavior due to input changes.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Verify the feature store's read throughput and latency metrics to ensure it is healthy.

    Why it's wrong here

    Doesn't tell which predictions used stale data.

  • Check the error rate for the endpoint; if no errors, then features were retrieved correctly.

    Why it's wrong here

    The model may have used cached or default values without errors.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates assume no errors means no problem, but the question explicitly describes a silent failure where the model uses stale features without raising any error, so metrics like latency or error rate are irrelevant for detecting feature staleness.

Detailed technical explanation

How to think about this question

Under the hood, when a feature store lookup fails, the model serving code may fall back to a default value or a previously cached feature, which can skew the prediction distribution. Vertex AI Model Monitoring compares the statistical distribution of predictions (e.g., using the Jensen-Shannon divergence) against a baseline; a significant shift indicates that the input features have changed, even if no explicit errors are logged. In practice, this is a common silent failure mode in production ML systems where missing feature lookups are handled gracefully but degrade model accuracy.

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.

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.

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: Use Vertex AI Model Monitoring to compare the prediction distribution before and after the outage; significant drift indicates stale features. — 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.

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 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.

Loading comments…

Sign in to join the discussion.

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.