PMLE Practice Question: Collaborating Within and Across Teams to Manage Data and Models
A team uses Vertex AI Metadata to track pipeline runs. They need to identify all artifacts that were generated by a particular pipeline execution. Which API method should they use?
⚠ Common exam trap
PMLE often tests the assumption that artifacts can be filtered directly by execution ID — candidates pick the 'filter artifacts' option because it sounds precise, missing that Vertex AI Metadata expresses execution-artifact relationships through lineage events, not a direct foreign key.
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 the lineage query API with the execution ID
The Vertex AI Metadata lineage query API accepts an execution ID and returns all artifacts, contexts, and events connected to that execution, giving the full provenance graph in one call. This is the purpose-built method for tracing which artifacts a pipeline run produced.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
List executions and then list artifacts separately
Why it's wrong here
Listing executions and artifacts separately yields two unlinked collections; nothing associates a given artifact with the execution that produced it. This suits inventory browsing or auditing counts of runs and artifacts, not answering which artifacts a particular execution generated.
- ✓
Use the lineage query API with the execution ID
Why this is correct
The lineage query API accepts an execution ID and returns the subgraph of artifacts produced by that execution, directly answering which artifacts a given pipeline run generated. Listing executions alone returns run metadata without the produced artifact relationships.
- ✗
Create a context and query executions
Why it's wrong here
Creating a context groups related executions for lineage grouping, but it does not return the artifacts generated by one specific execution. Contexts suit organising multiple runs under a shared logical container, such as comparing experiments, not resolving a single execution's output artifacts.
- ✗
Query artifacts by filter on execution ID
Why it's wrong here
Filtering artifacts by execution ID returns artifacts directly linked to that run, but the stem asks which API method identifies them, and querying artifacts presupposes already knowing the execution ID rather than deriving the relationship. It suits ad-hoc metadata searches across lineage, not traversing from an execution to its generated artifacts.
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.