Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An e-commerce company runs a checkout service on Google Cloud and is establishing a site reliability engineering (SRE) framework to evaluate service performance. The engineering team defines the following operational parameters for the service:
Which cloud operations term describes the Internal Target defined by the engineering team?
A Service Level Agreement (SLA) is a formal, legally binding contract between a service provider and its customers that guarantees a minimum level of service performance or availability. An SLA explicitly outlines the consequences—such as financial refunds, fee reductions, or service credits—if the provider fails to meet the promised threshold.
99.5% latency compliance) used by the engineering team, whereas an SLA is an external commitment negotiated with clients.99.0%) than internal SLOs (such as 99.5% or 99.98%) to create a safety buffer for engineering teams.5% monthly service fee credit for every 0.1% drop below minimum guaranteed availability.The question asked which cloud operations term describes the Customer Commitment parameter—the legally binding contract guaranteeing 99.0% monthly availability backed by financial service credits.
Organizations use SLOs to protect their SLAs. By setting a stricter internal SLO (99.5%), the engineering team receives early alerts and can resolve performance degradation well before the looser contractual SLA (99.0%) is breached.
A Service Level Objective (SLO) is a precise, measurable internal target for service reliability evaluated over a defined period of time. An SLO combines a Service Level Indicator (SLI) with a specific performance goal (such as 99.5%) and a compliance period (such as a rolling 30-day window or a calendar week) to define what qualifies as acceptable service performance.
99.5% of checkout requests must complete within 300 milliseconds directly establishes the desired level of performance (SLI ≥ lower_bound).99.5% internal target vs. 99.0% contractual guarantee), alerts on SLO compliance warn engineers to remediate issues before customer agreements are violated.100% − SLO), quantifying the exact amount of unreliability a service can tolerate before feature launches should be paused.Unlike an SLI (which only measures raw performance) or an SLA (which governs external legal and financial penalties), an SLO is specifically designed as an internal operational target that empowers engineering teams to manage service reliability proactively.
A Service Level Indicator (SLI) is a quantitative measurement of a specific aspect of service performance and reliability. Rather than representing a goal or threshold, an SLI provides the raw telemetry ratio—ranging from 0% to 100%—that shows how a system is actually behaving at any given moment or over a specific time window.
99.5% over a 30-day window.99.5% is acceptable or unacceptable performance for the engineering team.200 responses under 300 ms) to the total number of valid events.The question asked which cloud operations term describes the Measurement parameter—specifically, the quantitative ratio of checkout requests completed in under 300 milliseconds compared to total valid requests.
In Google Cloud's reliability hierarchy, the SLI is the foundational building block. Engineers first define an SLI to capture performance data, and then apply an upper or lower bound to that SLI over a compliance period to create a Service Level Objective (SLO).
An error budget is the quantifiable amount of unreliability or failure a service is permitted to experience over a compliance period while still meeting its Service Level Objective (SLO). Calculated mathematically as 1 − SLO (or 100% − SLO%), the error budget represents the number of promises a service can fail to uphold during a time window before violating its reliability target.
99.5%), which is the SLO itself. In contrast, the error budget for this target would be the remaining 0.5% of requests allowed to exceed 300 milliseconds.1 − SLO at the beginning of a compliance window and declines each time actual service performance misses the SLO criterion.The question asked for the term that quantifies the remaining 0.5% allowance of slow or failed checkout requests that the service can tolerate over the 30-day window without breaching its internal reliability goal.
Because an SLO determines the error budget, a useful SLO always targets less than 100%. Setting a 100% target leaves a 0% error budget, leaving zero room for planned changes, routine deployments, or inevitable infrastructure transients.
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