PMLE Automating and Orchestrating ML Pipelines Practice Question
An ML engineer has a Vertex AI pipeline that trains a model and then evaluates it. The engineer wants the pipeline to deploy the model to an endpoint only if the evaluation metric exceeds a threshold defined at pipeline submission time. The threshold must be changeable without recompiling the pipeline. Which mechanism should the engineer use?
⚠ Common exam trap
A common mix-up: candidates confuse a dsl.Condition on a component output with a condition on a runtime parameter, when only the latter allows the threshold to change without recompiling.
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
✓
Define the threshold as a pipeline input parameter and use a dsl.Condition on that parameter to gate the deployment component.
Vertex AI Pipelines distinguishes compile-time structure from runtime parameters. Making the threshold a pipeline input parameter allows it to be supplied at submission time without recompiling, and dsl.Condition on that parameter creates the deployment gate. The other options either bake the threshold into the pipeline definition, misuse Model Registry aliases, or rely on an unsupported environment variable mechanism that the compiler cannot see.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set the threshold as an environment variable in the pipeline's service account and read it inside the deployment component.
Why it's wrong here
Environment variables on a service account are not a supported mechanism for passing pipeline parameters, and reading them inside a component makes the value invisible to the pipeline compiler. The dsl.Condition would not be able to reference the threshold, so the deployment gate could not be expressed declaratively.
- ✗
Hardcode the threshold in the evaluation component and use a dsl.Condition on the evaluation component's output.
Why it's wrong here
Hardcoding the threshold in the evaluation component means changing it requires editing and recompiling the pipeline, which violates the requirement that the threshold be changeable without recompiling. A dsl.Condition on the evaluation output is fine for branching, but the threshold value itself must be a runtime parameter, not a constant.
- ✓
Define the threshold as a pipeline input parameter and use a dsl.Condition on that parameter to gate the deployment component.
Why this is correct
A pipeline input parameter is part of the pipeline's runtime interface, so the threshold can be supplied at submission time without recompiling. Wrapping the deployment component in dsl.Condition on that parameter creates the conditional gate. This is exactly the pattern Vertex AI Pipelines supports for runtime-configurable branching.
- ✗
Use a Vertex AI Model Registry alias and configure the endpoint to only serve models whose alias matches the threshold value.
Why it's wrong here
Model Registry aliases identify model versions, not evaluation thresholds, and endpoints do not natively gate serving on an alias matching a numeric threshold. This conflates model versioning with deployment gating and would not implement the metric-based condition the engineer needs.
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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Google Cloud exam blueprint
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.