Common Preparation · Field Notes

Field Notes — What Test-Takers Report

Every other page in this course teaches you the material or the mechanics. This one was supposed to ask a different question: what do people who actually sat the SRE Foundation exam choose to publish afterwards? We searched for those accounts before writing a word of this page, and the honest headline is that we found exactly one — a single named engineer, on his own blog, describing a single sitting in December 2023. Not a shelf. Not a handful. One. So this page does the only respectable thing available: it gives you that one account in full, with its limits stated plainly; it explains why the public record for this particular exam is so empty; and then it rebuilds the rest of the picture out of what DevOps Institute and PeopleCert actually guarantee in writing — clearly labelled as official rather than experiential. Nothing here is invented to make the page look fuller than the evidence is.

Part One — the one published account

☺ Like you're 10: One real person wrote down what his exam was like. Here's everything he said, and here's what's changed since he said it.

The account is by Chris McLeod, published on his personal blog on 17 December 2023, describing an exam he sat and passed on 9 December 2023. It qualifies as a genuine field note on every test that matters: he is named, the site is his own domain rather than a content farm, he is not selling a course or a practice bank, and he describes his own sitting in specific, checkable detail rather than paraphrasing a marketing page.

Because it is the only such account we found, we are going to give it more space than a single data point would normally deserve — and then spend the rest of the page being careful about exactly how far a single data point can be stretched.

What he actually reports

↗ Chris McLeod — the account, in his own words

What "open book" actually means here — and why it may not help you

This is the single most useful thing in McLeod's write-up, and it is not obvious from the vendor pages. The SREF is officially open book. But PeopleCert's product page states the permission narrowly: candidates may use the Official Training Materials, whether supplied directly by PeopleCert or through an Accredited Training Organization. That is not "your notes." It is not "this course." It is not "the internet." It is the specific, purchased courseware.

McLeod's practical observation follows straight from that: he did not have the official materials in front of him, so the open-book allowance was worth approximately nothing to him and he answered from memory. If you self-study — that is, if you will not have the purchased official courseware open in front of you — you are, in every way that matters on the day, sitting a closed-book exam. Sixty minutes for forty questions is ninety seconds each, which is not enough time to look anything up even if you were entitled to.

Part Two — why the shelf is empty

☺ Like you're 10: We looked hard, we found one, and here's our honest guess at why there aren't more.

Saying "we found one account" is only useful if you also say how hard you looked and what you rejected. So: we searched for first-hand SREF write-ups across blogs, developer communities, LinkedIn and video, and we examined every plausible candidate rather than stopping at the first result. Most of what came back was not experience reports at all. It was accredited training partners' course pages, practice-test and exam-dump vendors, and SEO content farms — and several of those publish exam specifications that are simply wrong, which Part Four deals with.

What we examined and did not use

Rejecting sources is part of the work, and hiding the rejects would make the page look better than the evidence. Here is what we looked at and why each one did not make it into Part One.

Four reasons the record is this thin

None of this is a criticism of the certification. It's a structural consequence of what kind of exam it is, and understanding the reasons stops you from reading the silence as a bad sign.

• People write up hard hands-on exams, not sixty-minute multiple-choice ones. The genre of "how I passed" blog post exists because performance-based exams are frightening, expensive and full of tactical detail worth sharing — which cluster to touch first, how to budget minutes per task. A forty-question knowledge exam capped at Bloom levels 1 and 2 generates far less to say. Compare the platform-engineering course's equivalent page, where the hands-on CNPE has a genuine shelf of detailed write-ups and the multiple-choice CNPA barely has three.
• It is very often taken as part of an employer-paid course, not as a personal quest. McLeod's own route is the common one: a two-day classroom course with the voucher bundled in. People who are sent on a course by their employer and pass the exam at the end of it are far less likely to write a triumphant blog post than people who self-funded a months-long solo campaign.
• The search space is saturated by dump and practice-test vendors. Even if organic write-ups existed in reasonable numbers, they would be buried. Search this exam and you will hit page after page of commercial question banks before you hit a human being.
• It has changed hands. DevOps Institute was acquired by PeopleCert, the exam platform migrated in late 2023, and the syllabus moved to v1.2 in late 2024. Anything written before those changes is partly obsolete, which further thins an already thin shelf.

Part Three — what the official sources guarantee

☺ Like you're 10: One review isn't much. But the menu is printed, and the menu is guaranteed.

With testimony this thin, the reliable move is to reason forward from what the exam officially is rather than backwards from one person's afternoon. Everything in this part comes from PeopleCert's product page, DevOps Institute's certification page, or the official SREF Exam Study Guide — all three of which we checked directly. It is still worth confirming on the vendor's own page on the day you book, because vendors change these things and this page cannot change itself.

The specification, cross-checked across two official sources

The topic weighting — the most actionable official fact on this page

The free official study guide publishes something that most foundation-level exams do not: a table of the maximum number of questions drawn from each of the eight topic areas. The eight maximums sum to exactly 40, which is the whole exam. Here it is, with the page in this course that covers each area.

What the official sample paper reveals about the distribution

The free study guide contains a complete 40-question sample paper with a topic-tagged answer key. Counting that key gives a small but genuinely useful result, and you can reproduce it yourself in five minutes: the sample paper's questions are distributed 4 / 6 / 5 / 7 / 6 / 4 / 4 / 4 across the eight areas — which is every topic area sitting at its stated maximum, simultaneously, summing to 40.

Read that carefully, because it is easy to over-claim. It tells you the sample paper was constructed to the published table exactly, which is decent evidence the live forms are built from the same blueprint. It does not tell you your form will be distributed identically; the published figure is a maximum per area, and DevOps Institute promises only that no area exceeds it. The safe reading: plan as though your paper looks like the sample, and do not be shocked if one area is a question light.

The Bloom ceiling — the official calibration for "how hard should I study?"

This is the most quotable line in the whole official corpus and the one that most directly corroborates McLeod. The study guide states that the SREF uses Bloom's Taxonomy in constructing both the content and the exam, and that the paper contains Bloom 1 questions (testing knowledge of SRE concepts and vocabulary) and Bloom 2 questions (testing comprehension of those concepts in context). That is the whole range. There is no Bloom 3 — no "apply this to a novel situation," no multi-step design judgement.

McLeod, describing the exam in his own terms rather than the study guide's — he does not invoke Bloom levels anywhere — landed on "broad rather than deep." Those two statements are the same statement, arrived at from opposite directions — one from the exam's construction rules, one from a candidate's experience of it. That is what corroboration actually looks like, and it is worth more than five unattributed blog posts agreeing with each other.

Version drift — the free guides are two versions behind

The free official study guides are excellent and we recommend them below. They are also v1.0 (2020) and v1.1 (2021). The current SRE Foundation material is v1.2, updated October 2024, and PeopleCert describes that update as adding insights on modern DevOps practices including generative AI, AIOps, platform engineering, value stream management, observability and progressive deployments, alongside refreshed references and redesigned materials. (A further minor revision in January 2025 tidied the sample papers inside the trainer and learner materials — nothing that affects your preparation.) SRE Practitioner, the next credential up, is separately at v1.3 as of December 2024.

The renewal contradiction — three different answers, none of them ours

We are flagging this rather than resolving it, because it genuinely is not resolvable from public sources. Three claims are in circulation, and two of them appear on the same page:

• Three years. DevOps Institute's certification page lists validity as 3 years, footnoted with an explanation that following PeopleCert's acquisition of DevOps Institute, certifications completed on the PeopleCert platform carry a 3-year validity from date of issue under PeopleCert's Continuing Professional Development programme. PeopleCert's own product page also states renewal every 3 years, requiring 60 CPD points.
• Two years. The Overview prose on that same DevOps Institute page still says DevOps Institute certifications expire two years from the date of completion.
• Evergreen. Some training partners advertise DevOps Institute certifications as never expiring at all.

Three years is the best-supported answer — it is the only one stated in two places, and the only one that accounts for the acquisition. But a page contradicting itself is exactly the kind of thing you should not paper over in study material. If renewal terms matter to your decision — and if your employer is paying, they probably do — ask PeopleCert directly before you book, and get the answer in writing.

Part Four — the traps

☺ Like you're 10: Googling this exam is genuinely dangerous. Here are the specific ways the search results will lie to you.

Most exam pages in this course have a "verify before you book" note. This one needs a longer list than usual, because the misinformation around this specific exam is unusually thick and unusually specific.

Part Five — what can be responsibly borrowed

☺ Like you're 10: One review can't tell you much. But there are other things you're allowed to lean on, as long as you say out loud what they are.

With one first-hand account, the gap has to be filled with something. These five sources can carry real weight — provided each one is labelled for what it is rather than smuggled in as though a candidate had said it.

1. PeopleCert's own online-proctoring documentation — official, and directly applicable

This is the strongest borrow available, and it is not really a borrow at all. PeopleCert publishes its online-proctoring process — the pre-exam system check, ID verification, the room scan, clear-desk rules, what the proctor will and will not allow — and it is the same pipeline used across ITIL, PRINCE2 and the whole DevOps Institute portfolio. It is therefore an official source for SREF exam-day mechanics, not an analogy.

And here is the useful part: McLeod's independent, first-hand description of his session — the human proctor, the slow webcam pan over and under the desk, the required camera angle showing him and the doors — matches that documented process. One official description and one independent account of the same thing agreeing is a real consistency check. Read the official page for what will be asked of you, then read McLeod for what it feels like when it is.

↗ PeopleCert — online proctoring process

2. The official 40-question sample paper — vendor-authored, free, and the closest public analogue to a real form

Inside the free SREF Exam Study Guide is a complete sample paper with a full, topic-tagged answer key. This is the single best free asset for this exam and it is startling how rarely it gets mentioned. It is vendor-authored, it matches the published topic distribution exactly, and it is legitimately published — which makes it the honest alternative to every dump site in Part Four. The same guide also carries a large DevOps and SRE glossary and a curated resource list.

Use it as a diagnostic, not a drill: sit it once, cold, timed to 60 minutes, before you have studied much — the topic tags on the answer key will tell you exactly which of the eight areas you are weakest in, which is more information than a bare score. Then work the weak areas and come back to this course's mock papers for repeat practice, so you are not re-sitting a paper you have accidentally memorised.

↗ Official SREF v1.1 Exam Study Guide (PDF)

3. The Bloom 1–2 ceiling — your calibration for when to stop

Covered above, and worth restating here as a borrowing strategy in its own right: the official difficulty ceiling is the most reliable answer available to "how deep do I need to go?" You do not have to infer the answer from a candidate's impression, because the exam's own construction rules state it. When you are deciding whether to spend another evening on multi-window burn-rate alerting for the exam's sake, the Bloom ceiling says no — know what a burn rate is, know why fast and slow windows both exist, move on. (Learn it properly anyway, for the job. Just not on exam time.)

4. Sibling exams in the same family — mechanics transfer, syllabus does not

DevOps Foundation and SRE Practitioner sit in the same PeopleCert-delivered family as the SREF. They share the delivery platform, the online-proctoring pipeline, the open-book-with-official-materials rule and the multiple-choice format. Accounts of sitting those exams can therefore tell you useful things about the machinery — booking, the system check, what the proctor does, how results arrive.

They tell you nothing reliable about content. SRE Practitioner is a different, harder exam on a different syllabus at a higher Bloom level; DevOps Foundation is about DevOps rather than SRE. Borrow the mechanics, never the syllabus, and never the numbers. This is the same discipline the platform-engineering course applies when it borrows KCNA and KCSA tactics for CNPA preparation — useful, as long as the label stays attached.

5. The free primary literature the syllabus is built on

Google's Site Reliability Engineering and The Site Reliability Workbook are free to read online at sre.google, and they are the closest thing the discipline has to primary sources. Two independent parties point you at them: the official study guide's resource list cites them directly, and McLeod names them as part of his own self-study. When your only first-hand account and the vendor's own guide recommend the same books, that recommendation is about as well-founded as anything on this page.

Read them for understanding rather than for exam coverage — they are far deeper than Bloom 2 requires, and much of what makes them great is beyond the exam's scope. The chapters that map most directly onto the heavy topic areas are the ones on service level objectives, on eliminating toil, and on monitoring distributed systems.

↗ sre.google — the free Google SRE books

Reading a single account without over-fitting to it

☺ Like you're 10: One person's story is true about that person. It isn't automatically true about you.

The failure mode this page exists to prevent is subtle, and it is worth naming because you will meet it constantly once you start looking for exam advice. It is the quiet promotion of an observation into a specification.

"I had four options on every question" is an observation, and almost certainly accurate. "The exam has four options per question" is an inference — one that happens to be well-supported here, since the official sources agree. "Official confirmation arrived a couple of days later" is also an observation, but nothing official promises that turnaround, so treating it as a specification would be a mistake. The two sentences look identical in structure. Only one of them has a second source behind it.

Three habits keep you honest:

• Ask what would corroborate this. For every claim in Part One we asked whether an official source, or an independent second account, says the same thing — and we wrote the answer in the table, including where the answer was "no."
• Notice who is selling something. The single most reliable filter on exam content is whether the author profits from your believing it. McLeod's account is trustworthy partly because he concludes the certification is "far from essential" — that is not what someone selling a course writes.
• Watch numbers launder themselves. A figure appears once, unattributed; a second site repeats it; a third cites the second. Within two years it reads as fact. This is exactly how "90 minutes, 50 questions, 70%" ends up on a blog about an exam that is 60 minutes, 40 questions and 65%.

So what should you actually do?

☺ Like you're 10: Short version of the whole page, in the order you should do things.

Compressing everything above into a sequence:

1. Confirm the spec yourself on PeopleCert's and DevOps Institute's own pages, for your own region, on the day you book — including the price and the renewal terms, which are the two most volatile things here. The exam guide covers registration mechanics.
2. Sit the official sample paper cold, timed to 60 minutes, and use its topic-tagged answer key to find your weakest of the eight areas.
3. Weight your study by the published maximums — Monitoring & SLIs, SLOs & error budgets and Tools & automation are 19 of 40 questions between them. The study plan already schedules it this way.
4. Study for recall, not recognition, because open book will not help a self-studier. The closed-book strategy page, Know It Cold and the flashcards are the machinery for that.
5. Calibrate to Bloom 1–2: broad coverage of all eight areas beats depth in three, because a skipped area donates free marks.
6. Rehearse the room scan and the system check days before, not minutes before.
7. Drill under the clock — 90 seconds a question is the real constraint. The exam simulator and answer triage are built for exactly that pressure, and Self-Check is where you find your gaps without a clock.

Check your answers

1. One — Chris McLeod, who sat and passed on 9 December 2023 and published on 17 December 2023. Caveat one: he sat the v1.1-era syllabus, so his sense of the content predates the v1.2 (October 2024) additions of GenAI, AIOps, platform engineering, VSM, observability and progressive deployments. Caveat two, and it works in your favour: he sat after the PeopleCert platform migration, so his account of the proctoring and logistics describes the current delivery model.
2. Because "open book" is restricted to the Official Training Materials supplied by PeopleCert or an Accredited Training Organization — not your notes, not this course, not the internet. A self-studier who hasn't bought the courseware has nothing permitted to open, which is exactly what McLeod found. At 90 seconds a question there would be no time to look anything up anyway.
3. SRE-4 Monitoring & SLIs (7), SRE-2 SLOs & error budgets (6), SRE-5 Tools & automation (6) — 19 of the 40 questions. The individual maximums are official, published in DevOps Institute's own study guide. The sum, and the study strategy drawn from it, are this page's arithmetic — not an official claim.
4. It caps the exam at knowledge and comprehension — define it, and recognise it described in context. No "apply this to a novel design problem." So broad coverage of all eight areas beats depth in a few. It corroborates McLeod's independent description of the exam as "broad rather than deep" — an experiential observation and a construction rule arriving at the same place from opposite directions.
5. Any two of: the GSDC name collision (a different body's separate "SRE Foundation" credential with different specs — 90 minutes, not open book); third-party blogs publishing wrong numbers (e.g. "90 minutes, 50 questions, 70%" — all three wrong); the official study guide's own stale "Supervised: No" line, which predates PeopleCert's live human proctoring; sites wrongly asserting the exam is closed book; and the exam-dump vendors that dominate the results.

Next, take the machinery seriously: the SREF exam guide for registration and the eight-module blueprint, the study plan for the week-by-week schedule, and the closed-book strategy for the memory system that makes all of it stick.