The answer is to use Vertex AI ML Metadata to track and retrieve model artifacts. This is the correct artifact management strategy because ML Metadata stores a lineage graph of all pipeline artifacts—models, datasets, and metrics—allowing you to query and reuse a specific model version by ID or custom properties without retraining. On the Google Professional Machine Learning Engineer exam, this question tests your understanding of how to avoid redundant compute costs by leveraging Vertex AI’s native metadata service rather than manually saving model files to Cloud Storage or using a custom registry. A common trap is choosing Vertex AI Model Registry, which is for model deployment and versioning, not for artifact retrieval across pipeline runs. Remember the memory tip: “Metadata for reuse, Registry for release”—if you need to reuse a trained model without retraining, think ML Metadata’s lineage graph, not the deployment registry.
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.
An ML engineer is using Vertex AI Pipelines and wants to reuse a trained model across multiple pipeline runs without retraining each time. Which artifact management strategy should be used?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Vertex AI ML Metadata to track and retrieve model artifacts
Vertex AI ML Metadata is the correct artifact management strategy because it is purpose-built for tracking and retrieving model artifacts across pipeline runs. It stores metadata about models, datasets, and other artifacts in a lineage graph, enabling you to query and reuse a specific model version without retraining. This integrates natively with Vertex AI Pipelines, allowing you to pass model artifacts between components and retrieve them by ID or custom properties.
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.
✗
Store the model in BigQuery as a ML model
Why it's wrong here
BigQuery ML models are for BigQuery, not for arbitrary model artifacts.
✗
Use Cloud Functions to cache the model
Why it's wrong here
Cloud Functions is not designed for artifact storage.
✗
Save the model to a Cloud Storage bucket and reference by path
Why it's wrong here
This works but without metadata tracking, it's hard to manage versions and dependencies; ML Metadata is recommended.
✓
Use Vertex AI ML Metadata to track and retrieve model artifacts
Why this is correct
ML Metadata provides lineage and artifact tracking, enabling efficient reuse across pipelines.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that simply saving a model to Cloud Storage (Option C) is sufficient for artifact management, but the trap is that it ignores the need for metadata tracking, version lineage, and automated retrieval—features that Vertex AI ML Metadata provides as a managed service.
Detailed technical explanation
How to think about this question
Vertex AI ML Metadata uses the ML Metadata (MLMD) library under the hood, which stores artifact and execution records in a scalable database (e.g., Cloud SQL or Spanner). Each model artifact is registered with a unique ID, type (e.g., 'google.VertexModel'), and custom properties, enabling precise retrieval via the MetadataStore API. In a real-world scenario, a pipeline component can produce a model artifact, and a downstream component can query ML Metadata for the latest model with a specific evaluation metric, ensuring reproducibility without hardcoding storage paths.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
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 — 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: Use Vertex AI ML Metadata to track and retrieve model artifacts — Vertex AI ML Metadata is the correct artifact management strategy because it is purpose-built for tracking and retrieving model artifacts across pipeline runs. It stores metadata about models, datasets, and other artifacts in a lineage graph, enabling you to query and reuse a specific model version without retraining. This integrates natively with Vertex AI Pipelines, allowing you to pass model artifacts between components and retrieve them by ID or custom properties.
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 →
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.
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.