Exam Day — What to Expect

The SRE Foundation is a sixty-minute, forty-question paper you sit at your own desk while a live human proctor watches you through your webcam. Almost nothing about that hour is technically difficult — but a surprising amount of it is procedurally unforgiving, and the failures are boring ones: a booking name that reads "Prash" while the passport reads "Prashant", a compatibility check nobody ran until twenty minutes before the slot, a second monitor that was switched off but still plugged in, a candidate who assumed "open book" meant their own notes. This page is the procedural half of your preparation. It covers what the exam actually is, how PeopleCert's online proctoring works step by step, exactly what may sit on your desk, how to spend sixty minutes across forty questions, and what to do when something goes wrong — separating what the official sources guarantee from what you must confirm yourself before you pay. It is deliberately the procedural half of preparation: what to learn and in what order lives in how to study for the exam, the knowledge the syllabus assumes you already have is in the baseline you need first, and what people who have actually sat this exam reported afterwards is in field notes.

What kind of exam day this actually is

☺ Like you're 10: There is no cloud console, no terminal, no cluster — just forty multiple-choice questions in a browser, with a real person watching through your camera.

Get the shape right first, because a lot of preparation advice on the internet is written about a different kind of exam. The SREF is a knowledge exam, not a performance exam. Nothing is graded on cluster state, nothing is typed into a terminal, and there is no environment to break. What you get is a question, four options, and a clock — forty times over.

The content is owned by the DevOps Institute; the exam itself is sold, scheduled, delivered and proctored by PeopleCert, which acquired DevOps Institute and now runs its certification portfolio on the same platform it uses for ITIL and PRINCE2. That single fact is the most useful thing on this page, because it means the exam-day mechanics are not a mystery: PeopleCert publishes detailed, versioned candidate guidelines for its online-proctored exams, and everything in the sections below about check-in, ID, the room scan and the interface comes from those documents rather than from folklore.

Which proctoring flow you will actually get

PeopleCert runs online proctoring two ways: an installable desktop application called ExamShield, and a browser-based Web Based Exam Driver that needs no installation. They are similar in spirit and differ in detail, and each has its own published candidate-guidelines document. Two signals point to the web-based driver for this exam: DevOps Institute lists SREF's delivery as "Web-based", and the Web Based Exam Driver's candidate guidelines contain a clause written specifically for DOI open book exams — DOI being DevOps Institute — describing which official courseware you may use.

That is a strong signal, not a guarantee for your particular booking, so do the thirty-second check rather than assume: your booking confirmation and your PeopleCert profile tell you which one you are on, and PeopleCert publishes both guides. Read the one that matches.

◆ PeopleCert — Web Based Exam Driver guidelines ◆ PeopleCert — ExamShield guidelines ◆ Web Based Exam Driver — Candidate Guidelines (PDF)

Everything quoted on this page comes from the Web Based Exam Driver candidate guidelines — the PDF linked above, ID no. ECS_WI_26-10, version 8.0, dated 22 January 2026 — unless stated otherwise. It is a public document, so every sentence this page puts inside quotation marks can be checked against it in about a minute. Where ExamShield differs, its own document says so.

The stale spec problem — and the exam that isn't this one

☺ Like you're 10: If you search for this exam, you will find pages with the wrong numbers on them, and one page about a completely different exam with almost the same name. Check who published anything before you believe it.

This exam has a genuinely bad public information problem, and it is worth ten minutes of your attention because the errors are the kind that change how you prepare. There are three distinct traps.

Trap one: the official free study guide's administration details are out of date

The free SREF v1.1 Exam Study Guide is an excellent asset — it contains the syllabus, the topic weighting, the concept and terminology list, a full forty-question sample paper with an answer key, a glossary and a curated reading list, all for free. Use it. But its examination-format table contains the line "Supervised: No", and that line is now stale: it describes the pre-PeopleCert delivery platform. DevOps Institute exams migrated onto PeopleCert's platform, and the exam you will sit is supervised by a live proctor who will watch you for the full hour.

The rule to carry away: from that PDF, trust the syllabus and distrust the administration. Its topic areas, its Bloom ceiling and its sample paper are still the best free map of what the questions look like. Its statements about how the exam is administered have been overtaken.

Trap two: third-party pages that simply have the numbers wrong

Search results for this certification are dominated by training resellers, practice-test vendors and exam-dump sites, and several of them publish specifications that do not match either official source. Confidently-worded pages exist stating the exam is 90 minutes, or 50 questions, or has a 70% pass mark, or is closed book — none of which is what PeopleCert and DevOps Institute publish. Exam-dump sites in particular saturate the results for this exam; beyond being useless preparation for a Bloom-1-and-2 paper, using leaked exam content is a malpractice issue that can cost you the credential. Take numbers from PeopleCert or DevOps Institute, and nowhere else.

Trap three: the name collision — two different "SRE Foundation" certifications

This one has genuinely caught people out. The Global Skill Development Council (GSDC) issues a separate credential also called Site Reliability Engineering (SRE) Foundation, code CSREF. It is not the DevOps Institute exam, it is not administered by PeopleCert, and its specification differs in exactly the places that matter for exam day.

Notice how the two rows that match — forty questions, 65% — are exactly the ones that make a reader think they have found corroboration. Someone who Googles "SRE Foundation exam duration", lands on GSDC's page and rehearses at ninety minutes will walk into a sixty-minute paper having trained at two and a quarter minutes per question when they get ninety seconds. That is a losing pace, produced entirely by reading the right numbers from the wrong exam.

Booking — the decisions that are hard to undo

☺ Like you're 10: You buy a voucher, then pick a time. The name you type when you buy it has to match your ID exactly — that is the part people get wrong.

There are two legitimate routes to a seat, and the SREF exam guide covers the choice in full: an exam-only voucher if you are self-studying, or a bundled package from an Accredited Training Organisation that includes courseware plus the exam. For exam-day purposes the bundled route has one consequence worth flagging now rather than later: the bundle is what makes the open-book allowance usable. Buy the voucher alone and you will be sitting the paper with nothing on your desk. That is a legitimate choice — but make it deliberately, not by accident.

The name-match rule, which ends attempts before they start

PeopleCert's candidate guidelines are unusually blunt about this, and the wording is worth reading twice: "If the first and last names on your ID do not exactly match the name you used to book your exam, you will not be allowed to test, and no refund will be provided." The guidelines add that a name mismatch may result in the session being terminated with no refund, and that you would then re-book through the standard process — meaning you pay again.

They are equally clear that "ID documents are NOT preapproved before the examination": your proctor checks the document on the day, during onboarding, and you are responsible for making sure it is valid and acceptable. There is nobody to appeal to at that point.

Scheduling, and the rescheduling ladder

Scheduling is self-service and fast: PeopleCert advertises that you can book a slot as little as four hours ahead, around the clock. Rescheduling is where the money is, and the guidelines set out a three-step ladder:

The guidelines note that fees depend on country, currency and applicable tax, so check the figure that applies to you rather than a number quoted on a blog. To reschedule: log in to your PeopleCert account, choose Overview, find the exam under My exams and select Change date.

Two scheduling judgements are worth making deliberately. First, pick an hour when your household is genuinely predictable — the room rules below require you to be alone, and a person walking in is an incident, not an inconvenience. Second, pick an hour when your internet is boring: not during the evening streaming peak, not during your employer's backup window.

The pre-flight — a mandatory check with a hard deadline

☺ Like you're 10: There is a five-minute computer test you have to pass at least a day before the exam. Do it in the same room, on the same laptop, on the same wifi you will really use.

This is the single most skipped requirement for this exam, and unlike most pre-flight advice it is not optional. PeopleCert's guidelines state that the system compatibility check "is mandatory before you can start your exam and must be completed at least 24 hours before your scheduled exam time." It takes about five minutes and checks your computer's system integrity, audio, camera, internet connection and speed.

Three conditions come with it, all of which people quietly break:

• Use the same computer you will use on exam day.
• Use the same setup and network — same camera, same headset, same wifi or LAN.
• Do it in the same room where you will take the exam.

PeopleCert also recommends repeating the check approximately two hours before your slot, on the grounds that an operating-system update between your first check and exam day can quietly change your configuration. That is a real failure mode, and two hours is enough runway to get technical support involved; twenty minutes is not.

The published system requirements

Note the Safari-shaped hole in that browser list. If you are a Mac user who lives in Safari, install one of the three supported browsers and run your compatibility check in it — do not discover this at check-in.

The work-laptop problem

PeopleCert says plainly that it suggests a personal computer, and warns that work computers "often have restrictions that could affect our Web Based Exam Driver". If you must use a corporate machine, the guidelines are specific about the consequences: you will need to share your screen, microphone and camera, and "you will need to make sure your organization's IT support department is available to assist you on your exam day." They also flag that corporate networks and VPN access may affect delivery, and that if the compatibility check fails you should ask IT about your organisation's policy on access to the peoplecert.org domain and on audio/video capture and screen sharing through the browser. Whitelisting *.peoplecert.org is the specific remedy the guidelines name.

Also from the guidelines: contact PeopleCert "up to 72 hours and no later than 48 hours before your exam" if your computer does not meet the requirements and you need guidance. And the consequence if you turn up on a machine that does not comply: "we may need to close the exam session and reschedule your exam."

The rest of the night-before list

• Add your mobile number, with country code, to your candidate profile. The guidelines say this is how PeopleCert reaches you if something goes wrong on the day.
• Disable virtualisation software — VMware, Virtual PC, VirtualBox, Sandbox are all named.
• Close everything that shares a screen or a message. Chat, desktop-sharing and mail clients are named specifically; AnyDesk, Skype and MS Teams appear as examples of programs to exit well before your start time.
• Sort out multiple screens before the compatibility check, not after. The check detects more than one screen and only one may be active. If you want to use a larger display, set it as primary and disconnect the others — and the guidelines add a detail people find surprising: make sure the disconnected screen "is covered (e.g. by using a towel)".
• Save your work and quit your applications. You will be sharing your entire screen with a stranger for an hour. Anything on it is on camera.

Measure your link like an SRE, not like a candidate

Four megabits is not a demanding number, and raw throughput is rarely what fails. What fails is stability — a video call that drops for four seconds every couple of minutes is a proctor connection that keeps re-establishing. You already know how to measure this; you do it for services at work. Do it for your own uplink, at the same time of day you have booked, for as long as the exam lasts. None of these commands touch the exam.

# baseline: latency and loss to a well-known resolver
ping -c 30 1.1.1.1

# one sample per second for the length of the paper, then count the failures
for i in $(seq 1 3600); do
  printf '%s ' "$(date +%H:%M:%S)"
  ping -c 1 -W 2 1.1.1.1 2>/dev/null | awk -F'time=' '/time=/{print $2; ok=1} END{if(!ok) print "LOSS"}'
  sleep 1
done | tee ~/exam-link-check.log

# your SLI for this window: how many seconds of the hour were bad?
grep -c 'LOSS' ~/exam-link-check.log

Treat the result exactly as you would a service SLI. If that count is not zero, you have an availability problem to fix before exam day: move to ethernet, move the router, or move the slot. The consolation, covered in when something goes wrong, is that a dropped connection on this exam is much less punishing than on a hands-on one — but "less punishing" is not "free", and a session that reconnects five times will still cost you concentration you cannot get back.

Identity — the check with no appeal at the desk

☺ Like you're 10: One real, unexpired, government-issued ID card with your photo on it, and the name on it has to match the name you booked with. A photo of it on your phone does not count.

ID verification happens during onboarding, before the paper is released, and it is binary. PeopleCert's published criteria are specific, and all of them have to hold at once. Your ID must:

• Be current and valid — "ID containing dates that have expired are not allowed."
• Be an original, not a photocopy.
• Include a recognisable photo of you.
• Match the information you gave when you booked.
• Be a government-issued national, state or province identity card recognised by the country in which you are a citizen or permanent resident.
• Contain your full date of birth.
• Contain your first, middle and last names in English (Latin) characters — with an important exception, below.

And explicitly: "electronic IDs will not be accepted." A digital driving licence in a phone wallet is not the document this policy asks for — and your phone should not be in your hand during the exam anyway.

One more requirement that candidates routinely miss because it is filed under preparation rather than under ID: the guidelines say you must have a second form of photo ID available and to hand in case additional verification is needed on the day. It costs nothing to put a second document on the desk beside the first.

If your ID is not written in Latin characters

This is handled, but it must be handled at booking time, and the process has its own deadline. PeopleCert's rule is that an ID not written in Latin characters is accepted only if you booked the exam selecting a proctor whose language matches your ID's script. Their own example: an ID written in Chinese characters means selecting Chinese as your proctor-language preference.

If no matching proctor language is offered in the booking system, the guidelines set out a two-step fallback: at least 48 hours before the exam, upload a clear image of your ID to your candidate profile, and separately submit PeopleCert's contact form with the subject line "ID Validation Request", giving your full name, candidate ID, date of birth, exam date and time, and country of origin. PeopleCert then tells you whether the ID can be validated; if it cannot, they contact you to reschedule so you can obtain an acceptable document.

The room, the desk, and what "open book" actually permits

☺ Like you're 10: A private room with one door, a clear desk, nobody else inside, and a slow camera tour so the proctor can see there is nothing hidden. You may have the official course book — and nothing else.

The environment rules are enforced literally rather than reasonably, and they are easy to satisfy if you prepare the room the night before instead of improvising while a proctor waits.

The room, as specified

• One doorway for access in and out, and it must be visible to your webcam throughout the exam. This is the requirement that most often forces people to move a desk.
• Private, with no transparent walls — glass walls and indoor windows are named. A meeting-room pod with glass sides does not qualify.
• No background noise, and you alone in the room.
• Walls and desk clear of unnecessary or unauthorised items — "posters, post-it notes, papers and books" are the examples given.
• No screens visible other than the one you are sitting the exam on, or a second device authorised for an open-book exam.
• Adequate light, so the proctor can always see you clearly, and not directed toward the camera — a bright window behind you turns you into a silhouette and will be corrected.

PeopleCert also includes one line that is funny right up until you understand why it exists: "We do not advise attempting to take your exam in a bathroom/restroom." People have tried. Do not be the reason for a future revision of the document.

The computer and the seat

• The webcam is clean and unobstructed.
• Screen and camera are positioned so that you and the doorway are both fully visible to the proctor.
• You can rotate the camera 360 degrees, low and high, to show all areas of the room "including under your desk, the desk's surface and any other areas that may pose a risk to exam security". That clause sets what your equipment must be able to do; the guidelines word the scan your proctor actually walks you through slightly differently, and both wordings are quoted on this page — see the security checks.
• No second monitors, smart accessories or devices connected or accessible — unless authorised for an open-book exam.
• Sound is set to speakers and microphone. For Business & IT exams, headsets are allowed only during onboarding, and if you use one the proctor will ask you to place it on the desk without disconnecting it before the exam starts.
• You are seated comfortably and able to hold the same position, in full view, for the whole hour. Sixty minutes is not long — but it is long enough that a badly-placed laptop becomes a problem.

Open book: the most misread line in the specification

Both official sources say the SREF is open book. Almost nobody reads the second half of the sentence. PeopleCert's product page states the permitted materials are the Official Training Materials — the Learner Workbook containing course content, quizzes, activities and sample papers, and the Quick Reference Guide — whether provided by PeopleCert directly or through an Accredited Training Organisation.

The candidate guidelines are more specific still. For DOI open book exams — DevOps Institute's — if you have official training materials from an Authorised Training Organisation you may use either your official hard copy learner courseware or your official digital learner courseware on a second device, which must be set to airplane mode. And then the limits:

And the mechanic that makes it real: "To allow you to use your Official Book during the exam, your proctor will ask you to open it and flip through the pages in front of the web camera." Tabs and margin notes survive that inspection. A folded sheet tucked inside it will not.

Check-in — the thirty-minute window and the onboarding sequence

☺ Like you're 10: A button appears half an hour before your slot. Press it straight away — none of that half hour comes out of your exam time.

The Check in to your exam button activates 30 minutes before your scheduled start, and PeopleCert's own advice is unambiguous: "we strongly recommend you use the full 30-minute exam check in timeframe." None of it eats your sixty minutes. Being early is free; being late is not.

The sequence, step by step

You reach the exam either from the Web Proctor Session Link email PeopleCert sends after booking, or by logging in to your profile, going to Overview and clicking Connect. Then, in order:

1. Accept the Non-Disclosure Agreement and Terms of Use. You cannot continue without agreeing. Note what this actually binds you to: the exam content is confidential, so discussing specific questions afterwards is a malpractice issue, not a grey area.
2. Read the exam instructions — read them rather than clicking past them; this is where anything exam-specific appears.
3. Confirm the exam rules, ticking each one. You cannot proceed until all are ticked.
4. Scan your ID, either by capturing a photo with your webcam or uploading an image. Hold the whole front of the document in frame without covering it with your fingers; if it has a back side you will be asked for that too, and if it does not, there is a "my ID document has one side only" option.
5. Click "Start now" to connect to your proctor, then "Start Call".
6. Share your entire screen when prompted — choose the Entire Screen option, not a single window. The compatibility check offers the same choice earlier; picking Entire Screen then makes this step familiar rather than fumbled.
7. The proctor takes over: checks your audio and video, runs the security checks, confirms your personal details — tell them immediately if anything is wrong — and confirms when you may start.

One small kindness in the guidelines worth knowing about: if you finish the check-in steps with a few minutes to spare, "you can take a short break if you wish, though make sure you return promptly for your exact exam start time so your proctor can connect with you." That is the last unsupervised minute you get — use it, and do not spend it revising.

The security checks — what the proctor will actually ask for

Your exam does not start until the proctor is satisfied the regulations can be met. PeopleCert lists the checks, and notes the list is not exhaustive:

• Identity verification, showing your ID via the webcam.
• A 360-degree scan of the room, "including detailed views under the desk and above/below/inside areas of the room that may pose a risk to exam security".
• A view of your monitor, using the available cameras.
• Requests to move or remove items that pose a risk — including guidance on where to place your mobile phone and what view it needs to capture during the exam, where that applies.
• Candidate checks: a close-up view of your sleeves, eyeglasses, ears and hair, to confirm there are no concealed devices. You may be asked to remove headwear briefly for the same reason.

Two provisions here have deadlines attached, which is why they belong on a page you read weeks early rather than on the morning itself. If you require a female proctor for the candidate security check, you must contact PeopleCert at least three business days before your exam. And if you need a reasonable adjustment of any kind, PeopleCert publishes a Reasonable Adjustment Policy in the Support section of its site, with its own process and timeframes — start that early, because it cannot be arranged at check-in.

The checks may also be repeated during the exam if the proctor observes something. The guidelines require you to comply with all check requests "in a reasonable and timely manner", and note that the session is recorded and retained under PeopleCert's privacy policy.

What happens if you do not comply

The escalation ladder is published, and knowing it is genuinely calming, because it makes clear that a minor query is a minor query:

The behavioural rule that follows is simple: comply immediately and without arguing. Move the bottle, tilt the camera, do the second scan. If you believe a request was wrong, take it up with PeopleCert support afterwards — never with the proctor mid-exam, where the only thing you can win is a terminated session.

Inside the paper — the interface and the sixty-minute budget

☺ Like you're 10: Forty questions, sixty minutes — about ninety seconds each. You can skip around, change answers, and flag things to come back to. A pop-up warns you when fifteen minutes are left.

The interface is deliberately plain, and rehearsing it takes about a minute of reading. From the guidelines: a menu on the left lists the question numbers and highlights the one you are on; you move with Next or by clicking a number directly; you flag a question by checking the button beside its number in the left menu, and unflag by clicking again; you answer by clicking the letter of your chosen option, and "you can change your answer by clicking on a different option"; and — the sentence that should change how you play the hour — "You can review a question as many times as you want."

Two further mechanics matter. A pop-up reminds you when fifteen minutes remain. And when you click End Exam, if anything is unanswered you get a warning, because "unanswered questions will be marked as incorrect". Once you confirm, answers are submitted automatically and cannot be changed.

Sol's arithmetic — the numbers that decide your strategy

Three published numbers, and one consequence each.

Put those together and the correct behaviour is not "solve every question in order". It is: answer everything once, quickly, flagging as you go, then spend what is left on the flags. Because you may change answers freely and review as often as you like, an early guess costs you nothing and buys insurance against running out of clock with six blanks at the end.

Where the questions come from — and how that shapes the hour

The official Exam Study Guide publishes a maximum number of questions per topic area, summing to the full forty. This is a maximum per area rather than a percentage weighting, and it lives inside the free study guide PDF rather than on the certification web pages — which is why you will sometimes see this exam described as having no published weighting at all.

The arithmetic that follows is ours, derived from that table rather than a vendor claim: monitoring and SLIs, SLOs and error budgets, and tools and automation account for a maximum of 19 of 40 questions between them — very close to half the paper, and comfortably more than the fourteen you are allowed to lose. Those three are the areas where an extra hour of revision has the highest expected return.

One caveat, stated honestly: the free study guide is v1.1, published 2021, and the current syllabus is v1.2 (October 2024), which added material on generative AI, AIOps, platform engineering, value stream management, observability and progressive deployments. Treat the weighting above as indicative rather than exact, and do not assume the v1.1 maxima carry over unchanged. The good news for a reader of this course is that the v1.2 additions map onto pages you already have — observability and progressive delivery among them.

The difficulty ceiling, and what it means when a question looks too hard

The official study guide states that the exam is built on the Bloom taxonomy and 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 ceiling. There is no Bloom 3 application layer, no design judgement, no "which of these four architectures would you choose".

This is the most useful calibration on the page, and it is officially sourced rather than inferred. It also matches the only published first-hand account: McLeod described the exam as "broad rather than deep in terms of knowledge needed", and reported that a DevOps background helped with general familiarity but was not essential. In the moment, the practical effect is this: if a question feels like it is demanding deep architectural judgement, you have probably over-read it. Re-read it as a definition or a comprehension check, pick the option that matches the vocabulary, and move. Ninety seconds does not permit a second interpretation.

Drill that reflex before the day rather than discovering it during: answer triage is this course's page on reading a distractor quickly, and the mock exams and exam simulator exist to make ninety seconds feel like a normal amount of time rather than a panic.

When something goes wrong

☺ Like you're 10: If the internet drops, the proctor stops your clock and you get your time back. Do not panic, and do not close the browser.

Here is the most reassuring sentence in the whole candidate guidelines document, and it is worth memorising because it is the opposite of how many proctored exams behave: "In case of communication loss during the exam, the proctor will pause the exam timer to prevent any impact on your allotted time. Once the connection is restored you can resume your exam with the same amount of time remaining prior to the interruption."

So a dropped connection is a delay, not a loss. What you should actually do:

• Do not close the tab or the browser. That terminates the session — a much worse outcome than waiting for a reconnect.
• Keep your microphone on. The guidelines require it throughout, and it is how the proctor reaches you when video is struggling.
• Talk to the proctor. They are online for the whole exam specifically in case you need help. Say what you are seeing.
• If you are fully disconnected, log back in with the same credentials, via the same session link or the Connect button in your profile.
• If you cannot get back in at all, contact PeopleCert's technical support, which the guidelines describe as available 24/7/365, immediately — while the session is live or has just ended. A case made at the time is treated very differently from one raised the next day.

Results — provisional now, official in a couple of days

When you click End Exam and confirm, your answers are submitted and "you will receive a provisional result which is subject to verification by PeopleCert", which you can print or export from the screen. Your proctor then confirms the session completed successfully, and you can close the browser.

Then you wait — briefly. PeopleCert's own delivery material describes web-based marking as automated, with provisional results instant and results verified and guaranteed within two days; DevOps Institute's FAQ says you receive your certificate and digital badge by email with your confirmed results shortly after completing the exam. The one published candidate account matches: McLeod reported seeing his score immediately and receiving the official confirmation and certificate a couple of days later. So plan for a number on the day, a certificate within a few days — and note that a session sent for post-exam security review is one of the published reasons results can be delayed.

If you fail

Be honest about what is and is not published here, because this is a place where third-party pages overstate their confidence.

• How to re-book: DevOps Institute's FAQ says to contact whoever you bought the voucher from, and that additional fees may apply to purchase another exam voucher. There is no free-retake entitlement stated for this exam of the kind some other certification families include.
• Waiting period: at least one training partner advertises that there is no waiting period between a first and second attempt. We could not confirm that from PeopleCert or DevOps Institute, and you should not plan around it. Ask PeopleCert directly if the timing matters to you.
• What to do with the result: you are told the score, not a per-question breakdown. That makes the topic table above your best diagnostic — rebuild against the study plan, check whether the gap is actually a baseline gap rather than a syllabus one, drill with flashcards and Know It Cold, and re-test with a fresh mock set rather than the one you have already seen.

Renewal — genuinely contradictory sources

This deserves flagging rather than smoothing over, because three different claims are in circulation and one of them is on a single official page twice.

DevOps Institute's own footnote explains the direction of travel: following the PeopleCert acquisition, "certifications completed on the PeopleCert exam platform will have a validity period of 3 years from their date of issue as per PeopleCert's Continuing Professional Development program." The three-year figure is the one both current official sources state, so it is the one to plan around — but confirm it with PeopleCert before you make a renewal commitment, and treat any partner page claiming a permanent certification as marketing rather than policy.

None of this is the hard part. The hard part is the material — error budgets, the four golden signals, the toil definition, and the vocabulary in the glossary, drilled until a distractor cannot fool you. But procedure is the cheapest place on the whole journey to lose an exam, and the only place you can eliminate risk entirely with an hour of preparation. Work through how to study and the study plan, use the self-check to find what is still soft, keep the readiness checklist beside you, and confirm every volatile number on the two official pages before you book.

↗ PeopleCert — SRE Foundation exam page ◆ DevOps Institute — SRE Foundation ◆ Official Exam Study Guide (free PDF, v1.1)