The answer is that the `min_nodes` setting is too low, and increasing it to handle baseline traffic is the correct solution. This is because Vertex AI autoscaling provisions new instances based on load, but it cannot scale instantly; if `min_nodes` is set too low, the autoscaler starts from an insufficient baseline, and during a flash sale where traffic spikes 10x, the provisioning lag causes high latency as new nodes spin up. On the Google Professional Machine Learning Engineer exam, this scenario tests your understanding of Vertex AI autoscaling configuration issues, specifically the trade-off between cost and responsiveness—a common trap is assuming `max_nodes` alone solves scaling, but the real bottleneck is the starting capacity. A helpful memory tip: think of `min_nodes` as your "safety buffer" for sudden bursts; set it high enough to absorb the first wave of traffic, and autoscaling handles the rest.
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 company deploys a model to Vertex AI Prediction with autoscaling enabled. During a flash sale, traffic spikes 10x, but the endpoint fails to scale fast enough, causing high latency. What is the most likely cause and solution?
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 min_nodes setting is too low; increase min_nodes to handle baseline traffic
The correct answer is A. With Vertex AI Prediction autoscaling, the `min_nodes` setting defines the baseline number of instances that are always kept running. During a flash sale, traffic spikes 10x, but if `min_nodes` is set too low, the autoscaler cannot provision new instances quickly enough to handle the sudden load, resulting in high latency. Increasing `min_nodes` ensures a sufficient baseline capacity to absorb the initial spike while the autoscaler scales up additional nodes.
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 min_nodes setting is too low; increase min_nodes to handle baseline traffic
Why this is correct
Higher min nodes allow faster scaling as they are already running.
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.
✗
Switch to preemptible VMs to reduce cost and allow more instances
Why it's wrong here
Preemptible VMs are not supported for Vertex AI Prediction.
✗
The model container is too large; rebuild with a smaller image
Why it's wrong here
Image size affects start time but not autoscaling responsiveness.
✗
Use Cloud Functions to pre-warm instances before the sale
Why it's wrong here
Cloud Functions cannot pre-warm Vertex AI endpoints.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that autoscaling is instantaneous or that external services like Cloud Functions can directly pre-warm ML instances, when in reality the root cause is an insufficient baseline capacity (`min_nodes`) to handle the initial burst before the autoscaler catches up.
Detailed technical explanation
How to think about this question
Vertex AI Prediction autoscaling uses a target utilization metric (default 60% of CPU or memory) to trigger scaling events, but scaling up is not instantaneous—it involves provisioning new VM instances, pulling the container image, and loading the model, which can take several minutes. The `min_nodes` parameter acts as a buffer to absorb traffic bursts during this provisioning delay; setting it too low means the autoscaler starts from a deficit, leading to request queuing and latency. In practice, for flash sales, you might also combine `min_nodes` with a higher `max_nodes` and configure a custom scaling metric based on request queue depth to trigger scaling earlier.
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 startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
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 min_nodes setting is too low; increase min_nodes to handle baseline traffic — The correct answer is A. With Vertex AI Prediction autoscaling, the `min_nodes` setting defines the baseline number of instances that are always kept running. During a flash sale, traffic spikes 10x, but if `min_nodes` is set too low, the autoscaler cannot provision new instances quickly enough to handle the sudden load, resulting in high latency. Increasing `min_nodes` ensures a sufficient baseline capacity to absorb the initial spike while the autoscaler scales up additional nodes.
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 has deployed a model with autoscaling configured as shown. They notice that during off-peak hours, the endpoint consistently runs 3 instances instead of scaling down to 1. What is the most likely cause?
medium
✓ A.There is a sustained request rate that prevents scaling down.
B.The `enableAccessLogging` flag increases resource usage.
C.The `minReplicaCount` is set too high.
D.The model is too large to fit on a single instance.
Why A: The autoscaling configuration is likely based on a target metric (e.g., requests per second or CPU utilization). During off-peak hours, if there is a sustained but low request rate that still exceeds the scale-down threshold, the model will not reduce instances below the number needed to handle that load. The endpoint runs 3 instances because the sustained request rate prevents the scaling-down logic from triggering, even though the traffic is lower than peak.
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.