Google PCA Ensure solution and operations reliability Practice Question
A company wants to monitor their Cloud Run services for errors and latency. Which Google Cloud product should they use?
⚠ Common exam trap
It's easy for candidates to confuse Cloud Trace (for latency) or Error Reporting (for errors) as standalone solutions, but the question asks for a single product that monitors both errors and latency, which is Cloud Monitoring's role as the central metrics and alerting platform.
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 Monitoring
Cloud Monitoring (formerly Stackdriver Monitoring) provides comprehensive observability for Cloud Run services, including built-in dashboards for request latency, error rates, and resource utilization. It collects metrics like request count, request latencies, and container instance counts, and allows you to set alerting policies based on these metrics. While Cloud Trace can help with latency analysis and Cloud Logging captures logs, Cloud Monitoring is the primary product for monitoring both errors and latency in a unified view.
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
Why it's wrong here
Cloud Trace records distributed request traces and span timings, but it does not aggregate error rates into alertable metrics. It is tempting because latency analysis is its purpose; it would be correct if the stem asked to diagnose slow requests across microservices rather than monitor errors and latency.
- ✓
Cloud Monitoring
Why this is correct
Cloud Monitoring natively ingests Cloud Run request metrics, error rates and latency percentiles, letting the company alert on them without custom instrumentation. It satisfies the stated requirement to monitor errors and latency across their services, unlike logging-only or CI/CD tools.
- ✗
Cloud Logging
Why it's wrong here
Cloud Logging stores and queries log entries, but latency is captured as metrics, not log lines, so it cannot report request duration. It is tempting because Cloud Run errors do appear in logs; it would be correct if the requirement were log retention or forensic searching.
- ✗
Error Reporting
Why it's wrong here
Error Reporting aggregates and groups application exceptions, but it does not record request latency, so the latency half of the requirement goes unmet. It is tempting because it genuinely surfaces Cloud Run error counts; it would be the right pick if the stem asked only about error visibility.
Go deeper
Related to this question
Learn chapter
Google Cloud Resource Hierarchy and Organization
Key term
Cloud logging
Cloud logging is the practice of collecting, storing, and analyzing log data generated by cloud-based resources and applications to monitor performance, troubleshoot issues, and maintain security.
Key term
Container instance
A container instance is a running software package created from a container image that includes its own code, runtime, and dependencies, isolated from the host system.
About these practice questions
This PCA question is part of Courseiva's 807-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 PCA 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 PCA exam.