- A
Keep using Cloud Composer but add retries with exponential backoff to the Dataflow task, and set up a Cloud Monitoring alert to notify the team if the task fails repeatedly
Why wrong: Retries do not solve schema changes; manual intervention still needed.
- B
Migrate to Vertex AI Pipelines and add a pre-processing step that validates incoming data schema against a schema registry; if schema change is detected, the pipeline sends an alert and uses a default schema to continue processing
This provides automated handling of schema changes.
- C
Use Cloud Scheduler to trigger the pipeline more frequently to reduce the impact of failures
Why wrong: Does not address the root cause; failures will still occur.
- D
Create a separate Dataflow pipeline to handle schema detection and run it before the main pipeline; if schema changes, send an email to the team
Why wrong: Still relies on manual intervention; not automated.
Quick Answer
The correct approach is to migrate to Vertex AI Pipelines and add a pre-processing step that validates incoming data against a schema registry, automatically applying a default schema when changes are detected. This solution directly addresses the need to automatically handle schema changes in ML pipelines by decoupling schema validation from downstream processing, ensuring the Dataflow job never stalls on unexpected fields. On the Google Professional Machine Learning Engineer exam, this scenario tests your understanding of Vertex AI Pipelines as a unified orchestration tool and the concept of schema drift detection—a common pitfall in production ML systems. A frequent trap is choosing a manual re-training or alert-only solution, which fails to eliminate downtime. Remember the mnemonic: **Validate, Default, Continue**—the pipeline checks the schema, falls back to a safe default, and keeps running without human intervention.
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 large financial company uses a complex ML pipeline to detect fraudulent transactions. The pipeline consists of multiple steps: data ingestion from Pub/Sub, feature engineering using Dataflow, model training with Vertex AI, and deployment to an endpoint. They currently use Cloud Composer to orchestrate the pipeline with separate DAGs for each step. Recently, they have been experiencing failures in the Dataflow job due to schema changes in the incoming transactions, causing the pipeline to stall. The team manually fixes the schema and re-runs the pipeline, which is time-consuming. They want to improve the robustness of the pipeline. The pipeline is run on a schedule but also triggered by the arrival of new data. The team is considering moving to Vertex AI Pipelines to unify the workflow. They also want to automatically detect schema changes and handle them without manual intervention. Which approach should they take?
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
Migrate to Vertex AI Pipelines and add a pre-processing step that validates incoming data schema against a schema registry; if schema change is detected, the pipeline sends an alert and uses a default schema to continue processing
Option B is correct because it directly addresses the need for automated schema change detection and handling within a unified orchestration framework. By migrating to Vertex AI Pipelines, the team gains a managed, end-to-end ML workflow service that can include a pre-processing step to validate incoming data against a schema registry. When a schema change is detected, the pipeline can automatically apply a default schema and continue, eliminating manual intervention and reducing downtime.
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.
- ✗
Keep using Cloud Composer but add retries with exponential backoff to the Dataflow task, and set up a Cloud Monitoring alert to notify the team if the task fails repeatedly
Why it's wrong here
Retries do not solve schema changes; manual intervention still needed.
- ✓
Migrate to Vertex AI Pipelines and add a pre-processing step that validates incoming data schema against a schema registry; if schema change is detected, the pipeline sends an alert and uses a default schema to continue processing
Why this is correct
This provides automated handling of schema changes.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use Cloud Scheduler to trigger the pipeline more frequently to reduce the impact of failures
Why it's wrong here
Does not address the root cause; failures will still occur.
- ✗
Create a separate Dataflow pipeline to handle schema detection and run it before the main pipeline; if schema changes, send an email to the team
Why it's wrong here
Still relies on manual intervention; not automated.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often think retries or alerts (Option A) are sufficient for handling failures, but the question explicitly requires automatic handling without manual intervention, which only a schema validation and fallback step can provide.
Detailed technical explanation
How to think about this question
Vertex AI Pipelines uses Kubeflow Pipelines or TFX under the hood, allowing you to define a DAG of components that can include custom Python code for schema validation using a schema registry (e.g., Avro or Protobuf schema store). The pre-processing step can compare the incoming data schema against a registered schema and, if a mismatch is detected, either transform the data to match the expected schema or use a fallback schema, all within the same pipeline execution. This approach avoids the operational overhead of managing separate DAGs in Cloud Composer and provides built-in retry, caching, and monitoring capabilities.
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 — study guide chapter
Learn the concepts, then practise the questions
- →
Automating and orchestrating ML pipelines practice questions
Targeted practice on this topic area only
- →
All PMLE questions
506 questions across all exam domains
- →
Google Professional Machine Learning Engineer study guide
Full concept coverage aligned to exam objectives
- →
PMLE practice test guide
How to use practice tests most effectively before exam day
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.
Scaling prototypes into ML models practice questions
Practise PMLE questions linked to Scaling prototypes into ML models.
Automating and orchestrating ML pipelines practice questions
Practise PMLE questions linked to Automating and orchestrating ML pipelines.
Collaborating within and across teams to manage data and models practice questions
Practise PMLE questions linked to Collaborating within and across teams to manage data and models.
Architecting low-code ML solutions practice questions
Practise PMLE questions linked to Architecting low-code ML solutions.
Collaborating to manage data and models practice questions
Practise PMLE questions linked to Collaborating to manage data and models.
Serving and scaling models practice questions
Practise PMLE questions linked to Serving and scaling models.
Monitoring ML solutions practice questions
Practise PMLE questions linked to Monitoring ML solutions.
Solving business challenges with ML practice questions
Practise PMLE questions linked to Solving business challenges with ML.
PMLE fundamentals practice questions
Practise PMLE questions linked to PMLE fundamentals.
PMLE scenario practice questions
Practise PMLE questions linked to PMLE scenario.
PMLE troubleshooting practice questions
Practise PMLE questions linked to PMLE troubleshooting.
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?
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: Migrate to Vertex AI Pipelines and add a pre-processing step that validates incoming data schema against a schema registry; if schema change is detected, the pipeline sends an alert and uses a default schema to continue processing — Option B is correct because it directly addresses the need for automated schema change detection and handling within a unified orchestration framework. By migrating to Vertex AI Pipelines, the team gains a managed, end-to-end ML workflow service that can include a pre-processing step to validate incoming data against a schema registry. When a schema change is detected, the pipeline can automatically apply a default schema and continue, eliminating manual intervention and reducing downtime.
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 →
Last reviewed: Jun 24, 2026
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.