Toil Reduction & Elimination Flashcards

An SRE proposes building a deployment pipeline to replace a 47-step manual deployment checklist. The initial build will take 3 sprints. What framework should justify this investment?

Answer: Calculate cumulative hours saved per deployment multiplied by deployment frequency over 12 months and compare to the build cost

Toil elimination is justified by comparing cumulative time saved (hours × frequency × team size) against investment cost over a reasonable horizon.

What is the PRIMARY risk of over-automating processes that still require human judgment?

Answer: Automation can mask system anomalies by silently 'fixing' symptoms without addressing root causes

Blind automation of remediation can hide underlying problems by repeatedly correcting symptoms while the root cause continues to worsen.

A team uses a ticketing system where 200 tickets per month are opened and closed by the same automation script with no human review. This is BEST described as:

Answer: Automated toil that should be eliminated by fixing the root cause or removing unnecessary process steps

Tickets created and resolved entirely by automation with no human value are vestigial toil — the process generating the tickets should be fixed or eliminated.

Which practice BEST helps SRE teams identify toil that has become 'invisible' due to normalization over time?

Answer: Conducting regular toil audits where engineers time-track their work for one week per quarter

Periodic time-tracking audits reveal the true proportion of toil versus project work, making normalized toil visible again.

An SRE team is deciding between fixing the root cause of frequent disk-full alerts versus building automation to clean up disk space when triggered. Which approach aligns BEST with SRE toil-elimination principles?

Answer: Fix the root cause (e.g., log rotation misconfiguration or storage quota) to prevent the condition entirely

Eliminating the root cause removes both the alert toil and the need for remediation automation, representing the highest-value intervention.

How does infrastructure-as-code (IaC) contribute to toil reduction in SRE practice?

Answer: IaC replaces repetitive manual provisioning steps with version-controlled, reproducible, automated deployments

IaC converts manual, error-prone infrastructure changes into automated, consistent processes that can be executed repeatedly without human intervention.

An on-call engineer receives an alert, checks a dashboard, determines everything is normal, and acknowledges the alert — 15 times per week. This is toil because:

Answer: It is repetitive, manual, devoid of enduring value, and scales with alert volume rather than engineering capacity

Classic toil characteristics: repetitive action triggered by an external event, requiring human time with no lasting benefit, growing proportionally with system scale.