- A
Deploy a sidecar proxy in each pod to collect detailed latency data and export it to a third-party tool.
Why wrong: This adds unnecessary complexity and cost; Cloud Monitoring already supports custom metrics without third-party tools.
- B
Use Cloud Monitoring's 'Service Monitoring' to set up a service SLO and create a burn-rate alert.
Why wrong: Service Monitoring helps define and track SLOs, but it won't provide per-region granularity; it uses the same aggregated metrics.
- C
Use the GKE Dashboard to view per-pod latency metrics.
Why wrong: The GKE Dashboard shows pod-level metrics but not latency broken down by external user region; it cannot isolate the regional backend issue.
- D
Create a custom log-based metric that extracts latency per region from application logs.
Log-based metrics allow you to parse latency values and labels (e.g., region) from structured logs, providing per-region latency data to pinpoint the issue.
PCDOE Implementing service monitoring strategies Practice Question
This PCDOE practice question tests your understanding of implementing service monitoring strategies. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company runs a multi-region web application on Google Kubernetes Engine (GKE) using Cloud Load Balancing and Cloud Armor. They use Cloud Monitoring to track user-facing latency. Recently, they noticed that the p99 latency has increased from 200ms to 2s during peak hours, but only for users in the US region. The team suspects a specific backend service in us-central1 is causing the spike. They have set up a dashboard showing latency by region, but the latency metric is aggregated globally, not broken down by region. What should they do to pinpoint the issue?
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
Create a custom log-based metric that extracts latency per region from application logs.
Option D is correct because creating a custom log-based metric that extracts latency per region from application logs allows you to break down the globally aggregated latency metric into per-region slices. This directly addresses the need to isolate the us-central1 backend service's impact on p99 latency during US peak hours, without requiring additional infrastructure or third-party tools.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Deploy a sidecar proxy in each pod to collect detailed latency data and export it to a third-party tool.
Why it's wrong here
This adds unnecessary complexity and cost; Cloud Monitoring already supports custom metrics without third-party tools.
- ✗
Use Cloud Monitoring's 'Service Monitoring' to set up a service SLO and create a burn-rate alert.
Why it's wrong here
Service Monitoring helps define and track SLOs, but it won't provide per-region granularity; it uses the same aggregated metrics.
- ✗
Use the GKE Dashboard to view per-pod latency metrics.
Why it's wrong here
The GKE Dashboard shows pod-level metrics but not latency broken down by external user region; it cannot isolate the regional backend issue.
- ✓
Create a custom log-based metric that extracts latency per region from application logs.
Why this is correct
Log-based metrics allow you to parse latency values and labels (e.g., region) from structured logs, providing per-region latency data to pinpoint the issue.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may assume per-pod metrics (Option C) are sufficient for user-facing latency analysis, but GKE Dashboard metrics are infrastructure-focused and lack the regional breakdown needed to isolate a specific backend service's impact on global p99 latency.
Trap categories for this question
Command / output trap
The GKE Dashboard shows pod-level metrics but not latency broken down by external user region; it cannot isolate the regional backend issue.
Detailed technical explanation
How to think about this question
Log-based metrics in Cloud Monitoring work by parsing structured logs (e.g., JSON payloads) and extracting fields like latency and region using regular expressions or the logging query language. These metrics can then be sliced by the 'region' label in a Monitoring dashboard or alerting policy, enabling precise per-region latency analysis. In practice, this approach avoids the overhead of sidecar proxies and leverages existing application logs, which often already contain request latency and geographic metadata from Cloud Load Balancing headers like `X-Client-Geo-Location`.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Implementing service monitoring strategies — study guide chapter
Learn the concepts, then practise the questions
- →
Implementing service monitoring strategies practice questions
Targeted practice on this topic area only
- →
All PCDOE questions
500 questions across all exam domains
- →
Google Professional Cloud DevOps Engineer study guide
Full concept coverage aligned to exam objectives
- →
PCDOE practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PCDOE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Bootstrapping a Google Cloud organization for DevOps practice questions
Practise PCDOE questions linked to Bootstrapping a Google Cloud organization for DevOps.
Managing service incidents practice questions
Practise PCDOE questions linked to Managing service incidents.
Managing Google Cloud costs practice questions
Practise PCDOE questions linked to Managing Google Cloud costs.
Building and implementing CI/CD pipelines practice questions
Practise PCDOE questions linked to Building and implementing CI/CD pipelines.
Implementing service monitoring strategies practice questions
Practise PCDOE questions linked to Implementing service monitoring strategies.
Optimizing service performance practice questions
Practise PCDOE questions linked to Optimizing service performance.
PCDOE fundamentals practice questions
Practise PCDOE questions linked to PCDOE fundamentals.
PCDOE scenario practice questions
Practise PCDOE questions linked to PCDOE scenario.
PCDOE troubleshooting practice questions
Practise PCDOE questions linked to PCDOE troubleshooting.
Practice this exam
Start a free PCDOE practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this PCDOE question test?
Implementing service monitoring strategies — This question tests Implementing service monitoring strategies — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create a custom log-based metric that extracts latency per region from application logs. — Option D is correct because creating a custom log-based metric that extracts latency per region from application logs allows you to break down the globally aggregated latency metric into per-region slices. This directly addresses the need to isolate the us-central1 backend service's impact on p99 latency during US peak hours, without requiring additional infrastructure or third-party tools.
What should I do if I get this PCDOE question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 25, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.