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 runs a business-critical order processing microservice on Google Cloud. The Site Reliability Engineering (SRE) team has established a 30-day rolling Service Level Objective (SLO) target of 99.9% availability based on a Service Level Indicator (SLI) measuring successful requests.
During an aggressive deployment cycle, custom Cloud Monitoring dashboards indicate that 90% of the 30-day error budget was consumed in just 4 days due to transient server errors and latency spikes.
According to SRE best practices, how should the team use these SLI/SLO metrics to guide their upcoming operational and development decisions?
Host-level monitoring measures infrastructure resource consumption, such as hypervisor CPU utilization, RAM usage, and disk I/O, rather than end-user service quality.
The team were conducting low-level VM instance sizing or debugging a suspected hypervisor hardware fault rather than evaluating overall service reliability and release governance.
A windowed SLI evaluates the percentage of discrete time windows (e.g., 1-minute or 5-minute intervals) that meet a specified goodness criterion. Resetting the compliance period wipes out historical measurement data.
The service's usage pattern transitioned from uniform traffic to periodic batch processing where time-windowed availability provides a more accurate reflection of operational health.
Lowering the SLO target alters the agreed-upon reliability goal to artificially make the current unreliability appear acceptable within reporting tools.
Business stakeholders and end users formally agreed that the service had been over-engineered and that a lower reliability threshold was acceptable to reduce operational costs.
SLOs should remain stable across rolling windows to accurately evaluate trends; changing them reactively defeats the purpose of SRE governance.
An error budget represents the acceptable level of unreliability a service can experience over a defined compliance period (such as 100% - 99.9% = 0.1% allowable failure over 30 days). In Site Reliability Engineering (SRE), the error budget functions as an objective, shared control mechanism that balances feature velocity with system reliability.
When an application burns through 90% of its monthly error budget in only 4 days, continuing standard deployments introduces unacceptable risk of violating contractual Service Level Agreements (SLAs) and degrading customer experience. Redirecting engineering focus addresses the situation by:

Using the error budget burn rate to throttle releases and prioritize operational excellence directly adheres to Google Cloud and SRE best practices, ensuring long-term service health without arbitrarily blocking innovation when budgets are healthy.
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