An enterprise e-commerce organization is designing a Site Reliability Engineering (SRE) monitoring and deployment strategy for its checkout service in Google Cloud Observability. The operations team has established a 99.9% availability Service Level Objective (SLO). The team needs to meet the following operational requirements: Continuously evaluate compliance and error budget availability on an ongoing basis rather than waiting for a fixed month-end evaluation Make daily, data-driven decisions on whether to deploy risky new features or freeze non-critical releases based on the remaining error budget Which compliance period configuration and error budget strategy should the team implement?

Configure a rolling compliance period (such as 30 days) and halt risky feature deployments when the error budget approaches depletion: ### What a rolling compliance period and error budget are A **rolling compliance period** is a continuous sliding time window (for example, the trailing 30 days) used to evaluate **Service Level Indicators (SLIs)** against a **Service Level Objective (SLO)**. The **error budget** represents the total allowable non-compliance or failure margin during that window, calculated as `100% - SLO%`. ### How it meets the requirements - **Continuous evaluation**: In a rolling window, older data points continuously roll out of the calculation as new performance data arrives. This allows the system to provide daily, real-time measurements of compliance for the preceding 30-day window rather than waiting for calendar month boundaries. - **Data-driven release governance**: Tracking error budget depletion enables the engineering team to manage release risk. When the error budget is near zero or exhausted (`error budget < 0`), non-critical feature releases are halted to prioritize stability and remediation. When sufficient error budget remains, teams can safely push new feature updates. ### Key advantages and capabilities - **Dynamic health tracking**: Eliminates the latency of fixed calendar cycles by recalculating service health daily. - **Objective risk management**: Balances innovation velocity and service reliability using quantitative metrics. - **Automatic budget recovery**: As historical incidents age past the 30-day sliding window, the available error budget naturally recovers if current performance remains compliant. ### Why this is optimal A rolling compliance period aligns directly with real-time operational needs, giving development and operations teams an up-to-date assessment of user experience every day to govern deployment velocity.

StudyCerts

Sre Slo Rolling Compliance Period Error Budget | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Sre Slo Rolling Compliance Period Error Budget

Section: Monitoring and logging

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An enterprise e-commerce organization is designing a Site Reliability Engineering (SRE) monitoring and deployment strategy for its checkout service in Google Cloud Observability. The operations team has established a 99.9% availability Service Level Objective (SLO).

The team needs to meet the following operational requirements:

Continuously evaluate compliance and error budget availability on an ongoing basis rather than waiting for a fixed month-end evaluation
Make daily, data-driven decisions on whether to deploy risky new features or freeze non-critical releases based on the remaining error budget

Which compliance period configuration and error budget strategy should the team implement?

Configure a calendar compliance period and trigger an immediate SLO violation whenever single-request latency exceeds the target threshold

Configure a 100% availability SLO with a rolling compliance period so that the error budget remains unlimited across all deployment windows

Configure a rolling compliance period (such as 30 days) and halt risky feature deployments when the error budget approaches depletion

Configure a calendar compliance period (such as monthly) and reset the error budget manually every day to allow continuous feature deployments

Professional Cloud Architect

Sre Slo Rolling Compliance Period Error Budget

Related questions