Exam Professional Cloud DevOps Engineer All Questions

View all questions & answers for the Professional Cloud DevOps Engineer exam

Exam Professional Cloud DevOps Engineer topic 1 question 145 discussion

Actual exam question from Google's Professional Cloud DevOps Engineer

Question #: 145
Topic #: 1

[All Professional Cloud DevOps Engineer Questions]

You recently noticed that one of your services has exceeded the error budget for the current rolling window period. Your company's product team is about to launch a new feature. You want to follow Site Reliability Engineering (SRE) practices. What should you do?

A. Notify the team about the lack of error budget and ensure that all their tests are successful so the launch will not further risk the error budget
B. Notify the team that their error budget is used up. Negotiate with the team for a launch freeze or tolerate a slightly worse user experience.
C. Escalate the situation and request additional error budget.
D. Look through other metrics related to the product and find SLOs with remaining error budget. Reallocate the error budgets and allow the feature launch.

Show Suggested Answer

Suggested Answer: B 🗳️

by activist at Oct. 21, 2023, 7:19 p.m.

Comments

Submit Cancel

alpha_canary

10 months ago

Selected Answer: B

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. https://sre.google/workbook/error-budget-policy/#:~:text=If%20the%20service%20has,exceed%20the%20error%20budget..

upvoted 1 times

alpha_canary

10 months ago

https://sre.google/workbook/error-budget-policy/#:~:text=If%20the%20service%20has,exceed%20the%20error%20budget.

upvoted 1 times

...

xhilmi

1 year ago

Selected Answer: B

Choosing (option B) aligns with Site Reliability Engineering (SRE) principles, emphasizing the importance of maintaining system reliability and availability. By notifying the team that the error budget has been exhausted, the SRE team is proactively communicating the potential risks associated with launching the new feature during a period of heightened error rates. The suggestion to negotiate for a launch freeze or tolerate a slightly degraded user experience demonstrates a commitment to preserving the system's reliability and ensuring that user impact is minimized. This approach fosters a collaborative effort between the SRE team and the product team, allowing for informed decision-making that prioritizes reliability over feature deployment when necessary, adhering to the core tenets of SRE practices.

upvoted 1 times

...

nqthien041292

1 year ago

Selected Answer: B

Vote B

upvoted 1 times

...

mshafa

1 year, 1 month ago

Selected Answer: B

This is SRE-friendly approach.

upvoted 2 times

...

lelele2023

1 year, 1 month ago

Selected Answer: B

Only B seems to make a bit sense although I don't like the idea to tolerate a worse user experience.

upvoted 3 times

...

koo_kai

1 year, 1 month ago

Selected Answer: B

Negotiate with the team for a launch freeze or tolerate a slightly worse user experience.

upvoted 2 times

...

activist

1 year, 1 month ago

Answer C seems to be correct per Google docs: https://sre.google/workbook/error-budget-policy/

upvoted 2 times

Feliphus

11 months, 3 weeks ago

If you look on link https://cloud.google.com/blog/products/management-tools/sre-error-budgets-and-maintenance-windowsfor silver bullets, there is an option to deploy when you have burnt the error budget. But it has to be scalated to ownerships. Then I think ans C is correct. You get extra error budget with the silver bullets. In B, you assume you can andthe Developer team negotiate a worse experience user, but it has to be negotiate to ownerships no between the developer team

upvoted 1 times

...

Jason_Cloud_at

1 year, 1 month ago

The link you have shared also tells about pausing the workload and nowhere says ask for error budget. I will go with B

upvoted 4 times

...