SRE Certification Exam Questions and Prep (2027)
SRE certification questions with answers: which SRE credentials exist, SLOs, error budgets, burn rate, toil, incident roles and exam-style scenarios.
SRE certification interview questions test the ideas that SRE exams and hiring panels share: SLIs, SLOs and error budgets, toil, golden signals, incident roles and blameless postmortems, plus short decision scenarios. This page lists the SRE credentials that exist today, from their owners' pages, and 28 exam-style questions with answers.
For the general interview list, use 100+ SRE interview questions and answers. For longer case studies see scenario-based SRE questions, and for a study timeline read the SRE interview preparation guide.
Key takeaways
- There is no single official SRE exam; the main vendor-neutral option is DevOps Institute's SRE Foundation, with a Practitioner follow-on.
- Google Cloud's Professional Cloud DevOps Engineer is the closest Google credential.
- Every SRE exam leans on the Google SRE book and workbook: SLOs, error budgets, toil and postmortems.
- Practise downtime arithmetic and burn-rate alerting; both appear often.
- Check exam formats and prices only on the certifier's own site.
Which SRE certifications exist?
There is no single industry SRE exam. The table lists credentials whose owners publicly describe SRE content. Exam formats, prices and renewal rules change, so read the certifying body's own page before you book; we do not quote them here.
| Credential | Certifying body | What it focuses on |
|---|---|---|
| Site Reliability Engineering (SRE) Foundation | DevOps Institute (part of PeopleCert) | Vendor-neutral SRE principles: SLOs, error budgets, toil, observability, incident response |
| SRE Practitioner | DevOps Institute (part of PeopleCert) | Advanced follow-on to SRE Foundation; check the DevOps Institute site for current details |
| Professional Cloud DevOps Engineer | Google Cloud | Applying SRE practices, CI/CD and observability on Google Cloud |
Google, which created SRE, does not offer a certification named SRE; its cloud DevOps exam is the closest. Cloud and Kubernetes certifications such as AWS DevOps Engineer Professional or CKA are often listed in SRE job ads because SREs operate those platforms, but they do not test SRE practice itself.
Freshers: SRE concepts every certification tests
These map to the foundation-level ideas from the Google SRE books that vendor-neutral SRE exams build on.
1. What is site reliability engineering?
SRE is an approach to running production systems that treats operations as a software problem. Reliability targets are set from user needs, measured with SLIs and SLOs, and protected with error budgets, automation and blameless learning. The idea comes from Google and is described in the Site Reliability Engineering book.
2. What is the difference between an SLI, an SLO and an SLA?
An SLI is a measurement, such as the share of requests served in under 300 ms. An SLO is the target for that SLI over a window, such as 99.9% over 28 days. An SLA is a contract with consequences if a level is missed, and it should be looser than the internal SLO.
| Term | What it is | Owner |
|---|---|---|
| SLI | A ratio of good events to valid events | Engineering |
| SLO | Target value for the SLI over a window | Engineering and product |
| SLA | Contract with penalties | Business and legal |
3. What is an error budget?
One minus the SLO. A 99.9% monthly SLO allows 0.1% of requests (or time) to fail. While budget remains, teams can ship faster; when it is spent, an agreed error budget policy shifts effort to reliability work.
4. What is toil?
Manual, repetitive, automatable work that scales with service size and has no lasting value, such as hand-restarting a stuck job. The SRE book suggests keeping toil under half of an SRE's time so engineering work can reduce it.
5. What are the four golden signals?
Latency, traffic, errors and saturation. They come from the monitoring chapter of the SRE book and are a common exam and interview item.
6. Why does SRE prefer symptom-based alerts?
Users feel symptoms (slow pages, errors), not causes (high CPU). Alerting on symptoms, ideally on SLO burn, pages people only when users are affected and leaves cause metrics for dashboards and debugging.
7. What is a blameless postmortem?
A written review after an incident that records impact, timeline, root causes and action items without blaming individuals. The aim is to fix systems and processes so the same failure is less likely.
8. What does 'hope is not a strategy' mean in SRE?
It is an informal SRE motto: reliability comes from measured targets, tested failover and practised incident response, not from assuming things will work.
2 to 5 years: applying SRE practices
Mid-level certification questions and interviews ask you to calculate and decide, not define.
9. How much downtime does 99.9% availability allow in a 30-day month?
About 43 minutes (0.1% of 43,200 minutes is 43.2 minutes). For 99.99% it is about 4.3 minutes. Expect to do this arithmetic on paper.
10. What is burn rate, and how do you alert on it?
Burn rate is how fast you consume error budget relative to the SLO window. A burn rate of 1 uses the whole budget exactly at the end of the window. The SRE workbook recommends multiwindow, multi-burn-rate alerts, for example paging on a fast burn over 1 hour confirmed by a 5 minute window, and ticketing on slower burns.
11. How do you choose a good SLI for a web API?
Measure at the point closest to the user that you can, usually the load balancer. Use the ratio of successful requests to valid requests for availability, and the share of requests under a latency threshold for latency. Exclude client errors that the service cannot fix.
12. What goes into an error budget policy?
What happens when the budget is exhausted (feature freeze, reliability sprint), who can grant exceptions, how incidents count against budget, and how the policy is reviewed. It should be agreed by engineering and product before it is needed.
13. What roles exist in incident response?
A common model has an incident commander who coordinates, an operations lead who makes changes, a communications lead who updates stakeholders, and a scribe. Separating roles stops the person fixing things from also running the call.
14. How do you reduce toil in practice?
Measure it (track tickets and manual tasks), pick the highest-volume items, automate or remove them, and make the fix part of the platform so it does not return. Self-service tooling often removes more toil than scripts.
15. What is capacity planning in SRE terms?
Forecasting demand from organic growth and planned launches, load testing to find the limits of each component, and provisioning with headroom so the service meets its SLO at peak, including when a zone fails.
16. How does release engineering support reliability?
Through reproducible builds, small changes, progressive rollouts (canaries, feature flags) with automatic rollback on SLO regression, and configuration treated like code.
17. What is the purpose of a game day or chaos experiment?
To test a hypothesis about how the system behaves under failure, such as losing a zone, in a controlled way, and to practise response. Start in staging, limit blast radius, and have a stop condition.
18. How do you make on-call sustainable?
Limit pages per shift, follow up every page with a fix or alert change, keep runbooks current, share load across enough people, and give time back after heavy shifts. Page only for user-facing urgent problems.
Senior: SRE leadership and design
Senior rounds and advanced practitioner exams expect trade-offs and organisational judgement.
19. How do you introduce SRE into a team that has never used SLOs?
Start with one critical user journey, define one or two SLIs from existing data, set a realistic SLO from current performance, and review it monthly with product. Add error budget policy only once people trust the numbers.
20. How do you set SLOs for a service with dependencies?
A service cannot be more reliable than its critical dependencies in series. Map the dependency chain, add redundancy or graceful degradation where a dependency is weaker than your target, and agree SLOs with dependency owners.
21. What SRE engagement models exist?
Common ones are embedded SREs in product teams, a central SRE team that owns shared platforms, and consulting engagements with a production readiness review before SRE takes on a service. Each needs a clear handback rule if the service misbehaves.
22. What is a production readiness review?
A checklist review before launch or before SRE takes over a service: SLOs and alerts, capacity tests, rollback plan, runbooks, dependencies, security and data recovery. It stops unknown risks from reaching on-call.
23. How do you measure whether your SRE practice is working?
Track SLO attainment, error budget spend, pages per shift, toil percentage, time to restore, and the share of postmortem actions completed. Trends matter more than single numbers.
24. How do SRE and DevOps relate?
DevOps is a broad culture and set of practices for faster, safer delivery. SRE is one concrete way to implement it, with SLOs, error budgets and engineering work on operations. Our SRE vs DevOps comparison covers the differences.
Certification-style scenarios
Practitioner-level exams and interviews present short cases. Answer with a decision and a reason.
25. Scenario: the SLO is 99.9% and the team has spent 80% of the monthly budget by day 10.
Apply the error budget policy: slow or freeze risky releases, prioritise fixes for the main budget consumers, and review whether the SLO matches user needs. Do not quietly lower the SLO to make the problem disappear.
26. Scenario: on-call gets 30 pages a week, most of which need no action.
Delete or downgrade alerts that need no human action, convert cause-based alerts to dashboards, and move to SLO burn-rate alerts. Review the remaining pages weekly with the team.
27. Scenario: a postmortem names an engineer who ran the wrong command.
Rewrite it blamelessly: ask why the system allowed the command, why there was no guardrail or review, and add action items such as safer tooling or confirmation steps.
28. Scenario: product wants a 99.999% SLO for a new feature.
Ask what users need and what it costs. Five nines allows about 26 seconds a month of failure and usually requires multi-region design. Agree a lower SLO that matches user expectations unless the business case justifies the cost.
How to prepare
Read the SRE book chapters on SLOs, monitoring, toil, incident management and postmortems, then the workbook chapters on implementing SLOs and alerting on them. Build an SLO dashboard for a small app with Prometheus and Grafana and write one postmortem for a failure you cause on purpose. The role of SREs in DevOps teams gives context, and our DevOps training covers the Linux, Kubernetes and monitoring base that SRE roles expect.
Official references
- Google SRE book
- Google SRE workbook
- DevOps Institute SRE Foundation
- Google Cloud Professional Cloud DevOps Engineer
Frequently asked questions
Is there an official SRE certification?
There is no single official exam. DevOps Institute, now part of PeopleCert, offers SRE Foundation and SRE Practitioner, and Google Cloud's Professional Cloud DevOps Engineer covers SRE practices on Google Cloud.
Does Google offer an SRE certification?
Not under that name. Google publishes the SRE books for free, and its related credential is the Google Cloud Professional Cloud DevOps Engineer certification.
Do I need an SRE certification to get an SRE job?
Usually not. Employers look for Linux, networking, coding, Kubernetes, cloud and on-call experience. A certification can help structure study, but practical answers decide interviews.
What should I study for an SRE foundation exam?
SLIs, SLOs and SLAs, error budgets and policies, toil, monitoring and the golden signals, incident response roles, blameless postmortems and release practices. The Google SRE book and workbook cover all of these.
Where can I check exam price and format?
Only on the certifying body's page: the DevOps Institute or PeopleCert site for SRE Foundation and Practitioner, and the Google Cloud certification page for Professional Cloud DevOps Engineer.
How is this page different from the 100+ SRE interview questions?
The 100+ post is the general SRE interview list. This page is organised around certification-style concepts and short exam-style scenarios, plus which credentials exist.
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Angry
0
Sad
0
Wow
0