Question 373 of 506
Serving and scaling modelshardMultiple SelectObjective-mapped

Quick Answer

The answer is to quantize the model to INT8, implement dynamic batching, and optimize the custom container’s inference pipeline. Quantizing to INT8 reduces the computational load per token, directly lowering the processing time for each request and smoothing out latency spikes. Dynamic batching groups multiple inference requests into a single forward pass, maximizing GPU utilization and amortizing overhead, which is especially effective for LLMs because it reduces the per-request variance that creates tail latency. On the Google Professional Machine Learning Engineer exam, this question tests your understanding of latency optimization trade-offs: the common trap is to focus only on hardware scaling (like adding more GPUs) rather than algorithmic and batching strategies. A key memory tip is “Quantize, Batch, Optimize” — remember that reducing precision, grouping requests, and tuning the serving stack are the three pillars for cutting tail latency on Vertex AI.

PMLE Serving and scaling models Practice Question

This PMLE practice question tests your understanding of serving and scaling 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 is serving a large language model (LLM) on Vertex AI using a custom container. They want to reduce tail latency. Which THREE strategies should they consider?

Question 1hardmulti select
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

Use dynamic batching to combine requests.

Dynamic batching (B) reduces tail latency by grouping multiple inference requests into a single batch, which improves GPU utilization and amortizes overhead across requests. This is particularly effective for LLMs because it allows the model to process more tokens per forward pass, reducing the per-request latency variance that contributes to tail latency.

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.

  • Increase the number of replicas.

    Why it's wrong here

    Helps with throughput, not tail latency.

  • Use dynamic batching to combine requests.

    Why this is correct

    Improves GPU utilization and reduces per-request latency.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Implement response caching for common queries.

    Why this is correct

    Avoids inference for repeated requests.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Quantize the model to INT8 to reduce computation.

    Why this is correct

    Reduces latency per request.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Upgrade to a more powerful GPU type.

    Why it's wrong here

    May reduce overall latency but not specifically tail.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse scaling strategies (like increasing replicas or upgrading hardware) with latency-optimization techniques, failing to recognize that tail latency is primarily reduced by batching and caching, not by adding more compute resources.

Detailed technical explanation

How to think about this question

Dynamic batching works by queuing incoming requests and waiting for a configurable timeout (e.g., 100ms) or a maximum batch size (e.g., 32 sequences) before sending them to the GPU. Under the hood, this leverages CUDA's ability to parallelize matrix operations across batch dimensions, and frameworks like TensorFlow Serving or vLLM implement this with a scheduler that balances latency and throughput. In real-world scenarios, tail latency spikes often occur when a single large request blocks smaller ones; batching smooths this by ensuring all requests share the same forward pass.

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.

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?

Serving and scaling models — This question tests Serving and scaling models — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Use dynamic batching to combine requests. — Dynamic batching (B) reduces tail latency by grouping multiple inference requests into a single batch, which improves GPU utilization and amortizes overhead across requests. This is particularly effective for LLMs because it allows the model to process more tokens per forward pass, reducing the per-request latency variance that contributes to tail latency.

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 →

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. Your team has deployed a PyTorch model using a custom container on Vertex AI Prediction. The model uses dynamic batching to combine incoming requests. You notice that the average latency is 150 ms, but the 99th percentile latency is 2 seconds. Cloud Monitoring shows that the CPU is idle much of the time, and GPU utilization is around 70%. The model is deployed on a single n1-standard-4 with a T4 GPU. You suspect the issue is related to request queuing. Which change would most effectively reduce tail latency?

hard
  • A.Add a second replica to share the load.
  • B.Increase the batch timeout to allow larger batches to form, reducing the number of batches.
  • C.Decrease the batch size to reduce processing time per batch.
  • D.Implement a priority queue to handle high-priority requests first.

Why A: Option C is correct because adding a replica reduces the queue length per replica, thus reducing waiting time for requests. Option A might increase tail latency if timeout is too long. Option B could reduce processing time but not queuing delay. Option D adds complexity and doesn't address root cause.

Keep practising

More PMLE practice questions

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