PMLE Automating and Orchestrating ML Pipelines Practice Question

An ML engineer is designing a Vertex AI pipeline that trains a model, evaluates it, and conditionally deploys it only if the evaluation metric meets a threshold. The pipeline must pass the evaluation metric from the evaluation component to a downstream conditional. Which Vertex AI Pipelines feature should the engineer use to implement this flow?

⚠ Common exam trap

The trap here is assuming that Vertex AI Experiments or Model Registry can directly control pipeline flow based on metrics, when in fact they are for tracking and storage, not runtime decision-making.

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 the output of the evaluation component as an input parameter to a condition in the pipeline definition, referencing the component's output parameter.

In Vertex AI Pipelines, component outputs can be promoted to pipeline parameters, which can then be used in conditions to control downstream execution. The evaluation component should output the metric as a parameter, and the condition compares it to the threshold. This maintains a single, traceable pipeline run and avoids external services.

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 the Vertex AI Model Registry to compare the new model's metric with the deployed model's metric and let the registry automatically deploy if better.
Why it's wrong here
The Vertex AI Model Registry does not automatically compare metrics and deploy models based on thresholds. It is a repository for model versions and metadata. Deployment decisions must be explicitly implemented, typically via a pipeline condition that evaluates the metric and then triggers a deployment component.
✗
Write the metric to a Cloud Storage file and use a Cloud Function to trigger a separate pipeline for deployment.
Why it's wrong here
Using a Cloud Function triggered by a file write adds unnecessary complexity and latency, and it breaks the pipeline's orchestration. The condition should be within the same pipeline to keep the workflow atomic and maintain lineage. This approach also requires managing permissions and error handling across services.
✓
Use the output of the evaluation component as an input parameter to a condition in the pipeline definition, referencing the component's output parameter.
Why this is correct
Vertex AI Pipelines allows a component to expose outputs as parameters that can be consumed by downstream conditions. The evaluation component can output a metric value as a pipeline parameter, and the condition can compare this value to a threshold. This is the standard way to implement conditional logic based on runtime values in a pipeline.
✗
Store the metric in a Vertex AI Experiment run and then use the Experiment's metric in the condition.
Why it's wrong here
Vertex AI Experiments track metrics for analysis, but they are not designed to feed runtime control flow within a pipeline. A condition in a pipeline cannot directly read an Experiment's metric at runtime. The metric must be passed as a pipeline parameter or artifact to be available for conditional evaluation.

Go deeper

PMLE Automating and Orchestrating ML Pipelines Practice Question

Why each option matters

Option-by-option breakdown

Related to this question