Free Google Professional Cloud DevOps Actual Exam Questions - Question 4 Discussion
Question No. 4
[Applying Site Reliability Engineering (SRE) principles to a service]
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.)
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.)
Select all that apply, then reveal solution.
US
PP
Peter P.
2026-02-09
Option B feels right because if you’ve got a big error budget left over, you can afford to push releases more often or take a few risks without breaking your SLO. That helps balance speed and reliability. Alongside that, D is smart since adding more SLIs can give a fuller picture of how the app really performs from different angles before making any SLO changes. Just tightening the SLO without better measurement might be rushing it.
0
PP
Peter P.
2026-02-09
D definitely, and also B to balance reliability with faster releases.
0
AH
Ash H.
2026-01-17
Option E seems like a trap-why waste error budget on planned downtime? Option C and D make more sense here.
0