CLOUD-DIGITAL-LEADER practice question 30 of 35

An organization's public cloud provider failed to meet their SLA of 99.99% availability. What is the potential impact on the organization?

Full set: 411 questions
Answer options
A: The organization risks using up their error budget.
B: Renegotiation of the SLA to put less emphasis on uptime could be necessary.
C: Unexpected downtime could risk the loss of customers. Correct answer
D: All data stored in their database could be unexpectedly lost.
Correct Answer:
C. Unexpected downtime could risk the loss of customers.
Explanation

If the cloud provider misses its 99.99 % availability SLA, the organization can experience unplanned service interruptions. Such downtime directly affects end-user experience, erodes trust, and may drive customers to competing services, resulting in revenue loss and long-term churn. Availability shortfalls do not, by themselves, imply data loss, mandate SLA renegotiation toward less uptime, or automatically “spend” an internally defined error-budget; they chiefly threaten business continuity and customer retention.

Why Incorrect

A. Error budgets measure the gap between an internal SLO and observed reliability; provider SLA breaches do not necessarily consume the organization’s own error budget.
B. A failure to meet uptime targets usually drives tighter—not looser—availability terms; renegotiating for lower uptime is counter-intuitive.
D. An availability SLA concerns service reachability; durability commitments protect against data loss, which is governed by separate terms (e.g., data durability SLAs).

References

1. Google Cloud Architecture Framework – Reliability Pillar, “Business impact of outages includes revenue loss, customer churn, and brand damage.” (Section 1.2, 2023‐05‐09 edition)

2. Google Cloud Service Level Agreements Overview, “Availability SLAs cover service reachability, not data durability.” (Docs > SLA overview, para 2)

3. Beyer et al., Site Reliability Engineering, O’Reilly/Google, “Error budgets measure conformance to internal SLOs, independent of external vendor SLAs.” (Ch. 4, p. 79)

Scroll to Top