PCDOE Implementing service monitoring strategies Practice Question
You are monitoring a microservices application deployed on Google Kubernetes Engine (GKE) that uses Cloud Monitoring for observability. You notice that the error rate for a critical service has increased, but the CPU and memory usage remain normal. The service uses gRPC and logs are structured. Which Cloud Monitoring tool should you use first to diagnose the root cause of the increased error rate?
⚠ Common exam trap
Google Cloud often tests the distinction between monitoring (Metrics Explorer, dashboards) and logging (Logs Explorer) — the trap here is assuming that aggregated metrics or automated error grouping are the fastest path to root cause, when in fact direct log inspection is required to see the specific error details and status codes.
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
✓
Logs Explorer to filter logs by error status codes
Logs Explorer allows you to directly query structured gRPC logs by filtering on error status codes (e.g., gRPC status codes like `UNAVAILABLE`, `INTERNAL`, or `DEADLINE_EXCEEDED`). Since the service uses structured logging, you can quickly isolate the exact error messages and stack traces without needing to pre-configure dashboards or wait for automated grouping. This is the fastest first step to identify the root cause of an increased error rate when CPU and memory are normal, as it points to application-level or dependency issues.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Logs Explorer to filter logs by error status codes
Why this is correct
Logs Explorer allows you to examine structured logs, including gRPC status codes, to find error patterns.
- ✗
Service Monitoring to create a custom dashboard
Why it's wrong here
Service Monitoring focuses on SLOs and service-level dashboards, not log-level root cause analysis.
- ✗
Error Reporting to automatically group error occurrences
Why it's wrong here
Error Reporting summarizes errors but may not provide the granularity of gRPC status codes.
- ✗
Metrics Explorer to view error rate and latency charts
Why it's wrong here
Metrics Explorer shows aggregated metrics, not individual log entries needed for detailed error analysis.
Go deeper
Related to this question
About these practice questions
This PCDOE question is part of Courseiva's 486-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 PCDOE 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 PCDOE exam.