Exam Day — What to Expect

Almost nobody fails the DOP-C02 because of the thing they were afraid of. They fail because a driving licence had quietly expired, because the name on the AWS booking didn't match the passport, because a corporate laptop refused to run the proctoring software twenty minutes before the slot, or because they spent forty minutes on the first fifteen questions and then hit the fatigue wall at question fifty with two hours already gone. This page is the procedural half of your preparation — what booking actually involves, which of the two delivery methods you are choosing between and how differently they behave, what may be on the desk, how the paper itself moves, what the 180-minute clock forces you to do, and what to do when something goes wrong. Read it once now, and again the week before you sit.

What kind of exam day this actually is

☺ Like you're 10: Three hours, seventy-five questions, pick the best answer from a list. Nothing to build, nothing to look up, nothing to type except your answers.

Getting the category of exam right is the cheapest correction you will ever make to your preparation, because it changes what you practise. The DOP-C02 asks you to choose between plausible AWS designs under time pressure. It never asks you to build one. That single fact determines the shape of the whole day: no environment to configure, no tooling to warm up, no scratch work that survives past the question you are on — just reading, deciding, and the clock.

Two question types, and only two. AWS's own DOP-C02 exam guide — version 1.6 at the time of writing — states them plainly: multiple choice, which has one correct response and three distractors, and multiple response, which has two or more correct responses out of five or more options. The same guide states that the exam contains 65 questions that affect your score plus 10 unscored questions that do not, and that the unscored items are not identified — so there is no clever way to spend less effort on them.

For the format, the scoring mechanics and the six domain weights in full, the sibling page The DOP-C02 Exam is the reference. This page assumes you have read it, and concentrates on the day itself.

Booking — the decisions that shape the day

☺ Like you're 10: You book it through your AWS account, and you have to choose: go to a special exam room, or take it at home with a webcam. Those are two very different days.

You register and pay through your AWS Certification account, which hands you off to Pearson VUE for scheduling and delivery. At that point you make the choice that determines most of what follows: a physical testing centre appointment, or OnVUE online proctoring from a private room of your own. Both are legitimate, both are represented in the published candidate accounts, and they are not equally easy for everyone.

Test centre or OnVUE — pick deliberately, not by default

Most candidates pick whichever is fewer clicks and discover the consequences on the day. Choose instead on the honest answer to one question: which risk is smaller for you — the risk of your own room and network, or the risk of the journey and an unfamiliar environment?

Both routes appear in the published write-ups. Rishab Kumar sat DOP-C02 in person at a Pearson VUE centre. Tolu Nimi, Suraj Solanki and Irene Bonso all sat it remotely under OnVUE. Nobody reports that one route is easier than the other. What the accounts do show is that the OnVUE failures are environmental and the centre failures are logistical — which is what you would expect, and exactly what you can plan around.

The numbers you are booking against

AWS publishes the commercial and format facts on the official DOP-C02 certification page: 180 minutes, 75 questions, 300 USD, delivery at a Pearson VUE testing centre or as an online proctored exam, availability in English, Japanese, Korean and Simplified Chinese, and a certification valid for 3 years. Note where those facts live: the duration and the price are on the product page, not in the exam guide, which states neither. Prices also vary by country and by local tax treatment.

↗ AWS official DOP-C02 certification page

Language, accommodations, and the reschedule window

• Language is chosen at booking, and it deserves a moment's thought rather than a reflex. The exam is offered in English, Japanese, Korean and Simplified Chinese; if one of the others is your first language, sitting in it removes a genuine source of fatigue from three hours of dense scenario reading.
• Accommodations must be requested and approved before you schedule, not on the day. AWS operates an exam-accommodations process that covers, among other things, additional time for candidates taking the exam in a language that is not their first. Eligibility rules and what each accommodation grants do change, so look them up in your AWS Certification account and apply early — approval is not instant.
• Learn the reschedule and cancellation cut-off the day you book. There is a deadline before your appointment after which changing or cancelling costs you the fee, and it is stated in your Pearson VUE confirmation. Read it while you are calm, not while you are trying to move an appointment at midnight.
• Book a slot your life can actually protect. Three uninterrupted hours plus check-in is a longer block than most people plan for; at home it means three hours during which nobody else enters the room. Irene Bonso solved this by booking a midnight slot and shifting her sleep schedule the day before — a legitimate tactic, provided the shift is deliberate rather than accidental.

Identity — the check that ends more attempts than any technical fault

☺ Like you're 10: You need a real ID card made by a government, with your photo on it, that hasn't run out — and the name you booked with has to be spelled exactly the way the card spells it. A photo of the card on your phone doesn't count.

The identity check happens before anything else and it is binary. There is no appeal at the desk, no "I can email you a scan," no colleague vouching for you. If the ID does not satisfy the policy, the proctor or the centre staff cannot let you start, and you have burned both the attempt and the fee. Treat it with the seriousness you would give a boarding pass.

What the ID has to satisfy

• Government-issued. Passport, driving licence, national identity card, residence permit. A student card, an employee badge, a club membership or a bank card is not an identity document for this purpose.
• Carries your photograph, and in most programmes your signature too. The staff member or proctor compares your face against the card on camera or in person.
• Currently valid. Expired is rejected, however recently. Check the expiry date the week you book, and again the night before.
• The physical document. A photo of it, a scan, a PDF, or a digital ID in a phone wallet is not the document the policy asks for — and at home your phone is supposed to be out of reach for the duration anyway.
• Name spelled exactly as your booking spells it. This is the one that catches people, and it gets its own section below.

The name-match rule, which trips up more people than anything technical

The name on your AWS Certification profile — the name that flows through to the Pearson VUE booking — must match your ID exactly. Not "close enough." If you registered as Sam Rivera and your passport says Samuel J. Rivera, fix the profile — and fix it weeks ahead, because a name change may need a support ticket and human review rather than a form submission. The same applies to a recently changed surname, a middle name your ID includes and your profile omits, a hyphen that got dropped, and diacritics your keyboard did not produce when you signed up.

The failure mode here is almost always self-inflicted and entirely preventable. Nobody arrives at check-in intending a mismatch; they arrive having never compared the two documents side by side.

The pre-flight, run a week early rather than an hour early

☺ Like you're 10: Test everything a week before, on the exact computer and in the exact room you'll use — not twenty minutes before it starts.

Everything in this section is free, and every item on it is the kind of thing candidates otherwise discover at the worst possible moment. Do it once at T−7 days and once again at T−1 day.

If you booked OnVUE: run the system test properly

Pearson VUE provides a system test from your exam dashboard. The rule that makes it useful is that a system test only tests what you actually test with: run it on the exact machine, in the exact room, on the exact network, at the same time of day as your booked slot. A system test run on the office Wi-Fi at lunchtime tells you nothing about your kitchen at midnight.

What it is really checking is that the OnVUE application can start, that it can see your camera and microphone, that it can take over the screen, and that your connection is good enough to stream. Failures cluster into a short list: an OS update that changed camera permissions, a security agent that blocks the application, a VPN that must be off, a browser that is no longer supported, and a webcam that a driver update quietly disabled.

Measure your own link, not just theirs

Online proctoring streams your webcam and screen continuously for over three hours, which is a modest but relentless load. The published bandwidth minimum is small; what actually hurts is instability. These are ordinary commands on your own machine and none of them touch the exam:

ping -c 20 1.1.1.1

curl -o /dev/null -s -w 'dns=%{time_namelookup}s connect=%{time_connect}s ttfb=%{time_starttransfer}s total=%{time_total}s\n' https://aws.amazon.com/certification/

mtr --report --report-cycles 50 1.1.1.1

A single sample proves nothing. What you want to know is whether your link drops packets during a window as long as your exam, at the hour you booked:

# log one latency sample per second for 30 minutes, then count the drops
for i in $(seq 1 1800); 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 "PACKET-LOSS"}'
  sleep 1
done | tee ~/exam-link-check.log

grep -c 'PACKET-LOSS' ~/exam-link-check.log

If that count is anything but zero, fix it before exam day rather than hoping: plug into ethernet, move the router, or move the slot. On the day itself take the obvious precautions — close every other application, pause cloud sync and backups, disable automatic updates, plug the laptop into mains power, and ask the household to stay off video calls for the duration.

If you booked a testing centre

• Find the centre before the day. Test centres are frequently inside office buildings, training providers or business parks with unhelpful signage. Know the entrance, the floor, and where you are allowed to park.
• Plan to arrive at least thirty minutes early, and treat the lateness rule as unforgiving. The permitted tolerance is stated in your confirmation; beyond it you can be recorded as a no-show and lose the fee.
• Bring only your ID and the smallest amount of everything else. Bags, phones, watches, jackets and drinks go into a locker. Anything you carry in is one more thing to store.
• Ask what the centre provides when you check in — note board and pen, earplugs, noise-cancelling headphones, a locker key. Ask before you sit down rather than raising your hand at question thirty.

The night before

Nothing in this list is clever, and every item on it is something a real candidate has got wrong.

• Put the ID somewhere you cannot fail to find it, having already checked the expiry date and the spelling.
• Clear the desk completely if you are sitting at home, and remove anything printed from the walls in shot. Do it the night before so that check-in is not also a tidying exercise.
• Unplug the second monitor. Not "switch it off" — unplug it and turn it away. "It was switched off" is a sentence people say after their session has been terminated.
• Charge everything and plug the laptop in. Three hours plus check-in is longer than a lot of batteries and longer than most people think.
• Sleep, and stop studying. Every published account that mentions the night before says the same thing: cramming the evening before a three-hour reading-endurance exam trades a small amount of recall for a large amount of stamina. That is a bad trade on this exam in particular.
• Eat properly and moderate the caffeine. You are planning for three hours without a break; front-loading coffee an hour beforehand is a decision your bladder will make you regret at question forty.

Testing-centre day, step by step

☺ Like you're 10: You arrive early, put everything you own in a locker, show your ID, sign your name, and someone walks you to a computer that already has your exam on it.

The centre route trades your environment for theirs. That is usually a good trade — their machine is maintained for this purpose and their network is not shared with your household — and the price is that the whole day has a travel component and a strict clock at the front of it.

Expect roughly this order. You arrive, ideally thirty minutes early. You present your ID at the desk. Staff check it against the booking, capture a signature and usually a photograph, and in many centres a biometric such as a palm scan. Everything you brought — phone, watch, wallet, bag, jacket, drink, notes — goes into a locker, and you keep the key. Staff explain the rules, hand over whatever the centre provides in the way of a note board and pen, walk you into the exam room, and seat you at a machine that is already showing your name. You confirm it is yours, work through the tutorial and non-disclosure screens, and the exam begins.

Things worth knowing before you sit down at a centre

• The note board is not guaranteed and it is not yours. Where a centre issues an erasable board and pen, it is surrendered at the end and it is a conduct matter to take anything out of the room. Never plan a strategy that depends on writing — practise as though you have none, and treat a board as a bonus.
• Ask for earplugs or noise-cancelling headphones at check-in if the room is shared. Most centres have them. Asking at question forty means standing up and attracting a proctor's attention for no gain.
• Bathroom breaks are usually possible, and the clock keeps running. You raise your hand, staff acknowledge you, you sign out and back in, and every one of those minutes comes out of your 180. Budget for zero and treat a break as an emergency measure.
• Cameras and staff are watching the room continuously. The rules about looking away, muttering, and anything appearing on the desk apply just as strictly as they do at home.
• If the machine misbehaves, raise your hand immediately. Do not attempt to fix it. Centre staff can restart a session, and the sooner they start the fewer of your minutes are involved.

OnVUE at home, step by step

☺ Like you're 10: You start a program on your computer, take photos of your ID and your desk with your phone, then wait for a real person to look through your webcam, check the room, and unlock the test.

The at-home route removes the journey and hands you the entire responsibility for the environment. The check-in itself is longer and fussier than most people expect, which is precisely why it opens well before your slot.

The check-in sequence

The exact flow is revised from time to time, so follow the on-screen instructions rather than anyone's write-up — including this one. At the time of writing, the shape is: you launch the OnVUE application from your exam dashboard a set period before your appointment. It runs a system check and asks for camera, microphone and screen-share permissions. You are then asked to photograph, usually with your phone, your ID and your workspace — typically a headshot, the front of the ID, and several views of the desk and the area around it. Your phone then goes out of reach for the duration. You wait in a queue for a live proctor. The proctor verifies you, asks you to pan the webcam around the room and under the desk, confirms the rules, and releases the exam. The timer starts then, and not before.

The queue is the part people forget. It is on their side of the clock, not yours, which is exactly why beginning check-in at the earliest permitted moment rather than five minutes before your slot is the difference between a calm start and a frantic one. The tolerance for arriving late is stated in your confirmation email — read it, because past it you can be recorded as a no-show and lose the fee.

What may and may not be on the desk

The default is a completely clear desk: your computer, one display, keyboard, mouse, and nothing else. Everything else is an exception, not a right.

Two of those surprise experienced engineers every time. Your own paper is not permitted at home, so if your study habit is "sketch the architecture first," you need to break it in practice rather than discover it at question three — Tolu Nimi's write-up flags exactly this, noting that at home you likely will not be allowed pen and paper. And headphones are usually prohibited, which means the proctor speaks to you through your speakers, in a room quiet enough for you both. Confirm both against the current policy; permitted-items lists are exactly the kind of thing that gets revised.

Breaks: plan the three hours as three hours

The safe planning assumption for an online-proctored AWS exam is that there are no breaks and the clock never stops. Whatever the current policy says, standing up and walking out of frame without clearing it first is the single fastest way to have a session flagged. Handle it before check-in: use the bathroom, have the permitted drink already on the desk, and moderate what you drank in the preceding hour. If something genuinely unavoidable happens, tell the proctor first and comply with whatever re-verification they ask for afterwards.

If you disconnect

It happens, and it is survivable. Plan for this behaviour: the exam timer keeps running, your answers so far are held server-side rather than on your laptop, and the correct move is to reconnect immediately by relaunching from the same dashboard link. Expect the proctor to re-verify you and possibly repeat the room scan. If you cannot get back in at all, contact Pearson VUE support using the number or chat link in your confirmation email straight away — a case opened during or immediately after the session is taken far more seriously than one opened the following day. Note the times. If a fault genuinely cost you minutes, that record is the only evidence you will have.

The screen in front of you

☺ Like you're 10: A long paragraph of story, then a question, then four or five choices. A button to mark the ones you want to come back to, a counter, and a clock. That's the whole screen.

Interface fumbling in the first five minutes is pure waste, and it is avoidable because the interface is simple. There is a question, a set of options, navigation, a Mark for Review control, a question counter and a countdown. That is essentially all of it, and it looks the same at a testing centre as it does at home.

The two question types, and what each costs you in time

A multiple-choice item gives you one correct response and three distractors. A multiple-response item gives you five or more options and asks for two or more correct ones, and the stem tells you how many to pick. The practical difference is that a multiple-response item is not one decision, it is several. Treat it as all-or-nothing: the standard position across AWS certification exams is that every correct response must be selected for the item to count, with no partial credit — so getting two of three right earns exactly what getting none right earns.

That asymmetry is why multiple-response items dominate the flagged list of nearly every candidate who writes one up. Tolu Nimi's account reports flagging 25 of the 75 questions, and notes that many of the flagged ones were multi-select — "choose 3 of 5 or 6." Treat every "choose TWO" or "choose THREE" as a natural place to slow down slightly and a natural candidate for the flag, and let the single-answer items carry your speed.

Mark for Review, and the review screen

Navigation is free: you can move forwards and backwards through the paper, change answers, and use the Mark for Review control to build a list you can return to. Before you submit, the review screen shows every item with its answered, unanswered and flagged state, and lets you jump straight to any of them.

Three rules make that machinery pay:

• Always record an answer before you flag. A flagged blank and a flagged guess are not the same risk. The exam guide is explicit that unanswered questions are scored as incorrect and that there is no penalty for guessing, so a blank you never got back to is a guaranteed zero while a guess is a chance already banked.
• Flag for a reason you could say in three words. "Down to two." "Unfamiliar service." "Misread the qualifier." Anxiety will happily flag half the paper if you let it, and a review pass with thirty flags is not a review pass.
• Reserve real time for the review screen. Five minutes is not enough to revisit fifteen flags. The pacing table below reserves twenty.

The fuller protocol — when to guess now versus flag, and how to decide whether a second-look change is evidence or nerves — is worked out in detail on Answer Triage & Elimination. Do not learn it on exam day.

What is not on the screen

Worth saying explicitly, because a surprising number of candidates arrive expecting one of these:

• No documentation. No AWS docs, no allowlist, no search. The DOP-C02 is entirely closed-book — which is exactly why No Docs Map — Closed Book exists as a page in its own right.
• No terminal and no console. Nothing to run, nothing to inspect, no AWS account.
• No calculator and no digital scratchpad. Any arithmetic — cost comparisons, retention windows, instance counts — happens in your head.
• No indication of which items are unscored. Ten of the seventy-five do not count and you cannot tell which; the only sane response is to treat all seventy-five identically.
• No per-question feedback, and no running score. You will not know how you are doing at question fifty, and trying to estimate it mid-exam is a way of spending attention you need elsewhere.

The clock — the arithmetic that drives every tactic

☺ Like you're 10: Three hours divided by seventy-five questions is about two and a bit minutes each. That sounds like plenty until you see how long the questions are.

Every genuine account of this exam converges on the same adversary, and it is not obscurity. It is length. Question stems run to full paragraphs, options run to full sentences, and the arithmetic that results is the single number that should shape how you practise: 180 minutes across 75 questions is 2.4 minutes each.

Simon Mafany does the arithmetic out loud in his write-up, and it is the best single sentence published about DOP-C02 pacing: "Questions are very lengthy, and you have practically 2.4minutes to read a question, understand it, read the options, analyze them, eliminate distractors, before selected the best option." Read that as a job description rather than a complaint. Six distinct activities, 144 seconds, seventy-five times in a row.

The checkpoint table — the only pacing tool you need

Averages are useless mid-exam because you cannot compute one under pressure. What you can do is glance at a clock and a counter and know instantly whether you are ahead or behind. Memorise one of these rows — the sixty-minute one is enough — and the rest takes care of itself.

Notice what the published accounts do with that budget. Tolu Nimi began his flagged review with 45 minutes left, having flagged 25 items — a generous reserve, and he needed it. Suraj Solanki finished his first pass with about 15 minutes for review, and describes trusting his first instinct on the flags rather than relitigating them. The Qiita candidate @Rabbit_booK finished a first pass with 20 minutes left and could not get through every flagged question — which is exactly the failure mode the twenty-minute reserve above is sized against. At the other end, @Crowncrow completed the whole thing including review in around 100 minutes of the 180 and scored 815. There is no single correct pace. There is only the difference between a pace you chose and a pace that happened to you.

The fatigue curve is real, and it arrives earlier than you expect

This is the part practice questions do not teach you, because nobody drills seventy-five long scenarios in one unbroken sitting unless they deliberately decide to. Two independent accounts describe the same curve at almost the same point.

Simon Mafany: "After the first hour, I felt tired already but still had almost 2/3 of the questions. At the end of the se[cond] hour, I almost lost my concentration." Rishab Kumar, sitting at a testing centre rather than at home, describes struggling with focus "after the 30-35th question" — roughly the same place, reached by a different route. Both passed. Neither was surprised by the exam's difficulty so much as by their own reading stamina.

Three things follow, and they are the highest-value paragraph on this page:

• Practise the endurance, not just the content. A ninety-question practice set worked in three sittings across a week builds knowledge. A seventy-five-question set worked in one unbroken 180-minute block builds the thing that actually fails at question fifty. Do at least two full-length timed sittings before the real one — that is what the five mock exam sets on this site are sized for.
• Spend your freshest hour on your fastest reading, not your hardest thinking. The first pass is where speed compounds. Do not use hour one to wrestle a single expensive item to the ground; use it to bank the thirty questions you can answer confidently, and let the wrestling happen in the review block when you know exactly how much time you have for it.
• Have a physical reset you can perform in your seat. You cannot stand up. You can look away from the screen for ten seconds, breathe deliberately, roll your shoulders, and reread the stem from the beginning. Ten seconds spent resetting at question fifty is cheaper than four minutes spent reading the same paragraph three times because none of it went in.

Never leave a blank — and what the passing score actually means

The exam guide states that unanswered questions are scored as incorrect and there is no penalty for guessing. That makes the rule absolute: at 150 minutes, everything gets an answer, including the items you would rather have thought about longer. A considered guess between two survivors beats a blank every time, and it beats it by exactly the amount of elimination you managed.

It also matters that scoring is compensatory. The guide is explicit: you do not need to achieve a passing score in each individual domain, only to pass the exam overall. A weak domain is survivable. A pattern of blanks is not.

Rishab Kumar's 756 is the argument in one number. He passed by six points of scaled score, on an exam he describes going into with no specific preparation. Nobody knows in advance which side of that line they are on, which is why the discipline is absolute rather than situational: at 150 minutes, every item has an answer, and the twenty minutes at the end belong to the flags and to nothing else.

When something goes wrong

☺ Like you're 10: If the person watching says something, stop and listen — it's almost never an accusation. If the computer breaks, tell someone straight away instead of trying to fix it yourself.

Most things that go wrong on exam day are recoverable, and the recovery depends almost entirely on responding fast and calmly rather than on being clever. Here is the whole decision tree.

And then, whatever it was, get back to the question. The clock did not pause for your feelings, and replaying an interruption for the next ten minutes costs you four or five questions you would otherwise have answered.

The service you have never heard of

☺ Like you're 10: The list of AWS services the exam guide gives you is a bit out of date. Some things on the real test aren't on the list, and something on the list has quietly disappeared. Here's how to not panic when it happens.

This is the one genuinely surprising thing about DOP-C02 exam day. It is documented rather than folklore, and it is far better read now than discovered at question nineteen.

The exam guide ends with an appendix listing in-scope AWS services. That appendix has drifted from the live exam in both directions, and both directions are checkable against AWS's own documents:

• AWS CodeCommit was dropped. The launch-era v1.0 exam guide listed CodeCommit among the in-scope developer tools and named it in a task statement. The current v1.6 guide does not mention CodeCommit anywhere — not in the service list, not in any task statement.
• AWS's own free sample questions have not caught up. The official DOP-C02 sample questions PDF still opens with a CodeCommit scenario.
• AWS CodeConnections is not in the v1.6 list at all — and candidates report meeting it on the live exam. The Qiita author @boloyome wrote up his June 2026 sitting under a title that translates as "the story of meeting a service I'd never heard of when I took the AWS DOP": CodeConnections appeared repeatedly, he had never encountered it, and he was unsettled to find it absent from the official service reference. Independently, Irene Bonso lists AWS CodeConnections among the topics that came up frequently on her sitting.
• Some listed services have moved on without the list. The v1.6 appendix still names AWS CodeStar, AWS OpsWorks and AWS Proton — services AWS has since wound down or closed to new customers — and refers to "AWS Fault Injection Simulator," which AWS has since renamed Fault Injection Service. Simon Mafany's write-up devotes a section to exactly this, naming OpsWorks, CloudWatch Events and CodeStar as retired or renamed services still sitting in the exam guide. Irene Bonso and the DEV Community author Camille both list Fault Injection Service among the topics they encountered.

The guide itself is honest about this: it says the service list is non-exhaustive and subject to change. Read the appendix as a floor, not a ceiling. A reader who studies only the v1.6 list will over-study one service the current guide has dropped, and will meet at least one the list does not contain.

After you click End Exam

☺ Like you're 10: You answer a short survey, and then usually nothing happens. The result comes by email later — sometimes the same evening, sometimes the next day.

This is the part that catches people emotionally rather than procedurally, so it is worth knowing in advance. On many AWS professional-level sittings, no score appears on the screen. You submit, you answer a short post-exam survey, the session closes, and you are left holding three hours of adrenaline and no verdict.

The published accounts show exactly how variable the wait is. Irene Bonso reports that the result did not appear on screen and the pass email arrived about sixteen hours later. @Crowncrow reports the results email arriving the same evening as his sitting. AWS publishes its own expected turnaround, measured in business days rather than minutes — look up the current figure on the AWS Certification site so that a perfectly normal wait does not read to you as bad news. Whatever the number says, plan not to make any decisions that evening.

Retakes, validity, and the thing to do while it is fresh

• There is no bundled free retake. Unlike some hands-on certifications, each DOP-C02 attempt is a fresh full-price registration. Budget accordingly rather than assuming a second attempt is cheap.
• AWS enforces a waiting period between attempts — published as 14 days at the time of writing. Confirm the current figure in AWS's exam policies before you plan around it, and note that the wait starts from the attempt, not from when the result lands.
• Passing typically unlocks certification benefits in your AWS Certification account, historically including a discount toward a future exam. What is on offer changes; look in your own account rather than trusting a blog post.
• The certification is valid for 3 years per the AWS product page, after which you recertify. Put the expiry in a calendar the week you pass, with a reminder six months ahead — three years is exactly long enough to forget.
• Write your own notes within 24 hours — about the experience, never the questions. Which domains felt heaviest, where your pacing slipped, which service names you could not place, what you would do differently at check-in. That memory decays fast, it is the raw material for a retake or for helping a colleague, and it is the honest version of what every account cited on this page did.

None of this is the hard part. The hard part is the six domains, the service comparisons, and the reps — the study plan, Know It Cold, Answer Triage & Elimination and five full-length mock exams under a real clock. But procedure is the cheapest place on the whole journey to lose an exam, and the only one you can eliminate outright with an hour of preparation the week before. Work through how to study for the plan, read the field notes for what other candidates actually met, and confirm every volatile number on the official AWS certification page before you book.