- A
Check if the nodes in that zone have been cordoned.
Why wrong: Cordoning would prevent pod scheduling, but app is still serving, so unlikely.
- B
Check if the application's resource requests and limits have changed.
Why wrong: Resource requests affect scheduling, not metric collection.
- C
Check if the Kubernetes Metrics Server is running correctly in that zone.
Metrics Server is responsible for collecting resource usage; if it's down, CPU data would drop.
- D
Check if the Cloud Monitoring agent has been updated incorrectly.
Why wrong: GKE uses Metrics Server, not an agent, for resource metrics.
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.
Your company runs a multi-region application on Google Kubernetes Engine. You have implemented Cloud Monitoring dashboards to track cluster resource utilization and application SLIs. After a recent upgrade, you notice that the dashboard shows a sudden drop in CPU utilization for all nodes in one zone, but the application is still serving traffic normally. You suspect a monitoring issue. What should you investigate first?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"first"Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
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
Check if the Kubernetes Metrics Server is running correctly in that zone.
The Kubernetes Metrics Server is responsible for collecting resource metrics from Kubelets and exposing them via the Metrics API, which Cloud Monitoring uses to display CPU utilization. A sudden drop in CPU utilization across all nodes in a single zone, while the application continues to serve traffic normally, strongly indicates that the Metrics Server in that zone has failed or is not reporting metrics, rather than an actual change in workload. Investigating the Metrics Server's health and logs is the correct first step to confirm whether the monitoring pipeline is broken.
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.
- ✗
Check if the nodes in that zone have been cordoned.
Why it's wrong here
Cordoning would prevent pod scheduling, but app is still serving, so unlikely.
- ✗
Check if the application's resource requests and limits have changed.
Why it's wrong here
Resource requests affect scheduling, not metric collection.
- ✓
Check if the Kubernetes Metrics Server is running correctly in that zone.
Why this is correct
Metrics Server is responsible for collecting resource usage; if it's down, CPU data would drop.
Clue confirmation
The clue word "first" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Check if the Cloud Monitoring agent has been updated incorrectly.
Why it's wrong here
GKE uses Metrics Server, not an agent, for resource metrics.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that Cloud Monitoring relies on an external agent for all metrics, when in fact GKE integrates natively with the Metrics Server for node and pod resource utilization, making agent-related options a red herring.
Detailed technical explanation
How to think about this question
The Metrics Server uses the Kubelet's Summary API (port 10250) to scrape resource usage every 60 seconds by default, then aggregates and serves these metrics via the metrics.k8s.io API. If the Metrics Server pod is unhealthy, misconfigured, or has network issues in a specific zone, the Cloud Monitoring dashboard will show a drop or absence of CPU utilization data for that zone's nodes, even though the application continues to run normally. A common subtle behavior is that the Metrics Server may fail silently if its TLS certificate or RBAC permissions are misconfigured after a cluster upgrade, leading to a gap in monitoring data without any obvious application impact.
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: Check if the Kubernetes Metrics Server is running correctly in that zone. — The Kubernetes Metrics Server is responsible for collecting resource metrics from Kubelets and exposing them via the Metrics API, which Cloud Monitoring uses to display CPU utilization. A sudden drop in CPU utilization across all nodes in a single zone, while the application continues to serve traffic normally, strongly indicates that the Metrics Server in that zone has failed or is not reporting metrics, rather than an actual change in workload. Investigating the Metrics Server's health and logs is the correct first step to confirm whether the monitoring pipeline is broken.
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.
Are there clue words in this question I should notice?
Yes — watch for: "first". Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
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 30, 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.