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?