Congratulations! You passed!
1.
What is an error budget? Select all that apply (2 correct responses).
Great job! Error budgets are a measurement of service unreliability.
No, the time spent pushing new releases doesn’t factor into an error budget. (But if you serve more errors during a release, you will certainly burn some of your error budget!)
2.
Who is responsible for preventing error budget exhaustion? Select all that apply (2 correct responses).
Correct! It’s the development and SRE teams who are responsible for preventing error budget exhaustion
Correct! It’s the development and SRE teams who are responsible for preventing error budget exhaustion.
3.
What are the benefits to using error budgets? Select all that apply (3 correct responses).
Great job! Error budgets are a great common incentive for your development and SRE teams to help strike a balance between reliability and development velocity. They also allow teams to self-regulate and manage the risks they take with new features.
Great job! Error budgets are a great common incentive for your development and SRE teams to help strike a balance between reliability and development velocity. They also allow teams to self-regulate and manage the risks they take with new features.
Great job! Error budgets are a great common incentive for your development and SRE teams to help strike a balance between reliability and development velocity. They also allow teams to self-regulate and manage the risks they take with new features.
4.
True or false, you need executive buy-in for your error budgets.
True! When teams have executive obligations to meet agreed-upon SLOs, that means there’s backing to make sure that both the dev and SRE teams can do their jobs while staying within SLO.
Nenhum comentário:
Postar um comentário