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.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
An e-commerce organization hosts its core transaction service on Google Cloud. The business has committed to an external Service Level Agreement (SLA) that guarantees 99.5% monthly availability to enterprise customers, backed by financial penalties for non-compliance.
To ensure architectural compliance and proactively mitigate outages before violating the legal agreement, the cloud architecture team needs to establish a reliability monitoring strategy in Google Cloud Monitoring.
Which approach should the architect implement?
Create a log-based metric with high-cardinality user session ID labels, define an SLO matching the 99.5% SLA, and configure an alerting policy that triggers whenever raw 5xx error counts exceed a static threshold of zero.
Configure a request-based availability SLI using a GAUGE metric kind, set the SLO target exactly equal to the 99.5% SLA, and configure a static threshold alert when CPU utilization exceeds 80%.
Configure a request-based availability SLI calculating the ratio of successful responses to total responses, set an internal SLO target stricter than the SLA (such as 99.9%) over a rolling period, and configure an alerting policy based on error budget burn rate.
Deploy private uptime checks targeting internal IP addresses via Service Directory, configure an SLO target of 99.5%, and configure notification channels for email and PagerDuty when an uptime check fails.
Create a log-based metric with high-cardinality user session ID labels, define an SLO matching the 99.5% SLA, and configure an alerting policy that triggers whenever raw 5xx error counts exceed a static threshold of zero.
Configure a request-based availability SLI using a GAUGE metric kind, set the SLO target exactly equal to the 99.5% SLA, and configure a static threshold alert when CPU utilization exceeds 80%.
Configure a request-based availability SLI calculating the ratio of successful responses to total responses, set an internal SLO target stricter than the SLA (such as 99.9%) over a rolling period, and configure an alerting policy based on error budget burn rate.
Google Cloud Monitoring provides native service monitoring constructs to measure and track application reliability. A Service Level Indicator (SLI) measures service performance (such as the ratio of successful HTTP requests to total requests), while a Service Level Objective (SLO) specifies the target reliability level over a defined compliance period. The error budget represents the allowable fraction of failures (1 - SLO) before the objective is breached.
StudyCerts
StudyCertsDELTA or CUMULATIVE metric kind to evaluate the precise ratio of successful responses (e.g., HTTP 2xx/3xx/4xx vs. 5xx) across all incoming requests.Deploy private uptime checks targeting internal IP addresses via Service Directory, configure an SLO target of 99.5%, and configure notification channels for email and PagerDuty when an uptime check fails.