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!
Prepare and test your skills
Prepare and test your skills
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 is deploying a mission-critical e-commerce application on Google Cloud and needs to establish an observability strategy aligned with the Google Cloud Well-Architected Framework's operational excellence pillar.
The operations team wants to define Service Level Indicators (SLIs) and Service Level Objectives (SLOs) in Cloud Monitoring that measure user experience. The service experiences periodic bursts of high request volume where momentary latency spikes occur. Management wants to ensure that these short, transient spikes do not disproportionately exhaust the error budget, while still requiring that the service maintains acceptable performance over at least 95% of discrete 5-minute measurement intervals across a rolling 7-day period.
Which SLI and SLO configuration in Cloud Monitoring should you implement?
A windows-based Service Level Indicator (SLI) measures service quality by dividing the compliance period into discrete time intervals (windows) and determining whether each window satisfies a predefined goodness criterion. The overarching Service Level Objective (SLO) then specifies the target percentage of those windows that must meet the criterion over a defined compliance period.
A windows-based SLI directly fulfills the operational requirement of evaluating performance across discrete time windows over a rolling compliance period, insulating the error budget from extreme request volume fluctuations.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.