- A
Configure the component that produces the Metrics artifact to also output the metric as a pipeline parameter.
Why wrong: While possible, it's not always feasible to modify existing components. The extraction approach is more general.
- B
Use the importer component to convert the artifact into a parameter.
Why wrong: Importer is for importing artifacts, not for extracting metadata as parameters.
- C
Add a component that reads the artifact's metadata and outputs the metric as a parameter, then use that parameter in the condition.
A small Python function component can extract the metric value from the artifact's metadata and output it as a string or float parameter, which can then be used in dsl.If.
- D
Use the artifact directly in the dsl.If condition, as artifacts are comparable.
Why wrong: Artifacts are not directly comparable in dsl.If; conditions require pipeline parameters.
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.
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?
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.
Option C is correct because 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.
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.
- ✗
Configure the component that produces the Metrics artifact to also output the metric as a pipeline parameter.
Why it's wrong here
While possible, it's not always feasible to modify existing components. The extraction approach is more general.
- ✗
Use the importer component to convert the artifact into a parameter.
Why it's wrong here
Importer is for importing artifacts, not for extracting metadata as parameters.
- ✓
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
A small Python function component can extract the metric value from the artifact's metadata and output it as a string or float parameter, which can then be used in dsl.If.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use the artifact directly in the dsl.If condition, as artifacts are comparable.
Why it's wrong here
Artifacts are not directly comparable in dsl.If; conditions require pipeline parameters.
Common exam traps
Common exam trap: answer the scenario, not the keyword
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.
Detailed technical explanation
How to think about this question
Under the hood, Vertex AI Pipeline artifacts are stored as instances of the `Artifact` class with a `metadata` dictionary. To use a metric value in a condition, you must explicitly extract it via a component that accesses `artifact.metadata['metric_name']` and returns it as a `pipeline_param` of type `float` or `str`. This pattern is essential when using pre-built components (e.g., from Google Cloud's official pipeline components) that output only artifacts without exposing the metric as a parameter.
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
1,000 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.
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.
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.
Architecting Low-Code ML Solutions practice questions
Practise PMLE questions linked to Architecting Low-Code ML Solutions.
Scaling Prototypes into ML Models practice questions
Practise PMLE questions linked to Scaling Prototypes into ML Models.
Collaborating to manage data and models practice questions
Practise PMLE questions linked to Collaborating to manage data and models.
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: Add a component that reads the artifact's metadata and outputs the metric as a parameter, then use that parameter in the condition. — Option C is correct because 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.
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: Jul 4, 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.