hardMultiple Choice
PMLE Practice Question: Has multiple ML pipelines running on Vertex AI
An organization has multiple ML pipelines running on Vertex AI. They want to centralize monitoring and alerting for pipeline failures, including root cause analysis. Which combination of services should they use?
⚠ Common exam trap
A common mix-up: candidates confuse Cloud Trace and Cloud Debugger (debugging tools) with the monitoring and logging services needed for failure detection and root cause analysis, or mistakenly think Cloud Audit Logs (compliance logs) are sufficient for pipeline error monitoring.
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
✓
Cloud Logging + Cloud Monitoring + Error Reporting
Cloud Logging captures pipeline execution logs, Cloud Monitoring provides metrics and alerting on pipeline failures, and Error Reporting aggregates and analyzes errors with stack traces for root cause analysis. Together, they form a centralized observability stack that meets the requirement for monitoring, alerting, and root cause analysis of ML pipeline failures on Vertex AI.
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 Trace + Cloud Debugger
Why it's wrong here
Cloud Trace profiles request latency and Cloud Debugger inspects running application state; neither aggregates Vertex AI pipeline failure events nor performs root cause analysis across pipeline steps. They suit debugging latency in live web services, not centralised pipeline failure monitoring, which Vertex AI Pipelines' own logging and Cloud Logging-based alerting provide.
- ✓
Cloud Logging + Cloud Monitoring + Error Reporting
Why this is correct
Cloud Logging captures pipeline and component logs, Cloud Monitoring surfaces metrics and fires alerts on failures, and Error Reporting aggregates and groups exceptions for root cause analysis. Together they satisfy the centralised monitoring, alerting and diagnosis constraint across multiple Vertex AI pipelines.
- ✗
Cloud Operations for GKE + Stackdriver
Why it's wrong here
Cloud Operations for GKE monitors Kubernetes clusters, and Stackdriver is the retired former name for Google Cloud's operations suite, so neither centralises Vertex AI pipeline failure monitoring or root cause analysis. It is tempting for infrastructure telemetry, but Vertex AI Pipelines requires its own metadata and logging integration.
- ✗
Cloud Audit Logs + Cloud Functions
Why it's wrong here
Cloud Audit Logs record administrative API activity, not pipeline step execution failures or their causes, so Cloud Functions reacting to them cannot perform root cause analysis. This pairing suits detecting configuration or permission changes, whereas pipeline failure monitoring requires Vertex AI Pipelines' execution logs and metrics surfaced through Cloud Monitoring.
Go deeper
Related to this question
About these practice questions
This PMLE question is part of Courseiva's 775-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 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.