PMLE Automating and Orchestrating ML Pipelines Practice Question

An ML engineer is using Vertex AI Pipelines to orchestrate a workflow that includes a custom component for data validation. The component takes a dataset URI and outputs a validation report. The engineer wants to fail the pipeline immediately if the validation report indicates that the data is invalid, without running subsequent steps. How should the engineer implement this?

⚠ Common exam trap

The trap here is thinking that a conditional step or an external monitor is needed to stop the pipeline, when simply failing the component achieves the goal.

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

✓

Have the data validation component raise an exception if the data is invalid, causing the task to fail and the pipeline to stop.

The most effective way to fail the pipeline immediately upon invalid data is to have the data validation component raise an exception. This causes the task to fail, and Vertex AI Pipelines will not run any downstream tasks that depend on its output. The pipeline will be marked as failed, which can trigger alerts. This approach is simple, reliable, and leverages the native failure handling of the pipeline orchestrator.

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 a conditional step after validation that checks the report and only proceeds if valid, otherwise skips subsequent steps.
Why it's wrong here
A conditional step can branch based on the report, but it would not fail the pipeline; it would simply skip the remaining steps. The pipeline would still be marked as successful, which might not trigger alerts. The requirement is to fail the pipeline immediately, so raising an exception is more appropriate than conditional skipping.
✓
Have the data validation component raise an exception if the data is invalid, causing the task to fail and the pipeline to stop.
Why this is correct
If the data validation component raises an exception when data is invalid, the task fails, and Vertex AI Pipelines will not execute downstream steps that depend on its output. This is the simplest and most direct way to halt the pipeline upon validation failure. The pipeline status will reflect the failure, allowing for alerting and debugging.
✗
Write the validation result to a Cloud Storage bucket and use a Cloud Function to monitor the bucket and cancel the pipeline if invalid.
Why it's wrong here
Using a Cloud Function to monitor and cancel the pipeline introduces external dependencies and latency. It is an over-engineered solution. The pipeline itself can handle failure internally by having the component fail. This avoids additional infrastructure and keeps the logic within the pipeline, making it easier to maintain and debug.
✗
Configure the pipeline to use a 'fail_fast' execution option that stops the pipeline if any component outputs a failure status.
Why it's wrong here
Vertex AI Pipelines does not have a 'fail_fast' execution option. Pipeline execution already stops downstream tasks if a task fails. However, the validation component must indicate failure, typically by raising an exception. There is no separate 'fail_fast' setting to enable; it's the default behavior for failed tasks.

Go deeper

PMLE Automating and Orchestrating ML Pipelines Practice Question

Why each option matters

Option-by-option breakdown

Related to this question