Question 86 of 506
Scaling prototypes into ML modelshardMultiple ChoiceObjective-mapped

Quick Answer

The answer is implementing request batching to process multiple inputs per request. Batching reduces tail latency by amortizing the fixed overhead of model inference across several inputs, which smooths out the variability caused by variable-length text inputs that can create unpredictable compute spikes. On the Google Professional Machine Learning Engineer exam, this scenario tests your understanding that tail latency spikes often stem from per-request overhead rather than raw compute power, and a common trap is reaching for more resources like GPUs or memory when the real fix is architectural. Remember that for online predictions on Vertex AI, batching converts many small, erratic requests into fewer, more predictable batches, directly stabilizing the 99th percentile. A useful memory tip: think of batching as a “traffic jam smoother”—it merges individual cars into a steady bus route, eliminating the stop-and-go that causes the slowest riders to arrive late.

PMLE Scaling prototypes into ML models Practice Question

This PMLE practice question tests your understanding of scaling prototypes into ml models. 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 has successfully trained a deep learning model on Vertex AI using a custom container and distributed training with TensorFlow. They want to serve this model for online predictions with low latency. They deploy the model to Vertex AI Endpoint with a single n1-standard-4 machine. During load testing, they observe that the median latency is 200ms, but the 99th percentile latency spikes to 2 seconds. The model is a complex neural network that takes variable-length text as input. Which approach will best reduce tail latency while maintaining throughput?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "best"

    Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

Question 1hardmultiple choice
Full question →

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

Implement request batching to process multiple inputs per request.

Option C is correct because batching multiple requests together amortizes overhead and reduces per-request latency variability, particularly for variable-length inputs. Option A is wrong because increasing memory does not address compute-bound latency spikes. Option B is wrong because GPU might improve throughput but not necessarily reduce tail latency from variability. Option D is wrong because autoscaling adds replicas over time but does not reduce per-request latency spikes.

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.

  • Use autoscaling with a target CPU utilization of 70%.

    Why it's wrong here

    Autoscaling adds capacity over time, not reducing per-request latency spikes.

  • Implement request batching to process multiple inputs per request.

    Why this is correct

    Batching reduces overhead and smooths out latency for variable-length inputs.

    Clue confirmation

    The clue word "best" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use a GPU machine type like n1-standard-4 with an attached GPU.

    Why it's wrong here

    GPU may speed up inference but not specifically address tail latency from variable-length inputs.

  • Increase the machine type to n1-highmem-8 to allocate more memory.

    Why it's wrong here

    Memory is not the bottleneck; it's compute variability.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Detailed technical explanation

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

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.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • 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 PMLE exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.

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.

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?

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: Implement request batching to process multiple inputs per request. — Option C is correct because batching multiple requests together amortizes overhead and reduces per-request latency variability, particularly for variable-length inputs. Option A is wrong because increasing memory does not address compute-bound latency spikes. Option B is wrong because GPU might improve throughput but not necessarily reduce tail latency from variability. Option D is wrong because autoscaling adds replicas over time but does not reduce per-request latency spikes.

What should I do if I get this PMLE question wrong?

Identify which PMLE exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.

Are there clue words in this question I should notice?

Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more ways this is tested on PMLE

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 data science team has trained a custom model using Vertex AI and wants to deploy it for online predictions with low latency. Which TWO actions should they take to optimize performance?

medium
  • A.Use Vertex AI Endpoints with traffic splitting for canary deployments.
  • B.Enable autoscaling with a large min replicas count to handle bursts.
  • C.Optimize the model by quantizing to FP16.
  • D.Use a custom prediction routine with pre-processing inside the container.
  • E.Use a machine type with GPU for inference.

Why C: Option C is correct because quantizing the model to FP16 reduces its memory footprint and computational requirements, directly lowering inference latency on compatible hardware (e.g., NVIDIA GPUs with Tensor Cores). This optimization is especially effective for online predictions where response time is critical, as it accelerates matrix operations without significantly sacrificing model accuracy.

Keep practising

More PMLE practice questions

Last reviewed: Jun 24, 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.

Loading comments…

Sign in to join the discussion.

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.