Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
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:
Which compliance period configuration and error budget strategy should the team implement?
A calendar compliance period binds SLO evaluation to fixed, non-overlapping calendar boundaries (such as a calendar day, week, or month). In this model, the error budget starts at its maximum value at the beginning of the period and diminishes as incidents occur until the period ends.
The organization required formal reporting tied directly to billing cycles or contractual SLAs evaluated strictly on monthly calendar intervals.
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%.
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.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.
This approach uses a calendar compliance period while treating individual request latency spikes as immediate overall SLO violations, bypassing statistical error budget aggregation.
The requirement was to configure a simple real-time metric threshold alert for immediate incident paging rather than designing an SLO compliance and error budget strategy.
A 100% Service Level Objective demands zero downtime or failed requests across the entire evaluation timeframe. Mathematically, the error budget is defined as 100% - SLO%.
0% (100% - 100% = 0), meaning the service has zero allowed downtime or failures. It does not provide an "unlimited" budget.There was a theoretical requirement that permitted zero errors under any circumstance, though in SRE practice 100% is never a recommended target.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated