You support a service with a well-defined Service Level Objective (SLO). Over the previous 6 months, your service has consistently met its SLO and customer satisfaction has been consistently high. Most of your service's operations tasks are automated and few repetitive tasks occur frequently. You want to optimize the balance between reliability and deployment velocity while following site reliability engineering best practices. What should you do? (Choose two.)
Given that the service has consistently met its SLO, customer satisfaction is high, and most operations tasks are automated, the best approach to optimize the balance between reliability and deployment velocity is to increase the service's deployment velocity and/or risk and shift engineering time to other services that need more reliability. Deploying updates more frequently can help deliver value rapidly while leveraging the current stability. Meanwhile, reallocating engineering resources to services that need more reliability ensures overall improvement across the organization.
BC https://sre.google/workbook/implementing-slos/#slo-decision-matrix A: wrong – SLO is already well-defined, customer satisfaction is high. E: wrong – change SLI means how SLO, which is already well-defined. CD are valid, but the best option is C because current product is already quite reliable.
yes B and C
Agree with BC
NXD, thank you for posting the link. The answer is explicitly stated in the post. The SLO matrix listed there is also great for future use cases. I personally love reading the discussions and posts to fully understand the concepts and services. Thanks again.
Agree with BC
These are the correct answers. Thank me later. All the best guys
as NXD 's link shows (https://sre.google/workbook/implementing-slos/#slo-decision-matrix) answer is B C. See link.
i think BC
After perusing the SRE book... D, E Is correct, there is a question that is almost this very question but the wording is different
B C, ,,,, D; E Are for the previous question, number 80
B and C
BC is the answer. https://sre.google/workbook/implementing-slos/#slo-decision-matrix Choose to (a) relax release and deployment processes and increase velocity, or (b) step back from the engagement and focus engineering time on services that need more reliability.
I think B and E: A No: SLO is well defined B YES: the service met the SLO so you have error budget available for DEPLOY C I think NO, you will reduce your team number D NO higher reliability is unnecessary (SLO well defined) E YES you can modify SLI to extend coverage
i think CD are correct regarding E i am not sure we can modify SLI after we defined
As mentioned by others, we can see in the SRE book table here https://sre.google/workbook/implementing-slos/#slo-decision-matrix that when: SLO=Met Toil=Low Customer Satisfaction=High then: Choose to (a) relax release and deployment processes and increase velocity, or (b) step back from the engagement and focus engineering time on services that need more reliability. This matches only B and C.
This was asked on (12/24/22), passed the exam . I opted for B & E
Ans C; D are correct.
its a mistake here
letter B and C
Agree with BC
Agree with BC
Agree with BC
Are the questions still relavant?
B. Increase the service's deployment velocity and/or risk. With the current high reliability and consistent SLO adherence, you have room to increase the deployment velocity. This means you can deploy updates and new features more frequently, which can help in rapidly delivering value to your customers and staying competitive. As long as you monitor the impact on your SLO and maintain your reliability standards, this approach can optimize both reliability and deployment velocity. C. Shift engineering time to other services that need more reliability. Since your current service is already stable and meeting its SLOs, you can allocate some of the engineering resources to other services that might be struggling with reliability. This will help improve the overall reliability of your organization's services and make better use of your engineering talent.