Google Professional Cloud DevOps Engineer Question 145
Select 3Google Cloud PlatformYour team is managing a web application hosted on Google Cloud, and you have defined an SLO for the application's availability to be 99.9% over a 30-day period. You want to configure an alerting policy to notify the team when the error budget is exhausted by 50%, but only if this condition persists for at least 15 minutes. What steps should you take to create this alerting policy in Google Cloud Monitoring?
- A
Set the condition to monitor the SLI for availability and define the threshold as exceeding 50% of the error budget.
- B
Set a time window of 15 minutes for the condition to ensure the threshold is exceeded consistently over that period.
- C
Define a notification channel, such as email or PagerDuty, to send alerts when the condition is met.
- D
Configure the alerting policy to automatically delete itself after the error budget resets.
- E
Create a condition to monitor SLO compliance instead of availability to track the error budget.
Show answer and explanation
Correct answers: A, B, C
Explanation
To configure an alerting policy based on error budget consumption, you must monitor the relevant SLI (availability in this case) and set a threshold for exceeding the error budget. A time window ensures the condition persists before triggering an alert, and a notification channel is required to inform the team. Configuring the policy to delete itself or monitoring SLO compliance directly does not align with the scenario's requirements.
- A. Correct.
Correct: Monitoring the SLI for availability and setting the threshold for exceeding 50% of the error budget will ensure the alert triggers when the defined threshold is breached.
- B. Correct.
Correct: A 15-minute time window ensures that transient spikes do not trigger alerts prematurely and aligns with your requirement for persistence.
- C. Correct.
Correct: A notification channel is necessary to inform the team when the condition is met.
- D. Incorrect.
Incorrect: Alerting policies are not configured to delete themselves automatically. They are designed to remain active until manually updated or removed.
- E. Incorrect.
Incorrect: Monitoring SLO compliance directly would not allow precise tracking of the error budget depletion. Monitoring the SLI for availability is appropriate for this use case.