Exam Professional Cloud DevOps Engineer topic 1 question 66 discussion

Reason : Incident has not occurred yet, even when development team is already pushing new features multiple times a week. The option A says, to define an error budget "policy", not to define error budget(It is already present). Just simple means to bring in all stakeholders, and decide how to consume the error budget effectively that could bring balance between feature deployment and reliability.

Option A

A. Develop an appropriate error budget policy in cooperation with all service stakeholders. This will help to establish clear guidelines and expectations for service reliability, and ensure that the development team is aware of the importance of maintaining the SLO during periods of high traffic or other potential incidents. Additionally, the error budget policy will provide a clear framework for how to prioritize and respond to incidents, and ensure that the development team is able to quickly and effectively shift its focus to improving service reliability in the event of an incident.

going with A)

SLO Miss Policy If the service is performing at or above its SLO, then releases (including data changes) will proceed according to the release policy. If the service has exceeded its error budget for the preceding four-week window, we will halt all changes and releases other than P01 issues or security fixes until the service is back within its SLO. Depending upon the cause of the SLO miss, the team may devote additional resources to working on reliability instead of feature work.

A is the answer.

The goals of this policy are to: -- Protect customers from repeated SLO misses -- Provide an incentive to balance reliability with other features https://sre.google/workbook/error-budget-policy/

I vote for A

I vote for A

Correct answer: A

the reason why A is the answer we want something that is in relation to A....Service reliability, and who needs that service to be reliable its the customer, remember as Devops engneer you must put yourself inthe shoes of a customer.

thats the enswer

I don't think the answer should be A. Error Budget = 100% - SLO. Since the SLO is "well defined", ideally the Error Budget is going to already be well defined as well.

Correct Answer - A Error Budget Definition: A "Quantitative" measurement shared between SRE & product teams to balance innovation and stability. Hence first step is defining this "quantitative" error budget(Answer A). Only when there is risk of exceeding error budget then negotiate with product team (stakeholder) to prioritize reliability over features (option B)

Correct Answer is (B): When developing for your system, think of reliability as a feature, and in fact your most important feature, as customers simply expect that things ‘just work’. Once you have your objectives, reliability engineering provides practices to help you reach them, including: • Redundancy systems: Such as contingencies for using backup servers • Fault tolerance: Such as error correction algorithms for incoming network data • Preventative maintenance: Such as cycling through hardware resources before failure through overuse • Human error prevention: Such as cleaning and validating human input into the system • Reliability optimization: Such as writing code optimized for quick and consistent loading Keeping these reliability practices in mind as you develop will make your code acceptably reliable. At the same time, you’re able to confidently accelerate development by evaluating it against SLOs.

Ans B https://www.fullstory.com/blog/bootstrapping-an-availability-program-using-sre-principles/ Lets not forget the principles of availbility & reliabilty

Should be A