easyMultiple SelectObjective-mapped
Best Practices for Building ML Pipelines on Vertex AI
Which TWO options are best practices for building ML pipelines on Vertex AI?
Quick Answer
The answer is leveraging Vertex ML Metadata to track artifact lineage and using custom container components for pipeline steps. These are best practices for building ML pipelines on Vertex AI because they ensure reproducibility and modularity: Vertex ML Metadata automatically records the inputs, outputs, and parameters of each pipeline run, creating a complete lineage graph that helps debug model drift and trace data transformations, while custom containers encapsulate dependencies and libraries, allowing each step to execute consistently regardless of the environment. On the Google Professional Machine Learning Engineer exam, this tests your understanding of MLOps fundamentals—specifically how to design pipelines that are auditable and maintainable at scale. A common trap is selecting manual logging or monolithic steps, which violate the principles of automation and separation of concerns. Memory tip: think “Metadata for memory, Containers for consistency.”
⚠ Common exam trap
Google Cloud often tests the misconception that serverless functions like Cloud Functions are suitable for ML pipeline steps, but the trap is that ML steps require persistent state, longer timeouts, and specialized hardware, which Cloud Functions cannot provide.
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 custom container components to encapsulate reusable logic
Custom container components allow you to encapsulate reusable logic with specific dependencies, libraries, and environments, enabling consistent execution across pipeline steps. This is a best practice for building modular, maintainable ML pipelines on Vertex AI, as it decouples step logic from the pipeline orchestration and supports versioning and testing.
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 Cloud Functions to execute individual pipeline steps
Why it's wrong here
Vertex AI Pipelines uses containers or managed components, not Cloud Functions.
- ✗
Hardcode pipeline parameters in the component definitions
Why it's wrong here
Parameters should be passed dynamically via PipelineJob.
- ✓
Use custom container components to encapsulate reusable logic
Why this is correct
Reusable components allow sharing across pipelines and reduce duplication.
- ✗
Always use the same compute environment for training and serving to ensure consistency
Why it's wrong here
Training often requires GPUs, serving may need different resources; consistency is achieved through container images.
- ✓
Leverage Vertex ML Metadata to track artifact lineage
Why this is correct
Lineage tracking helps in debugging and reproducibility.
Go deeper
Related to this question
About these practice questions
One of 990 original PMLE practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on PMLE
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An ML team is using Vertex AI Pipelines to automate model training and deployment. They want to reuse components across multiple pipelines. What is the best practice for managing component code?
medium- A.Define components inline in the pipeline definition
- B.Embed component code in Cloud Composer DAGs
- C.Copy the component definitions into each pipeline's YAML file
- D.Use Cloud Functions to define components
- ✓ E.Store components as container images in Artifact Registry and reference them from pipelines
Why E: Vertex AI Pipelines natively supports reusable components by packaging them as container images stored in Artifact Registry. This allows teams to version, share, and reference components across multiple pipelines without duplicating code, ensuring consistency and reducing maintenance overhead. Container images encapsulate the component's runtime environment and logic, making them portable and independently deployable.
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.