The answer is the crossSeriesReducer set to REDUCE_SUM, which aggregates CPU across all containers in a namespace, causing false positives. This occurs because the sum of individual container utilization can exceed the 80% threshold even when no single container is overloaded—for example, five containers each at 20% sum to 100%, triggering the alert. On the Google Professional Cloud DevOps Engineer exam, this scenario tests your understanding of how aggregation functions in alert policies can distort signal interpretation; a common trap is assuming REDUCE_SUM measures per-container usage rather than total namespace usage. Remember the memory tip: “Sum the team, not the player”—if you want per-container alerts, use REDUCE_MEAN or REDUCE_NONE instead.
PCDOE Optimizing service performance Practice Question
This PCDOE practice question tests your understanding of optimizing service performance. 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.
Exhibit
Refer to the exhibit.
Cloud Monitoring alert policy (YAML):
```yaml
alertPolicy:
displayName: 'High CPU Utilization'
combiner: OR
conditions:
- displayName: 'CPU utilization > 80% for 5 min'
conditionThreshold:
filter: 'metric.type="kubernetes.io/container/cpu/usage_time" AND resource.type="k8s_container" AND resource.labels.cluster_name="prod-cluster"'
aggregations:
- alignmentPeriod: 60s
perSeriesAligner: ALIGN_RATE
- crossSeriesReducer: REDUCE_SUM
groupByFields:
- resource.label.namespace_name
- resource.label.container_name
- conditionThreshold:
thresholdValue: 0.8
duration: 300s
comparison: COMPARISON_GT
notificationChannels:
- 'projects/my-project/notificationChannels/12345'
```
You created the above alert policy to detect high CPU utilization in your GKE cluster. However, you are receiving too many false positive alerts. What is the most likely reason?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Refer to the exhibit.
Cloud Monitoring alert policy (YAML):
```yaml
alertPolicy:
displayName: 'High CPU Utilization'
combiner: OR
conditions:
- displayName: 'CPU utilization > 80% for 5 min'
conditionThreshold:
filter: 'metric.type="kubernetes.io/container/cpu/usage_time" AND resource.type="k8s_container" AND resource.labels.cluster_name="prod-cluster"'
aggregations:
- alignmentPeriod: 60s
perSeriesAligner: ALIGN_RATE
- crossSeriesReducer: REDUCE_SUM
groupByFields:
- resource.label.namespace_name
- resource.label.container_name
- conditionThreshold:
thresholdValue: 0.8
duration: 300s
comparison: COMPARISON_GT
notificationChannels:
- 'projects/my-project/notificationChannels/12345'
```
A
The threshold value of 0.8 is too low; it should be 0.9 for production.
Why wrong: 0.8 corresponds to 80% of a single core, which is a reasonable threshold. False positives are caused by sum aggregation, not threshold value.
B
The crossSeriesReducer is set to REDUCE_SUM, which sums CPU across containers, so a namespace with many containers can trigger the alert even if each container uses less than 80%.
REDUCE_SUM adds up CPU usage of all containers in the namespace/container group. This can exceed 0.8 when many containers are active, even if each is below 80%. Using REDUCE_MAX per container would be more appropriate.
C
The duration of 300 seconds (5 minutes) is too short; it should be longer to avoid transient spikes.
Why wrong: 5 minutes is standard for sustained high CPU. The aggregation is the main issue.
D
The filter does not specify a specific namespace, causing alerts from all namespaces.
Why wrong: The filter does not limit namespace, but the groupBy includes namespace, so alerts are per namespace. The issue is not about namespace scope.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The crossSeriesReducer is set to REDUCE_SUM, which sums CPU across containers, so a namespace with many containers can trigger the alert even if each container uses less than 80%.
Option B is correct because the crossSeriesReducer set to REDUCE_SUM aggregates CPU utilization across all containers in a namespace. This means that even if each container uses only 20% CPU, a namespace with five containers would show a total of 100%, triggering the alert when the threshold is 0.8 (80%). This causes false positives because the alert fires on the sum, not on individual container utilization.
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.
✗
The threshold value of 0.8 is too low; it should be 0.9 for production.
Why it's wrong here
0.8 corresponds to 80% of a single core, which is a reasonable threshold. False positives are caused by sum aggregation, not threshold value.
✓
The crossSeriesReducer is set to REDUCE_SUM, which sums CPU across containers, so a namespace with many containers can trigger the alert even if each container uses less than 80%.
Why this is correct
REDUCE_SUM adds up CPU usage of all containers in the namespace/container group. This can exceed 0.8 when many containers are active, even if each is below 80%. Using REDUCE_MAX per container would be more appropriate.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The duration of 300 seconds (5 minutes) is too short; it should be longer to avoid transient spikes.
Why it's wrong here
5 minutes is standard for sustained high CPU. The aggregation is the main issue.
✗
The filter does not specify a specific namespace, causing alerts from all namespaces.
Why it's wrong here
The filter does not limit namespace, but the groupBy includes namespace, so alerts are per namespace. The issue is not about namespace scope.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that false positives are caused by thresholds being too low or durations too short, when the real issue is an incorrect aggregation reducer that sums metrics across multiple resources.
Detailed technical explanation
How to think about this question
In Cloud Monitoring, the crossSeriesReducer controls how multiple time series (e.g., per-container CPU) are combined. REDUCE_SUM adds them together, which is useful for total resource usage but misleading for per-container thresholds. A better approach is to use REDUCE_MAX to alert when any single container exceeds 80%, or to use a per-series threshold with a group-by on container labels. In real-world scenarios, this misconfiguration often occurs when monitoring microservices with many replicas, where the sum of low individual usage falsely indicates a problem.
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.
Optimizing service performance — This question tests Optimizing service performance — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The crossSeriesReducer is set to REDUCE_SUM, which sums CPU across containers, so a namespace with many containers can trigger the alert even if each container uses less than 80%. — Option B is correct because the crossSeriesReducer set to REDUCE_SUM aggregates CPU utilization across all containers in a namespace. This means that even if each container uses only 20% CPU, a namespace with five containers would show a total of 100%, triggering the alert when the threshold is 0.8 (80%). This causes false positives because the alert fires on the sum, not on individual container utilization.
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: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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.