Alerting policies in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Alerting Policy Behavior

You have created an alerting policy in Google Cloud Monitoring that triggers when CPU usage exceeds 80% for 5 minutes. What will happen if the CPU usage spikes to 85% for 3 minutes and then drops back to 50%?

A The alert will not trigger because the CPU usage did not exceed 80% for the full 5 minutes.

B The alert will trigger after the CPU usage drops back below 80%.

C The alert will trigger immediately when CPU usage hits 85%.

D The alert will trigger only if CPU usage stays above 90% for 5 minutes.

💡 Hint

Think about how the duration condition affects alert triggering.

The alerting policy requires CPU usage to be above 80% continuously for 5 minutes. Since the spike lasted only 3 minutes, the alert does not trigger.

❓ Configuration

intermediate

Correct Configuration of Notification Channels

You want to receive email notifications when an alerting policy triggers. Which configuration step is necessary to ensure emails are sent?

A Create a Pub/Sub topic and subscribe your email to it.

B Add your email address as a notification channel and link it to the alerting policy.

C Enable Stackdriver Logging to forward alerts to your email.

D Set up a Cloud Function to send emails when alerts occur.

💡 Hint

Consider the built-in ways Google Cloud Monitoring sends notifications.

Notification channels like email must be added and linked to alerting policies to receive alerts directly.

❓ Architecture

advanced

Designing a Multi-Region Alerting Strategy

You manage a multi-region application and want to create alerting policies that notify you only if an issue affects more than one region simultaneously. Which approach best achieves this?

A Create separate alerting policies per region and combine notifications manually.

B Set up alerting policies per region and configure a Cloud Function to check if multiple alerts are active before sending notifications.

C Use a single alerting policy with a metric that aggregates data across all regions and triggers only if multiple regions report issues.

D Configure alerting policies with a short duration threshold to catch issues quickly in each region.

💡 Hint

Think about how to aggregate metrics across regions for alerting.

A single alerting policy using aggregated metrics can detect multi-region issues and trigger alerts accordingly.

❓ security

advanced

Securing Alerting Policies Access

Which IAM role should you assign to a team member who needs to create and edit alerting policies but should not have permission to delete notification channels?

A Monitoring Editor (roles/monitoring.editor)

B Project Owner (roles/owner)

C Monitoring Viewer (roles/monitoring.viewer)

D Monitoring Admin (roles/monitoring.admin)

💡 Hint

Consider the permissions included in each role.

The Monitoring Editor role allows creating and editing alerting policies but does not grant permission to delete notification channels, which is reserved for Admin or Owner roles.

✅ Best Practice

expert

Optimizing Alerting Policies to Reduce Noise

You notice your team receives too many alert notifications for transient issues that resolve quickly. Which configuration change best reduces alert noise without missing critical incidents?

A Disable alerting policies during off-hours to avoid unnecessary alerts.

B Lower the threshold to catch issues earlier and resolve them faster.

C Remove all notification channels except email to reduce alert volume.

D Increase the alerting policy's condition duration to require the issue to persist longer before triggering.

💡 Hint

Think about how alert duration affects alert triggering.

Increasing the condition duration ensures alerts trigger only for sustained issues, reducing noise from brief spikes.