SRE Practitioner study guide
SRE Practitioner · Work through your exam, one topic at a time.
The Site Reliability Engineering (SRE) Practitioner certification is an advanced credential from DevOps Institute, positioned as a follow-on to the SRE Foundation certification for people who need to apply SRE practices rather than just describe them. The exam is 40 multiple-choice questions delivered web-based over 90 minutes, with a passing score of 65 percent; it is open book and available in English, Brazilian Portuguese and Japanese. The SRE Practitioner study guide has 9 sections and about 3,084 words.
01SRE Culture, Principles, and Antipatterns
SRE is an engineering discipline applied to operations problems. The foundational principles a candidate must be able to name and reason about are: embracing risk rather than pursuing 100% availability; defining reliability through service level objectives backed by error budgets; eliminating toil through automation; measuring systems rather than eyeballing them; automating away repetitive work; release engineering as a first-class practice; and simplicity as a reliability feature (fewer moving parts, fewer failure modes).
355 words, about 2 min02Organizational Impact of Adopting SRE
Adopting SRE is an organizational change as much as a technical one. Exam questions probe the engagement models : an embedded model places SREs inside a product team; a consulting model has SREs advise without owning on-call; and an enablement or "SRE as a library" model scales a small central team by giving product teams tooling, SLO templates, and training while the product team keeps ownership.
337 words, about 2 min03SLIs, SLOs, and Error Budgets in a Distributed Ecosystem
An SLI is a quantitative measure of service behavior - best expressed as a ratio of good events to valid events (successful requests / all requests, requests under a latency threshold / all requests). An SLO is a target value for that SLI over a window (for example, 99.9% of requests succeed over a rolling 28 days).
350 words, about 2 min04Security and Resilience by Design in a Zero-Trust Environment
Zero trust replaces the perimeter assumption with "never trust, always verify". Every request is authenticated and authorized on its own merits, regardless of network location; identity - of users, services, and workloads - becomes the control plane.
339 words, about 2 min05Full-Stack Observability, Distributed Tracing, and Observability-Driven Development
Observability is the ability to ask new questions of a system without shipping new code. It is commonly decomposed into metrics, logs, and traces, but the modern framing emphasizes high-cardinality, high-dimensionality events (wide structured events) joined by shared context.
346 words, about 2 min06AI-Curated Data, AIOps, and DataOps for Proactive Incident Management
AIOps applies machine learning to operational telemetry to reduce noise and shorten detection and diagnosis. The pipeline matters as much as the model: ingest metrics, logs, traces, events, and change records; normalize and enrich with topology and deployment metadata; deduplicate and cluster related alerts; then apply detection (baselines with seasonality and trend), correlation, and sometimes prediction.
341 words, about 2 min07Platform Engineering for Consistency and Predictability
Platform engineering builds an internal developer platform that makes the reliable, secure, observable path also the easiest path. The organizing idea is the golden path (or paved road): a supported, opinionated route from code to production - templated service scaffolding, standardized CI/CD, GitOps delivery, preconfigured observability, SLO templates, secret management, and policy guardrails - that product teams self-serve without filing tickets.
340 words, about 2 min08Practical Chaos Engineering
Chaos engineering is the discipline of experimenting on a system to build confidence in its ability to withstand turbulent conditions. The method is scientific, not destructive: state a hypothesis ("if one instance of the checkout service is terminated, conversion SLI stays within SLO"), define a steady-state metric that represents normal behavior, introduce a controlled variable, and compare against the baseline.
337 words, about 2 min09Major Incident Response Responsibilities
Effective major incident response separates command from execution . The Incident Commander (IC) coordinates, sets severity, makes trade-off decisions, and keeps the responder group focused; the IC does not debug.
339 words, about 2 min