Exam Cloud Digital Leader topic 1 question 145 discussion

If you're within the error budget, there's no need to pause for stability just yet. In Site Reliability Engineering (SRE) practice, an error budget is the acceptable amount of unreliability based on the SLO. if the SLO is not being met, but the error budget is not yet exhausted, it indicates that there’s still tolerance for some risk. Therefore, the organization can prioritize speed and innovation, such as releasing new features, as long as they stay within the error budget.

To achieve SLO, a company needs its applications and services to be resilient. Definitely C

C is correct

C. Stability to avoid prolonged user downtime Since the organization is not meeting their SLO, they need to prioritize stability to avoid prolonged user downtime. This means focusing on fixing the underlying issues that are causing the SLO violations, rather than innovating on new features or releasing new features quickly.

C - focus on stability or lose customers.

Answer is C. Easier than A as if its not taken quickest care the Error Budget will get exhausted and the application will fall behind SLO

In this scenario, the organization should prioritize stability to avoid prolonged user downtime. This means focusing on ensuring that the service is stable and reliable, even if it means delaying new feature releases or reducing the rate of innovation temporarily. By prioritizing stability, the organization can prevent prolonged outages or downtime, which can negatively impact the user experience and erode customer trust. Once stability is achieved, the organization can then focus on innovation and improving the user experience.

They still have error budget left. The error budget gives developers clarity into how many failed fixes they can attempt without affecting the end user experience.

Minimizing downtown improves SLO.

"The error budget is typically the space between the SLA and the SLO. This error budget gives developers clarity into how many failed fixes they can attempt without affecting the end user experience."

When we monitor SLOs, our system begins to aggregate the data, and ties that back into error budgets which determines the allowable amount of system downtime or latency over a specific timeframe.

C is my answer.

Response is correct (C). Both Devs and SRE team must ensure that the error budget does not become exhausted. To avoid it, releases have to stop for the time being until the error budget resets. The team would have to reprioritise to focus on reliability to get it back to an acceptable state.

Error budgets let you track how many bad individual events (like requests) are allowed to occur during the remainder of your compliance period before you violate the SLO. You can use the error budget to help you manage maintenance tasks like deployment of new versions https://cloud.google.com/stackdriver/docs/solutions/slo-monitoring#defn-error-budget

to prevent errors like this case, should spend on stability

“The development team can ‘spend’ this error budget in any way they like. If the product is currently running flawlessly, with few or no errors, they can launch whatever they want, whenever they want. Conversely, if they have met or exceeded the error budget and are operating at or below the defined SLA, all launches are frozen until they reduce the number of errors to a level that allows the launch to proceed.”

A. Innovation to improve user experience The organization has NOT exhausted their error budget