- A
Convert the model to a different framework that is faster.
Why wrong: Major change without diagnosis is risky.
- B
Enable Cloud Trace to analyze request latency across services.
Cloud Trace provides detailed latency breakdowns.
- C
Check the endpoint's autoscaling metrics and cold start frequency.
Cold starts or insufficient scaling can cause latency.
- D
Increase the number of replicas to reduce load per replica.
Why wrong: Treats symptom, not root cause.
- E
Set the logging verbosity to DEBUG in the container.
Why wrong: Debug logging adds overhead and doesn't pinpoint latency.
Quick Answer
The answer is to check the endpoint's autoscaling metrics and cold start frequency. These two actions directly reveal the root causes of high latency: autoscaling metrics show whether the endpoint is under-provisioned and struggling to keep up with request volume, while cold start frequency indicates how often new inference instances are being initialized from scratch, which adds significant delay. On the Google Professional Machine Learning Engineer exam, this question tests your ability to distinguish between diagnosing a problem and applying a fix—common traps include jumping to solutions like increasing replica count or changing the model framework, which mask symptoms rather than uncover the underlying bottleneck. A key memory tip is to think of the diagnostic triad: scale, start, and serve—check scaling metrics first, then cold starts, before tuning serving infrastructure.
PMLE Serving and scaling models Practice Question
This PMLE practice question tests your understanding of serving and scaling models. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 model serving team is experiencing high latency in production. Which TWO actions should they take to diagnose the root cause? (Choose 2.)
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
Enable Cloud Trace to analyze request latency across services.
Options A and D are correct. Option B is wrong because increasing replicas may mask the issue but not diagnose. Option C is wrong because converting framework may not address latency. Option E is wrong because log level changes do not provide granular latency analysis.
Key principle: Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Convert the model to a different framework that is faster.
Why it's wrong here
Major change without diagnosis is risky.
- ✓
Enable Cloud Trace to analyze request latency across services.
Why this is correct
Cloud Trace provides detailed latency breakdowns.
Related concept
CIDR notation defines the prefix length.
- ✓
Check the endpoint's autoscaling metrics and cold start frequency.
Why this is correct
Cold starts or insufficient scaling can cause latency.
Related concept
CIDR notation defines the prefix length.
- ✗
Increase the number of replicas to reduce load per replica.
Why it's wrong here
Treats symptom, not root cause.
- ✗
Set the logging verbosity to DEBUG in the container.
Why it's wrong here
Debug logging adds overhead and doesn't pinpoint latency.
Common exam traps
Common exam trap: usable hosts are not the same as total addresses
Subnetting questions often tempt you into counting all addresses. In normal IPv4 subnets, the network and broadcast addresses are not usable host addresses.
Detailed technical explanation
How to think about this question
Subnetting questions test whether you can identify the network, broadcast address, usable range, mask and correct subnet. Slow down enough to calculate the block size correctly.
KKey Concepts to Remember
- CIDR notation defines the prefix length.
- Block size helps identify subnet boundaries.
- Network and broadcast addresses are not usable hosts in normal IPv4 subnets.
- The required host count determines the smallest suitable subnet.
TExam Day Tips
- Write the block size before choosing the subnet.
- Check whether the question asks for hosts, subnets or a specific address range.
- Do not confuse /24, /25, /26 and /27 host counts.
Key takeaway
Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets.
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. Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets. 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.
Review block sizes, usable host formulas (2^n − 2), and how to find network and broadcast addresses for /24 through /30. Then practise related PMLE subnetting questions on CIDR, address ranges, and subnet selection.
- →
Serving and scaling models — study guide chapter
Learn the concepts, then practise the questions
- →
Serving and scaling models 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?
Serving and scaling models — This question tests Serving and scaling models — CIDR notation defines the prefix length..
What is the correct answer to this question?
The correct answer is: Enable Cloud Trace to analyze request latency across services. — Options A and D are correct. Option B is wrong because increasing replicas may mask the issue but not diagnose. Option C is wrong because converting framework may not address latency. Option E is wrong because log level changes do not provide granular latency analysis.
What should I do if I get this PMLE question wrong?
Review block sizes, usable host formulas (2^n − 2), and how to find network and broadcast addresses for /24 through /30. Then practise related PMLE subnetting questions on CIDR, address ranges, and subnet selection.
What is the key concept behind this question?
CIDR notation defines the prefix length.
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 →
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.