SRE Foundation study guide
SRE Foundation · Work through your exam, one topic at a time.
The Site Reliability Engineering (SRE) Foundation℠ certification is a vendor-neutral, entry-level credential offered by DevOps Institute, now part of the PeopleCert Group. It is aimed at anyone who needs a shared vocabulary for reliability work: Site Reliability Engineers and engineers moving into the role, DevOps practitioners, software engineers, system integrators, consultants and change agents, plus IT directors, managers, team leaders, product owners and Scrum masters who sponsor or work alongside SRE teams. The SRE Foundation study guide has 8 sections and about 3,166 words.
01SRE Principles and Practices
Site Reliability Engineering treats operations as a software problem. Instead of staffing production with people who only run systems, SRE staffs it with engineers who write code to run systems.
384 words, about 2 min02Service Level Objectives and Error Budgets
SLI (indicator): a quantitative measurement of service behaviour, e.g. the proportion of HTTP requests served in under 300 ms, or the proportion of successful writes.
389 words, about 2 min03Reducing Toil
Toil is work that is manual, repetitive, automatable, tactical, devoid of enduring value, and scales linearly with service growth . All the properties matter.
374 words, about 2 min04Monitoring and Service Level Indicators
Monitoring exists to answer: is the service healthy from the user's perspective, and if not, why? Instrument four golden signals - latency (especially tail latency, not just the mean), traffic, errors and saturation.
328 words, about 2 min05SRE Tools and Automation
Automation is the main lever SRE has for scaling reliability without scaling headcount. It shows up at several levels: eliminating toil (scripting and self-service tooling), release engineering (build pipelines, artefact promotion, reproducible builds), infrastructure as code and configuration management, and safe rollout mechanisms - canaries, blue/green deployments, feature flags, staged rollouts with automatic rollback tied to SLI regression.
329 words, about 2 min06Anti-Fragility and Learning from Failure
Complex systems fail. Anti-fragile practice assumes failure is normal and engineers for graceful degradation: redundancy without shared fate, load shedding and admission control, timeouts, retries with exponential backoff and jitter, circuit breakers, and the ability to serve a degraded but useful experience.
344 words, about 2 min07Organizational Impact of SRE
The deepest organisational effect of SRE is not tooling; it is that reliability becomes a negotiated, measurable commitment rather than an argument. Error budget policies give product, development and operations a shared rule for when to ship and when to stop and fix.
346 words, about 2 min08SRE, Other Frameworks, The Future
DevOps is a broad cultural and professional movement - often summarised as CALMS (culture, automation, lean, measurement, sharing) - aiming to remove the wall between development and operations. SRE is one prescriptive implementation of those ideas: the specific mechanisms (SLOs, error budgets, the 50% rule, blameless postmortems, toil budgets) are what SRE adds.
672 words, about 3 min