The correct answer is to monitor both the p50 and p99 latency alongside request count, then build a dashboard correlating latency versus throughput at different load levels. This strategy works because p50 latency captures the typical user experience, while p99 reveals tail behavior and potential bottlenecks under stress, and request count directly measures throughput. Together, these metrics allow you to spot performance cliffs—points where increasing throughput causes latency to spike—which is critical for maintaining service-level objectives in production ML systems. On the Google Professional Machine Learning Engineer exam, this question tests your understanding of how monitoring online prediction latency and throughput must go beyond simple averages; a common trap is focusing only on p50 or mean latency, which hides dangerous tail latency that degrades real user experience. A useful memory tip: think of the “50/99/Count” triad—the 50th percentile for the typical user, the 99th for the unlucky few, and the count to know how many users are being affected.
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 company deploys an online prediction model serving 100 requests per second. They are optimizing for both latency and throughput. Which monitoring strategy should they use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Monitor both the p50 and p99 latency, and the request count. Create a dashboard showing latency vs. throughput at different load levels.
Option D is correct because monitoring both p50 and p99 latency alongside request count provides a comprehensive view of system performance under load. Latency percentiles reveal tail behavior (p99) and typical user experience (p50), while request count tracks throughput. A dashboard correlating latency vs. throughput at different load levels is essential for identifying performance cliffs or degradation before failures occur, aligning with best practices for production ML inference systems.
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 only the request count and set an alert if it drops below a threshold.
Why it's wrong here
Doesn't capture latency.
✗
Set a single alert on the 99th percentile latency and ignore throughput since it's already high.
Why it's wrong here
Throughput can change and affect latency.
✗
Monitor the error rate and set an alert if it exceeds 1%.
Why it's wrong here
Error rate alone is insufficient.
✓
Monitor both the p50 and p99 latency, and the request count. Create a dashboard showing latency vs. throughput at different load levels.
Why this is correct
Allows understanding of the relationship.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often focus on a single metric (e.g., error rate or p99 latency) and overlook the need for multi-metric correlation, especially the latency-throughput trade-off, which is a core concept in monitoring ML systems under production load.
Detailed technical explanation
How to think about this question
In production ML serving, latency percentiles (p50, p99) are critical because p99 captures tail latency from straggler requests or resource contention, while p50 reflects median user experience. Throughput (requests per second) must be monitored alongside latency to detect the 'knee' in the latency-throughput curve, where latency increases non-linearly as load approaches system capacity. Real-world scenarios like auto-scaling decisions or batch inference tuning rely on this correlation to avoid over-provisioning or SLO violations.
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 — 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: Monitor both the p50 and p99 latency, and the request count. Create a dashboard showing latency vs. throughput at different load levels. — Option D is correct because monitoring both p50 and p99 latency alongside request count provides a comprehensive view of system performance under load. Latency percentiles reveal tail behavior (p99) and typical user experience (p50), while request count tracks throughput. A dashboard correlating latency vs. throughput at different load levels is essential for identifying performance cliffs or degradation before failures occur, aligning with best practices for production ML inference systems.
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.