The answer is that the latency metric includes prediction time plus log writing time. This occurs because Vertex AI Endpoints’ reported latency encompasses both the model’s inference duration and the asynchronous time required to write prediction logs to Cloud Logging. When log buffers flush—typically on a scheduled interval like every hour—the metric spikes, even though the actual user-facing prediction latency remains unaffected. On the Google Professional Machine Learning Engineer exam, this scenario tests your understanding of how monitoring metrics can conflate infrastructure overhead with model performance, a common trap where candidates assume a spike always indicates a model or endpoint issue. Remember the key distinction: the metric measures end-to-end time from request receipt to log completion, not just inference. A helpful memory tip is “logs lag, not latency”—the spike reflects log flushing, not a slowdown in predictions.
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 team uses custom training and deploys a TensorFlow model using Vertex AI Endpoints. They set up Cloud Monitoring alerts for online prediction latency. However, they notice the latency metric shows a spike every hour, but the actual user experience is fine. What could be the cause?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The metric includes prediction time plus log writing time
Option A is correct because Vertex AI Endpoints' latency metric includes both the model inference time and the time taken to write prediction logs to Cloud Logging. This log writing occurs asynchronously but can cause periodic spikes in the reported latency metric when log buffers flush, even though the actual user-facing prediction latency remains unaffected. The spike every hour aligns with log rotation or buffer flush intervals, not with actual prediction performance degradation.
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.
✓
The metric includes prediction time plus log writing time
Why this is correct
Periodic log dumping can cause hourly spikes in measured latency.
Related concept
Read the scenario before looking for a memorised answer.
Sampling would reduce data points, not cause spikes.
✗
A monitoring agent on the VM is causing additional latency
Why it's wrong here
Vertex AI Endpoints do not use monitoring agents on the VM.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that latency metrics reflect only model inference time, when in reality they may include ancillary operations like logging, causing candidates to overlook the logging overhead as the source of periodic spikes.
Detailed technical explanation
How to think about this question
Vertex AI Endpoints automatically log prediction requests and responses to Cloud Logging when logging is enabled. The reported latency metric is the sum of model inference time and log write time, where log writes are batched and flushed periodically (e.g., every hour or when buffer size is reached). This can cause the metric to show a spike at flush intervals, while the actual prediction latency experienced by users remains low. In production, teams should monitor the 'model/response_latencies' metric separately or disable request-response logging if not needed for auditing.
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
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
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: The metric includes prediction time plus log writing time — Option A is correct because Vertex AI Endpoints' latency metric includes both the model inference time and the time taken to write prediction logs to Cloud Logging. This log writing occurs asynchronously but can cause periodic spikes in the reported latency metric when log buffers flush, even though the actual user-facing prediction latency remains unaffected. The spike every hour aligns with log rotation or buffer flush intervals, not with actual prediction performance degradation.
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 →
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.