Final review and exam-day strategy

The last session of the course was short and practical. Noor brought a single page: the ideas Andre should be able to state without hesitation, and the plan for the day itself. "By the final week you aren't learning much new," she said. "You're protecting what you know from nerves, fatigue and the clock." This lesson gives that page in full, then the exam-day strategy: pacing, flagging, reviewing, and what to do before, during and after the exam.

The one-page review

Andre plans to read the page aloud once a day in the final week and to test himself by covering the right-hand column and explaining each domain in his own words. He will also reread the nine traps from lesson 9 and the five causes in his error log, and he will not start any new material.

Pacing

Pacing turns the time limit into a plan. The simplest approach is to divide the exam into a first pass at a steady target pace, leaving a reserve of time for flagged questions and a final check.

The checkpoints are signals, not rules to panic over. If Andre reaches question 40 at minute 75 instead of 68, he is seven minutes behind: he should speed up slightly by flagging hard questions sooner, not abandon careful reading. Being well ahead is also a signal, often of reading too fast.

Flagging and the two-minute rule

The exam interface lets you flag questions to return to later. Noor's rule was simple: if a question is not resolved after about two minutes, choose your best answer now, flag it and move on. Always choose an answer before moving on, because a flagged blank is still a blank if time runs out. Long business case questions are the usual time traps; one stubborn question should not cost three easier ones at the end.

When returning to flagged questions, read the ask again with fresh eyes. Change an answer only if you can name a specific fact in the scenario that you missed or misread the first time. Andre's error log showed one point lost by switching a correct answer on a vague feeling; research on test-taking suggests that changes based on a clear reason are more often right than wrong, while changes based on unease are not.

Managing attention

An exam of two hours or more is long enough for fatigue to matter. Andre's diagnostic set had shown him rushing the last few questions, so he planned a few habits: a slow breath and a stretch at each checkpoint, a sip of water if allowed, and re-reading the ask of any question that felt confusing, because fatigue shows first as misreading. If a run of questions feels hard, remember that some questions are unscored and difficulty varies; one hard section says nothing about the result.

Before the exam

For online proctoring, the rules are strict: a private room, a clear desk, no other people entering, and no reading questions aloud. A proctor watches through the webcam and can end the exam if the rules are broken. Andre plans to choose a testing centre in Calgary to avoid worrying about his home internet connection and a household with two children on a Saturday.

During the exam: the routine for each question

• Read the last sentence and identify what is asked.
• Read the scenario, marking constraints and signal words.
• Predict the shape of the answer.
• Eliminate options that break a constraint or match a trap.
• Choose the option with the fewest assumptions; for multiple response, judge each option separately and check the count.
• If unresolved after about two minutes, answer, flag and move on.

After the exam

For the standard version, candidates normally receive a pass or fail result and a score report within a few business days; beta candidates wait until after the beta closes. The score report shows the scaled score and performance by domain. If you pass, you receive a digital badge and the certification, which for AWS certifications is valid for three years. If you do not pass, AWS requires a wait of 14 days before a retake and charges the full fee again. The domain feedback, read with the usual caution about small sections, and a new error log from memory of the hard questions are the starting point for the next attempt.

Andre had one more task for after the exam, whatever the result: a short note to Lorraine about what preparing had changed in the roadmap. He had already started it. The prioritization was sharper, the business cases had comparison groups and stop conditions, and the governance section had named owners for every system. The exam was in May; the value had begun in November.

A final practice round across the domains

In the last session Noor gave Andre one question from each domain, mixed together as they will be on the exam, and asked him to use the full per-question routine on each.

The point of the round was not only to reach four right answers but to explain why each wrong option was wrong. Noor considered that the real sign of readiness: not just knowing the right answer, but knowing exactly what was wrong with the others.

If things go wrong on the day

Most exam days go to plan, but it helps to know in advance what to do if they do not. If an online session loses its connection, follow the proctor's instructions and contact Pearson VUE support rather than starting again on your own. If a question seems to have no correct answer or a technical fault, choose the best available option, flag it, and use the comment or reporting option if one is offered; dwelling on it costs time for other questions. If anxiety rises, pause for a few slow breaths at the next checkpoint; a few seconds of calm costs far less than a run of misread questions. And if you are unwell on the day, check the rescheduling and cancellation rules in your booking, which usually allow changes up to a set time before the appointment.

Andre added one personal rule: no checking of answers with anyone in the hours after the exam. Whatever the result, the time to review would be when the score report arrived, using the domain feedback and his own notes.