Google Professional Cloud DevOps Engineer
Get started today
Ultimate access to all questions.
Comments
Loading comments...
Ultimate access to all questions.
Your Site Reliability Engineering team is engaged in toil work, specifically archiving unused data in tables within your application’s relational database, to maintain a low Latency Service Level Indicator (SLI) and meet your Service Level Objective (SLO). This toil is hindering your team from focusing on a high-priority engineering project aimed at improving the Availability SLI of your application. To reduce repetitive tasks, prevent burnout, enhance organizational efficiency, and adhere to Site Reliability Engineering best practices, what is the best course of action?
A
Change the SLO of your Latency SLI to reduce the frequency of toil work, thereby freeing up capacity to focus on the Availability SLI engineering project.
B
Identify and automate repetitive tasks contributing to toil to streamline operations and focus on the Availability SLI engineering project.
C
Assign the high-priority Availability SLI engineering project to the Software Engineering team to alleviate the burden on your team.
D
Onboard additional team members to handle the repetitive tasks contributing to toil, allowing your current team to concentrate on the Availability SLI engineering project.