The correct choice is to use a custom ParDo transform in Dataflow that calls the Vertex AI Prediction API directly. This approach is optimal because it allows each Dataflow worker to invoke the prediction endpoint synchronously, keeping data in-memory and processing predictions inline without the latency of writing to intermediate storage or triggering external services. On the Google Professional Machine Learning Engineer exam, this scenario tests your understanding of how to integrate ML inference into streaming or batch pipelines while minimizing overhead—a common trap is selecting an asynchronous pattern like Pub/Sub or Cloud Functions, which adds unnecessary delay. Remember the key principle: for low-latency, inline predictions, a synchronous ParDo call to Vertex AI is the direct path, avoiding detours. Memory tip: "ParDo predicts in place, no storage chase."
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.
A data-processing pipeline using Dataflow needs to incorporate a custom ML prediction step. The team wants to maintain fast processing and minimize latency. What is the optimal approach?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "minimum / minimize"
Why it matters: Asks for the least resource use — fewest addresses, smallest subnet, lowest overhead. Eliminate over-provisioned options even if they would technically work.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a custom ParDo transform in Dataflow that calls Vertex AI Prediction API directly
Option B is correct because using a custom ParDo transform in Dataflow allows the pipeline to call the Vertex AI Prediction API synchronously within each worker, avoiding the overhead of external triggers, intermediate storage, or asynchronous messaging. This keeps the data in-memory and minimizes latency by processing predictions inline with the Dataflow streaming or batch pipeline.
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.
✗
Write the data to Cloud Storage, trigger a Cloud Function to call the model, and write results back
Why it's wrong here
This adds latency and extra components.
✓
Use a custom ParDo transform in Dataflow that calls Vertex AI Prediction API directly
Why this is correct
Inline calls within Dataflow are efficient and keep the pipeline linear.
Clue confirmation
The clue word "minimum / minimize" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Send data to a Pub/Sub topic and have a separate subscriber that runs predictions
Why it's wrong here
Adds complexity and latency; DoFn is simpler.
✗
Stream data through Cloud Functions that serve predictions and write to BigQuery
Why it's wrong here
Cloud Functions have time and concurrency limits, not ideal for streaming.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that adding external services like Cloud Functions or Pub/Sub improves modularity without considering the latency penalty, leading candidates to choose options that introduce unnecessary hops instead of keeping prediction inline within the Dataflow pipeline.
Detailed technical explanation
How to think about this question
Under the hood, a custom ParDo transform in Dataflow runs within the Apache Beam SDK, allowing direct gRPC calls to the Vertex AI Prediction endpoint from each worker. This approach leverages Dataflow's autoscaling and fusion optimization, so prediction calls are batched or parallelized based on the pipeline's parallelism, and the results can be immediately used in downstream transforms without serialization to external services. In real-world scenarios, this is critical for real-time fraud detection where sub-second latency is required, as it avoids the 100-500ms overhead of Cloud Function cold starts or Pub/Sub publish-subscribe delays.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
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: Use a custom ParDo transform in Dataflow that calls Vertex AI Prediction API directly — Option B is correct because using a custom ParDo transform in Dataflow allows the pipeline to call the Vertex AI Prediction API synchronously within each worker, avoiding the overhead of external triggers, intermediate storage, or asynchronous messaging. This keeps the data in-memory and minimizes latency by processing predictions inline with the Dataflow streaming or batch pipeline.
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: "minimum / minimize". Asks for the least resource use — fewest addresses, smallest subnet, lowest overhead. Eliminate over-provisioned options even if they would technically work.
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.