The answer is that the alert policy is configured in a different project than the VM instances. This is correct because alert policies in Google Cloud are inherently project-scoped resources; a policy defined in one project cannot monitor metrics from resources in another project unless a cross-project metrics scope is explicitly set up. The MQL query in the policy references `compute.googleapis.com/instance/cpu/utilization`, which is only visible within the same project as the monitored VMs, so the policy remains blind to instances outside its own project. On the Google Professional Cloud Security Engineer exam, this tests your understanding of the fundamental boundary between project isolation and monitoring, often appearing as a trap where engineers assume alert policies are global. A common memory tip is to think of alert policies as having a “project passport”—they can only see metrics inside their own project’s borders unless you grant a visa via a metrics scope.
PCSE Practice Question: Managing operations in a cloud solution environment
This PCSE practice question tests your understanding of managing operations in a cloud solution environment. 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.
Exhibit
Refer to the exhibit.
```yaml
# monitoring alert policy
combiner: OR
conditions:
- conditionThreshold:
filter: resource.type="gce_instance" AND metric.type="compute.googleapis.com/instance/cpu/utilization"
aggregations:
- alignmentPeriod: 60s
perSeriesAligner: ALIGN_RATE
duration: 300s
comparison: COMPARISON_GT
thresholdValue: 0.8
trigger:
count: 1
displayName: CPU > 80%
- conditionMonitoringQueryLanguage:
query: |
fetch gce_instance
| metric 'compute.googleapis.com/instance/cpu/utilization'
| filter resource.zone == 'us-central1-a'
| group_by [resource.instance_id], 60s, [value_utilization_mean: mean(value.utilization)]
| every 60s
| condition value_utilization_mean > 0.9
duration: 0s
trigger:
count: 1
displayName: High average CPU per instance
documentation:
content: |
Alert when CPU is high.
mime_type: text/markdown
```
Refer to the exhibit. An operations engineer configured this alert policy to notify when any VM instance in project my-project has high CPU utilization. However, no notifications are received even when CPU is consistently above 90% on multiple instances in us-central1-a. What is the most likely cause?
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.
```yaml
# monitoring alert policy
combiner: OR
conditions:
- conditionThreshold:
filter: resource.type="gce_instance" AND metric.type="compute.googleapis.com/instance/cpu/utilization"
aggregations:
- alignmentPeriod: 60s
perSeriesAligner: ALIGN_RATE
duration: 300s
comparison: COMPARISON_GT
thresholdValue: 0.8
trigger:
count: 1
displayName: CPU > 80%
- conditionMonitoringQueryLanguage:
query: |
fetch gce_instance
| metric 'compute.googleapis.com/instance/cpu/utilization'
| filter resource.zone == 'us-central1-a'
| group_by [resource.instance_id], 60s, [value_utilization_mean: mean(value.utilization)]
| every 60s
| condition value_utilization_mean > 0.9
duration: 0s
trigger:
count: 1
displayName: High average CPU per instance
documentation:
content: |
Alert when CPU is high.
mime_type: text/markdown
```
A
The 'duration' of 0s in the MQL condition prevents the alert from firing because it needs a minimum duration.
Why wrong: Duration 0s means the condition triggers immediately upon violation; it is a valid setting.
B
The alert policy is configured in a different project than the VM instances.
If the alert policy is in project A but VM instances are in project B, the policy won't see those metrics unless cross-project access is set up.
C
The MQL query uses 'group_by' which causes the condition to be evaluated on the aggregate, but the threshold should be applied before grouping.
Why wrong: Grouping after filtering is valid; the condition is correctly evaluated on the mean of each instance's series.
D
The notification channel is not configured or is invalid.
Why wrong: While possible, the policy would still show as 'no notification channel' in the UI, but the question asks for most likely cause given the configuration shown; the exhibit does not show notification channels, so it could be a factor, but it's not tied to the exhibit.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The alert policy is configured in a different project than the VM instances.
Option B is correct because alert policies are project-scoped resources. If the VM instances reside in a different project than the one where the alert policy is defined, the policy cannot monitor those instances. The MQL query references the metric `compute.googleapis.com/instance/cpu/utilization` which is only visible within the same project as the monitored resources. Cross-project monitoring requires additional configuration such as a metrics scope or a separate alert policy in the target project.
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 'duration' of 0s in the MQL condition prevents the alert from firing because it needs a minimum duration.
Why it's wrong here
Duration 0s means the condition triggers immediately upon violation; it is a valid setting.
✓
The alert policy is configured in a different project than the VM instances.
Why this is correct
If the alert policy is in project A but VM instances are in project B, the policy won't see those metrics unless cross-project access is set up.
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 MQL query uses 'group_by' which causes the condition to be evaluated on the aggregate, but the threshold should be applied before grouping.
Why it's wrong here
Grouping after filtering is valid; the condition is correctly evaluated on the mean of each instance's series.
✗
The notification channel is not configured or is invalid.
Why it's wrong here
While possible, the policy would still show as 'no notification channel' in the UI, but the question asks for most likely cause given the configuration shown; the exhibit does not show notification channels, so it could be a factor, but it's not tied to the exhibit.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the subtle distinction between an alert that fails to fire (scope/resource mismatch) versus an alert that fires but fails to notify (channel issue), leading candidates to incorrectly blame the notification channel when the real problem is that the alert condition is never evaluated against the target resources.
Trap categories for this question
Command / output trap
While possible, the policy would still show as 'no notification channel' in the UI, but the question asks for most likely cause given the configuration shown; the exhibit does not show notification channels, so it could be a factor, but it's not tied to the exhibit.
Detailed technical explanation
How to think about this question
Under the hood, Google Cloud Monitoring uses a resource hierarchy where each metric time series is associated with a specific project. The MQL query in the alert policy implicitly scopes to the project containing the policy. To monitor resources across projects, you must use a metrics scope (formerly Stackdriver accounts) or create the alert policy in the same project as the VMs. A common real-world scenario is when an operations team centralizes alerting in a 'monitoring' project but forgets to add target projects to the metrics scope, causing silent failures.
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
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
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.
Managing operations in a cloud solution environment — This question tests Managing operations in a cloud solution environment — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The alert policy is configured in a different project than the VM instances. — Option B is correct because alert policies are project-scoped resources. If the VM instances reside in a different project than the one where the alert policy is defined, the policy cannot monitor those instances. The MQL query references the metric `compute.googleapis.com/instance/cpu/utilization` which is only visible within the same project as the monitored resources. Cross-project monitoring requires additional configuration such as a metrics scope or a separate alert policy in the target project.
What should I do if I get this PCSE 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 PCSE 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 PCSE 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.