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 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.
A request-based SLI evaluates performance by directly calculating the ratio of successful (or low-latency) requests to the total number of valid requests received across the entire evaluation timeframe.
The business requirement dictated that every single transaction must count equally toward the error budget without grouping transactions into time slices or insulating against high-volume burst anomalies.
A log-based metric extracts numerical values or counts matching log entries from Cloud Logging, and a static threshold alert fires whenever the metric value crosses a designated ceiling for a set duration.
You needed to detect specific application-level error codes logged to stdout/stderr in real time and trigger immediate automated incident remediation.
Cloud Monitoring uptime checks test the availability of a public or private endpoint by sending synthetic requests from distributed geographic locations at periodic intervals (e.g., every 1, 5, or 15 minutes).
The primary goal was black-box perimeter monitoring to verify whether an external URL endpoint is reachable from multiple regions worldwide.
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