The answer is that the prediction requests are not being batched, and the model inference code is not optimized for concurrency. This is the most likely cause because a custom container on Vertex AI, by default, often processes requests sequentially in a single-threaded handler; without explicit batching logic or async concurrency, each incoming request queues up, leading to latency that climbs under peak load as the backlog grows. On the Google Professional Machine Learning Engineer exam, this scenario tests your understanding of how Vertex AI’s autoscaling and container lifecycle interact with your inference code—a common trap is assuming that scaling instances alone fixes latency, when the real bottleneck is inside the container’s request handler. To optimize Vertex AI custom container inference concurrency and batching, you must implement a thread pool or async loop in your prediction endpoint and aggregate requests into batches before model execution. Memory tip: think “single-threaded sink” versus “batched and concurrent—latency won’t be recurrent.”
PMLE Scaling prototypes into ML models Practice Question
This PMLE practice question tests your understanding of scaling prototypes into ml 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 team deploys a PyTorch model on Vertex AI for online predictions. They notice that after deployment, the latency increases over time, especially during peak hours. The model is served using a custom container. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The prediction requests are not being batched, and the model inference code is not optimized for concurrency.
Option D is correct because the latency increase over time, especially during peak hours, indicates that the model inference code is not handling concurrent requests efficiently. Without batching or optimized concurrency, each request is processed sequentially, causing a queue buildup under load. This is a common issue with custom containers on Vertex AI when the prediction handler is single-threaded or lacks async processing.
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 custom container does not have a health check, causing instances to be prematurely terminated.
Why it's wrong here
Would cause request failures, not latency growth.
✗
The model is not using GPU even though a GPU machine is selected.
Why it's wrong here
Would affect throughput but not latency growth over time.
✗
The model is too large for the machine's memory, causing swapping.
Why it's wrong here
Would cause high latency but also likely out-of-memory errors.
✓
The prediction requests are not being batched, and the model inference code is not optimized for concurrency.
Why this is correct
Without batching and concurrency, requests queue up, increasing latency under load.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that latency increases are always due to resource exhaustion (memory/CPU) rather than concurrency or request handling inefficiencies, leading candidates to pick Option C.
Detailed technical explanation
How to think about this question
Vertex AI online prediction uses HTTP/2 for request handling, and the custom container must implement a concurrent web server (e.g., using gunicorn with multiple workers or an async framework like FastAPI). Without concurrency, requests are queued in the container's request handler, leading to increased tail latency as the queue depth grows. Batching can be implemented at the model level (e.g., using torch.utils.data.DataLoader with batch_size > 1) to amortize inference overhead across multiple requests.
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.
Scaling prototypes into ML models — This question tests Scaling prototypes into ML models — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The prediction requests are not being batched, and the model inference code is not optimized for concurrency. — Option D is correct because the latency increase over time, especially during peak hours, indicates that the model inference code is not handling concurrent requests efficiently. Without batching or optimized concurrency, each request is processed sequentially, causing a queue buildup under load. This is a common issue with custom containers on Vertex AI when the prediction handler is single-threaded or lacks async processing.
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.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
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 scaling their prototype inference model to handle high-throughput requests with low latency. They use a custom container on Vertex AI Prediction. They notice that latency spikes occur under heavy load. What is the most effective strategy?
hard
A.Enable auto-scaling with a higher minimum number of replicas.
✓ B.Optimize model serving with batching and model warm-up.
C.Use a larger machine type with more CPUs.
D.Use a GPU-based machine.
Why B: Option C is correct because optimizing model serving with batching and model warm-up reduces per-request overhead and ensures consistent latency. Option A is wrong because adding CPUs may not help if the bottleneck is model inference computation. Option B is wrong because auto-scaling doesn't reduce latency spikes; it adds replicas over time. Option D is wrong because GPU may help but not specifically for latency spikes due to load variation.
Last reviewed: Jun 30, 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.
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.