Google Cloud Professional Cloud DevOps Engineer — Question 76

You support a user-facing web application. When analyzing the application's error budget over the previous six months, you notice that the application has never consumed more than 5% of its error budget in any given time window. You hold a Service Level Objective (SLO) review with business stakeholders and confirm that the SLO is set appropriately. You want your application's SLO to more closely reflect its observed reliability. What steps can you take to further that goal while balancing velocity, reliability, and business needs? (Choose two.)

Answer options

• A. Add more serving capacity to all of your application's zones.
• B. Have more frequent or potentially risky application releases.
• C. Tighten the SLO match the application's observed reliability.
• D. Implement and measure additional Service Level Indicators (SLIs) fro the application.
• E. Announce planned downtime to consume more error budget, and ensure that users are not depending on a tighter SLO.

Correct answer: D, E

Explanation

The correct answers are D and E. Implementing additional Service Level Indicators (SLIs) can help gain a better understanding of the application's performance and reliability, while announcing planned downtime allows for the use of more error budget without negatively impacting user experience. Options A, B, and C do not address the need to align the SLO with observed reliability or could jeopardize service stability.