The answer is that a data validation step in the pipeline modified the SavedModel’s serving signature, adding an extra preprocessing operation. This is the most likely cause of the Vertex AI endpoint latency increase because the additional operation runs during every inference request on the endpoint, inflating latency from 50ms to 200ms even though the model architecture, container image, and machine type (n1-standard-4) remain unchanged. On the Google Professional Machine Learning Engineer exam, this scenario tests your understanding that a serving signature change—not model size or hardware—can silently degrade real-time performance, a common trap when debugging deployment pipelines. Remember that Vertex AI endpoints execute the entire serving graph defined in the SavedModel; any new node, even a simple validation or transformation, adds per-request overhead. Memory tip: “Signature shift slows the lift”—if the serving signature changes, expect latency to drift.
PMLE Automating and orchestrating ML pipelines Practice Question
This PMLE practice question tests your understanding of automating and orchestrating ml pipelines. 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.
You are an ML engineer at a large e-commerce company. Your team has developed a product recommendation model using TensorFlow and deployed it on Vertex AI Endpoints for real-time inference. The model is retrained weekly using a Vertex AI Pipeline that reads new user interaction data from BigQuery, trains the model, evaluates it, and deploys the new version to the endpoint with a traffic split: 10% to the new model and 90% to the previous champion model. Recently, the team noticed that the new model's online prediction latency has increased significantly (from 50ms to 200ms) after deployment, causing timeouts for some requests. The training code has not changed, and the model size is similar. The pipeline uses a custom container with the same TensorFlow Serving image as before. The deployment step uses the same machine type (n1-standard-4) for the endpoint. What is the most likely cause of the latency increase?
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 pipeline now includes a data validation step that modifies the SavedModel's serving signature, adding an extra preprocessing operation.
Option C is correct because the pipeline now includes a data validation step that modifies the SavedModel's serving signature, adding an extra preprocessing operation. This additional operation runs during inference on Vertex AI Endpoints, increasing the per-request latency from 50ms to 200ms, even though the model architecture and size remain unchanged. The custom container and machine type are identical, so the latency increase must stem from a change in the serving graph itself.
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 endpoint is using a machine type that is not optimized for the new model's computation.
Why it's wrong here
The machine type is the same as before.
✗
The new model has a significantly different architecture that requires more computation.
Why it's wrong here
The training code hasn't changed, so architecture is likely similar.
✓
The pipeline now includes a data validation step that modifies the SavedModel's serving signature, adding an extra preprocessing operation.
Why this is correct
A data validation step might have inadvertently added preprocessing ops, increasing latency.
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.
✗
The new model is experiencing data skew because the training data distribution has changed.
Why it's wrong here
Data skew affects model accuracy, not latency.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the concept that changes in the ML pipeline (like adding a data validation step) can alter the serving signature and increase latency, even when the model architecture and infrastructure remain unchanged, tricking candidates into focusing on hardware or data distribution instead.
Trap categories for this question
Similar concept trap
The training code hasn't changed, so architecture is likely similar.
Detailed technical explanation
How to think about this question
When a Vertex AI Pipeline step modifies the SavedModel's serving signature (e.g., by adding a tf.function for data validation or preprocessing), that operation is serialized into the model's graph and executed on every prediction request. This can introduce overhead such as additional TensorFlow ops, input validation loops, or feature transformations that were not present in the original model. In real-world scenarios, such signature modifications are often overlooked because the model file size remains similar, but the computational graph becomes more complex, leading to unexpected latency spikes.
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.
Automating and orchestrating ML pipelines — This question tests Automating and orchestrating ML pipelines — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The pipeline now includes a data validation step that modifies the SavedModel's serving signature, adding an extra preprocessing operation. — Option C is correct because the pipeline now includes a data validation step that modifies the SavedModel's serving signature, adding an extra preprocessing operation. This additional operation runs during inference on Vertex AI Endpoints, increasing the per-request latency from 50ms to 200ms, even though the model architecture and size remain unchanged. The custom container and machine type are identical, so the latency increase must stem from a change in the serving graph itself.
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 →
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.