GCP Professional Cloud Architect Practice Question

A retail enterprise is formalizing its non-functional requirements before rolling out a new set of micro-services across multiple regions. One proposal defines reliability as "the fraction of time the service is reachable from at least one region." Several architects object that this definition is incomplete. Based on guidance from the Google Cloud Well-Architected Framework, which alternative wording most accurately expresses the core concept of reliability so it can be used as the foundation for service-level objectives (SLOs)?

The ability of a system to perform its required functions under stated conditions for a specified period.
The percentage of time the service returns successful responses within 200 milliseconds.
The capacity of a system to scale out automatically whenever utilization exceeds 70 percent.
The guarantee that data will never be lost even if multiple zones fail.

Report Issue

Answer Description

Within the Google Cloud Well-Architected Framework, reliability is defined as the ability of a system to perform its required functions under stated conditions for a specified period. This wording highlights three key aspects that an SLO must capture: (1) correct functioning (the service does what users expect), (2) within declared operating conditions (such as load, dependencies, or infrastructure health), and (3) over a defined time window. Merely stating that the service is reachable describes availability, not full reliability. Focusing on data survival describes durability, and focusing on scaling or latency describes performance or elasticity. Therefore, the only option that aligns with the framework's definition of reliability is the statement that emphasizes sustained ability to meet functional requirements under specified conditions for a period of time.

Ask Bash

Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.