Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
A DevOps team manages a high-traffic microservices application running on Google Cloud and connected via Cloud Service Mesh. The service has a defined 30-day rolling Service Level Objective (SLO) of 99.9% availability, leaving an error budget of 0.1%.
The team needs to design an automated error budget policy and alerting mechanism that achieves the following requirements:
Which strategy should the team implement?
Raw error monitoring tracks the absolute number of error events across individual compute instances rather than computing a proportional ratio of successful requests to total valid requests (the Good Service Level Indicator over Total Valid Events).
An organization had no automated monitoring systems, minimal traffic, and required strict manual human-in-the-loop executive sign-offs for compliance audits.
End-of-budget alerting evaluates cumulative SLO metrics over the entire compliance cycle (such as 30 days) and only fires notifications once the entire allowable downtime or bad request allotment (100% of the error budget) has been exhausted.
Used strictly for retrospective monthly compliance reporting or SLA penalty accounting, where real-time operational response is not expected.
Single-window static threshold alerting triggers alerts based on an instantaneous or short-window metric value exceeding a static percentage threshold (such as 0.1% error rate over a 5-minute duration), without accounting for the overall error budget consumption over the rolling compliance period.
A system operated with zero-tolerance strict downtime requirements where any momentary dip below 99.9% availability necessitated an emergency stop on all pipeline activities.
Multiwindow multi-burn-rate alerting is a Site Reliability Engineering (SRE) best practice that measures the rate of error budget consumption (burn rate) across multiple time horizons and short/long confirmation windows. A burn rate of 1 means the entire error budget will be consumed exactly over the SLO period (e.g., 30 days). Higher burn rates (such as 14.4x consuming 2% of budget in 1 hour, or 6x consuming 5% in 6 hours) represent urgent, rapid degradation that requires immediate intervention, while lower burn rates (such as 1x to 2x over several days) represent slow degradation.
This approach solves the trade-off between alert precision and recall while providing an actionable, organizational framework to maintain service stability without stalling long-term velocity.
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