easyMultiple Choice
PDE Practice Question: A team is using Kubeflow Pipelines on Google…
A team is using Kubeflow Pipelines on Google Kubernetes Engine to orchestrate ML workflows. They need to track parameters, metrics, and artifacts for each run. Which tool should they integrate?
⚠ Common exam trap
Google Cloud often tests the distinction between general-purpose monitoring/logging tools and ML-specific metadata stores, so the trap here is that candidates may confuse Cloud Monitoring or Cloud Logging with a tool that can track ML metrics, when in fact they lack the structured schema and lineage capabilities required for ML workflow orchestration.
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
✓
Vertex ML Metadata
Vertex ML Metadata is the correct choice because it is purpose-built for tracking parameters, metrics, and artifacts in ML workflows, and it integrates natively with Kubeflow Pipelines on Google Kubernetes Engine. It stores metadata for each pipeline run, enabling lineage tracking, comparison, and reproducibility of experiments.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Cloud Monitoring
Why it's wrong here
Cloud Monitoring records time-series metrics for infrastructure and services, but cannot track parameters or artifacts per pipeline run. It is tempting because it visualises metrics, and it would be correct for alerting on resource utilisation or serving latency across deployed endpoints.
- ✗
Cloud Logging
Why it's wrong here
Cloud Logging captures text log entries, not structured parameters, metrics or artifact lineage tied to a run. It is tempting because pipeline pods emit logs, and it would be correct for debugging container output or retaining execution logs for troubleshooting.
- ✗
BigQuery
Why it's wrong here
BigQuery stores and queries tabular data; it has no native concept of Kubeflow run parameters, metrics or artifacts, so lineage is lost. It is tempting because pipelines can write results there, and it would be correct for large-scale analytical queries over exported experiment data.
- ✓
Vertex ML Metadata
Why this is correct
Vertex ML Metadata provides a managed store for tracking parameters, metrics and artifacts per pipeline run, integrating with Kubeflow Pipelines on GKE. It satisfies the lineage requirement without self-hosting a metadata database, unlike plain GCS logging or TensorBoard alone.
Go deeper
Related to this question
About these practice questions
This PDE question is part of Courseiva's 747-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PDE 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 PDE exam.