PMLE Automating and Orchestrating ML Pipelines Practice Question
In a Vertex AI Pipeline, a component produces a Metrics artifact that includes an evaluation metric. The engineer wants to use this metric value as a condition to decide whether to deploy the model. However, the metric value is stored in the artifact's metadata and not directly as a pipeline parameter. How can the engineer pass the metric value to a downstream conditional task?
⚠ Common exam trap
A common trap in this Google exam is the misconception that artifact metadata can be directly used in pipeline conditions, but conditions require typed parameters, not artifact objects or their metadata fields.
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
✓
Add a component that reads the artifact's metadata and outputs the metric as a parameter, then use that parameter in the condition.
Vertex AI Pipeline conditions require pipeline parameters (typed values) to evaluate expressions like `dsl.If`. A Metrics artifact's metadata is stored as an artifact property, not a pipeline parameter, so a custom component must read that metadata and output the metric as a parameter. This parameter can then be used in the `dsl.If` condition to control downstream deployment.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure the component that produces the Metrics artifact to also output the metric as a pipeline parameter.
Why it's wrong here
Emitting the metric as a component output parameter is precisely the mechanism that makes the value available to dsl.If, so this option is not incorrect. It is the standard pattern: the component reads the metric from its Metrics artefact and returns it as a typed output parameter.
- ✗
Use the importer component to convert the artifact into a parameter.
Why it's wrong here
An importer component brings external artefacts into a pipeline; it does not extract a metadata value into a scalar pipeline parameter. It is tempting because importers do surface artefacts, but converting metadata to a parameter requires reading that value and emitting it as an output parameter.
- ✓
Add a component that reads the artifact's metadata and outputs the metric as a parameter, then use that parameter in the condition.
Why this is correct
Metrics stored in artifact metadata are not pipeline parameters, so dsl.If cannot consume them directly. A component that reads the artifact's metadata and emits the metric as an output parameter makes the value usable in the downstream condition, satisfying the stem's constraint.
- ✗
Use the artifact directly in the dsl.If condition, as artifacts are comparable.
Why it's wrong here
dsl.If conditions evaluate pipeline parameters, not artefact objects; artefacts are not comparable in the condition expression. Referencing an artefact directly fails because the condition compiler expects a scalar value, which is why the metric must first be surfaced as a parameter.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PMLE question from scratch — 775 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.