The final-week plan
Lesson 4 of 4 in Exam Readiness.
Start with the arithmetic, because it governs everything else. 65 questions in 170 minutes is 2 minutes 37 seconds each — and that average has to absorb the ordering and matching items, which read slower than a multiple-choice item, plus whatever review you want at the end. So run the first pass faster than average, at roughly 2 minutes 15 seconds, and bank the difference.
Useful checkpoints on the clock: question 20 by 45 minutes, question 40 by 90 minutes, every question touched by about 148 minutes — which leaves roughly twenty minutes for the flags. The two-pass rule is absolute: nothing is left blank on the first pass, because an unanswered question is scored as incorrect and guessing is free. Flag and move.
The last week is not for new material. It is for finding out which of your beliefs are wrong, under time pressure, and repairing the cheapest ones. Here is a seven-day shape that does that.
Seven days, two mocks, one decision point
- Day −7 · Re-read the exam guide
An hour, end to end, including the in-scope service list and the C02 comparison appendix. You will spot two or three task statements you have been quietly avoiding. Write them down.
- Day −6 · Full mock, cold
65 questions, 170 minutes, no notes, no pausing. The number matters less than the per-domain breakdown and the list of items you flagged.
- Day −5 · Repair the two weakest domains
Weight by weight × weakness, not by discomfort. Domain drills plus the matching modules — and re-do the misses, not the whole module.
- Day −4 · IAM day
Twenty per cent of the exam, and the domain that decides the most questions in other domains. Policy evaluation order, boundaries, session policies, trust policies, cross-account, Access Analyzer.
- Day −3 · Formats and traps
Format drill for ordering and matching until the all-or-nothing grading stops feeling unfair, then the twenty traps as flashcards. These are the cheapest marks left.
- Day −2 · Full mock, timed
Second mock under exam conditions, at the time of day you have booked. Compare the per-domain table with day −6 and check your pacing against the checkpoints.
- Second mock comfortably over 750?
- Day −1 · Light review, logistics, sleep
The reflex tables and the trap list, once. Confirm identification requirements, the test-centre address or the proctoring setup, and your start time. No new material. Stop early.
- Day 0 · Sit it
Two passes. Nothing blank. Flag the ordering and matching items you cannot reconstruct quickly and come back with the banked time.
- Move the date
If the second mock is well under the line and the gap is knowledge rather than pacing, rescheduling costs less than a retake — in money and in the fortnight you would spend waiting.
| Day | Focus | In this course | In the Exam Hall |
|---|---|---|---|
Day −7 | Re-read the official exam guide and the C02 comparison; list the task statements you have avoided. | The SCS-C03 exam and the security map as a refresher. | — |
Day −6 | Cold full mock. Record the per-domain breakdown and every flagged item. | The whole path, for looking things up afterwards. | Full mock exam — 65 questions, 170 minutes. |
Day −5 | Your two weakest domains by weight × weakness. Re-do the misses only. | Stage 14 Detection and stage 15 Incident Response if those were the weak ones. | Domain drill ×2 — up to 15 questions, 39 minutes each. |
Day −4 | IAM, the heaviest domain at 20%: evaluation order, boundaries, session policies, trust policies, cross-account. | Domain drill — D4 · IAM. | |
Day −3 | The two new response formats until the grading stops surprising you, then the trap list as flashcards. | Format drill — ordering and matching, 30 minutes. | |
Day −2 | Second full mock, under exam conditions, at your booked time of day. Check pacing against the checkpoints. | — | Full mock exam, then a pace sprint if the clock was the problem rather than the content. |
Day −1 | One pass of the reflex tables and the trap list. Confirm identification, location or proctoring setup, and start time. Stop early. | Keyword reflexes and the glossary flashcards. | Nothing. Resist it. |
Day 0 | Two passes. Read the last sentence first. Nothing blank. Flag and return. | — | The real thing. |
Two honest notes about the mocks. First, a mock score is a diagnostic, not a prediction — its value is the per-domain table and the list of items you flagged, which tell you where to spend tomorrow. Second, resist re-sitting the same mock until the number looks nice; by the third attempt you are testing recall of the questions rather than knowledge of AWS, and the number stops meaning anything.
And one note about the formats: the all-or-nothing grading on ordering and matching items feels punishing the first time and stops mattering once you have met twenty of them. That is what the format drill is for — meeting them here rather than in the test centre.
Full mock exam — 65 questions, 170 minutes
The standard-form experience, weighted to the C03 blueprint across all six domains, with no feedback until you submit and a scaled score estimate (100–1,000, pass 750) plus the six-domain breakdown the real score report gives you. Sit it twice in the final week: once cold, once at the time of day you have booked. The real exam scores 50 of its 65 questions and does not tell you which, so the mock treats every item as live too.
Pace sprint — 20 questions, 52 minutes
The real per-question pace in one short sitting, stratified across the six domains. Use it when the problem is the clock rather than the content: if you ran out of time on the full mock, three sprints will teach you what 2 minutes 37 seconds of careful reading actually feels like on a security stem that buries the requirement in the third sentence.
Format drill — ordering and matching, 30 minutes
The mode that exists only because of C03. Every ordering and matching item from the bank, back to back, so you practise the two tactics deliberately: anchor the ends and work inward on an ordering item, commit the certain pairs and let elimination finish on a matching item. It also teaches the strategic lesson faster than any amount of reading — these items are worth exactly one mark each, so a quick committed answer plus a flag beats a perfect reconstruction that costs you two other questions.
Domain drill — up to 15 questions, 39 minutes
One domain at a time, with the domain your quiz history says is weakest suggested for you. Domain 4 (IAM) is the heaviest at 20% and the right default if you are unsure. Use drills on days −5 and −4, when you are repairing specific knowledge rather than rehearsing the whole exam.
Reading a mock report honestly
Three numbers matter, in this order. Pacing: where were you against the checkpoints at questions 20 and 40? Per-domain: which two domains cost you the most marks — weight × error rate, not error rate alone? Flag rate: if you flagged more than a dozen items, you are either second-guessing or genuinely short of knowledge, and the flagged list tells you which. A 760 with terrible pacing is more fragile than a 740 with twenty minutes spare.
The morning of
Confirm the identification requirements and the exact start time on the AWS certification policy pages the day before, not the morning of — and if you are testing online, run the system check in advance and clear the room of anything that looks like notes. Then: eat, arrive or log in early, and expect the first three questions to feel harder than they are. That is adrenaline, not the exam. Begin the first pass at pace and let the two-pass plan do its work.
Tool: SCS-C03 mock exam — The SCS-C03 Exam Hall: a blueprint-weighted 65-question mock in 170 minutes with a scaled-score estimate and the six-domain breakdown, a 20-question pace sprint, per-domain drills, and the format drill for the ordering and matching items no other AWS exam on this site uses.
Key terms: Pacing (2.6 minutes per question), Two-pass strategy, All-or-nothing grading, Compensatory scoring, SCS-C03