The answer is request latency percentiles (e.g., p99) and container CPU utilization. Request latency percentiles are the gold standard for detecting performance degradation because they directly measure end-user experience, revealing subtle slowdowns that resource metrics might miss. Container CPU utilization, on the other hand, is a direct indicator of resource pressure and capacity issues; high utilization can cause throttling, increased latency, and pod evictions, making it essential for capacity planning. On the Google Professional Cloud DevOps Engineer exam, this pairing tests your understanding that comprehensive monitoring must cover both user-facing signals (latency) and infrastructure health (CPU). A common trap is to focus only on resource metrics like memory or disk I/O, but the exam emphasizes that latency percentiles catch degradation before saturation occurs. Memory tip: “Latency for the user, CPU for the node”—if you track both, you’ll catch slowdowns and capacity crunches before they cascade.
PCDOE Implementing service monitoring strategies Practice Question
This PCDOE practice question tests your understanding of implementing service monitoring strategies. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. 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.
Which TWO metrics should be included in a comprehensive monitoring strategy for a production Kubernetes workload to detect performance degradation and capacity issues?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Container CPU utilization
Container CPU utilization (Option B) is a direct indicator of resource pressure and potential performance degradation in a Kubernetes workload. High CPU utilization can lead to throttling, increased request latency, and pod evictions, making it essential for detecting capacity issues. Request latency percentiles (Option E) are the gold standard for measuring user-facing performance degradation, as they reflect the actual experience of end users and can reveal subtle slowdowns before resource metrics show saturation.
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.
✗
Disk read IOPS per pod
Why it's wrong here
Disk IOPS is important for stateful workloads but not a general performance indicator for all workloads.
✓
Container CPU utilization
Why this is correct
High CPU utilization can indicate capacity pressure and performance issues.
Related concept
Read the scenario before looking for a memorised answer.
✗
Number of nodes in the cluster
Why it's wrong here
Node count is an infrastructure metric; it doesn't directly measure workload performance.
✗
Network bytes received per second
Why it's wrong here
Network throughput is not a direct measure of performance degradation; it may vary with traffic.
✓
Request latency percentiles (e.g., p99)
Why this is correct
Latency percentiles directly reflect user experience and performance degradation.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the distinction between infrastructure-level metrics (like node count or network bytes) and application-level metrics (like latency percentiles) that directly measure user experience and workload health.
Detailed technical explanation
How to think about this question
In Kubernetes, CPU utilization is measured via cgroups and reported by kubelet through the metrics API; the 'container_cpu_usage_seconds_total' metric from cAdvisor is used to calculate utilization percentages. Request latency percentiles, especially p99, are typically collected via service mesh sidecars (e.g., Envoy in Istio) or application instrumentation with OpenTelemetry, and they directly reflect tail latency which is critical for SLOs. A real-world scenario: a pod may show 80% CPU utilization but still serve requests within SLOs, while a sudden p99 spike to 2 seconds indicates a problem even if CPU is only at 50%.
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 healthcare organisation deploys an application with a public-facing web tier and a private database tier. The database subnet has no public IP and only accepts connections from the web tier's security group. Questions like this test whether you can design cloud network isolation using VNets/VPCs, subnets, and security group rules.
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 — 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: Container CPU utilization — Container CPU utilization (Option B) is a direct indicator of resource pressure and potential performance degradation in a Kubernetes workload. High CPU utilization can lead to throttling, increased request latency, and pod evictions, making it essential for detecting capacity issues. Request latency percentiles (Option E) are the gold standard for measuring user-facing performance degradation, as they reflect the actual experience of end users and can reveal subtle slowdowns before resource metrics show saturation.
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 →
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.
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.