Final review and next steps

The last session of Gwen's review is planned for the third week of January 2027, a week before Kwame's online exam and about two weeks before Mateo's testing centre appointment. Gwen has already told them what it will cover, and they have the plan on paper now, in November. "The final week is not for learning," she says. "It is for consolidating, resting and arriving calm. And after the exam, whatever the result, there is a plan for that too." This lesson covers the final review, the last week, exam day itself, and what to do with your result.

The final review sheet

In the taper phase, replace broad study with a one-page final review sheet. Gwen asks each candidate to build their own, because writing it is itself a review. It has five parts: the four domains and their weights; a short list of the services in each domain with their one-line jobs; the confused pairs from lesson 8 with deciding differences; the signpost phrases from lesson 2; and the candidate's own top ten mistakes from the mistakes log. Mateo's sheet leads with shared responsibility for EC2, RDS and Lambda, the security pairs he used to confuse, and the Cloud Adoption Framework perspectives. Kwame's leads with the EC2 purchase options, the billing tools and the support plan pattern.

Domain highlights

For Domain 1, be ready to name the six advantages of the cloud, the six Well-Architected pillars, the six AWS CAF perspectives and the 7 Rs, and to explain fixed versus variable cost. For Domain 2, be ready to draw the shared responsibility line for any service, describe IAM users, groups, roles and policies, explain least privilege and root user protection, and give the one-line job of each security service. For Domain 3, be ready to describe Regions, Availability Zones and edge locations and how to choose a Region, and to match needs to compute, storage, database, networking, analytics, AI and integration services. For Domain 4, be ready to match workloads to EC2 purchase options, name the billing tools by their jobs, explain consolidated billing, and describe the pattern of support plans.

The final week

The last week before the exam follows a simple shape. Early in the week, take one last unseen practice set under exam conditions, then review it with the four-step method from lesson 11. In the middle of the week, work through your final review sheet and your mistakes log, and drill the confused pairs. In the last two days, stop practice sets entirely. Read the sheet once a day, sleep well, and prepare the logistics: identification, the route to the testing centre and the time to leave, or for an online exam, the room and the system test. On the day before, do something unrelated to AWS in the evening. Cramming at that point adds stress and very little knowledge.

Logistics deserve a checklist. For a testing centre: your identification, matching your account name exactly; the confirmation email; the address and travel time, with a margin for traffic or snow; and arrival well before the appointment. For online proctoring: the system test passed on the same computer and network; a clear desk and private room; identification ready; other programs closed; and logging in at the start of the check-in window. Mateo plans to drive to the testing centre the weekend before to check parking. Kwame plans to tell his housemates exactly when the exam runs and put a sign on the door.

Exam day

On the day, eat normally, arrive or log in early, and begin with the pacing plan from lesson 10. Read each question with the four-part routine, look for the signpost, eliminate in three passes, and for multiple response mark each option true or false. Answer every question before moving on, flag anything you want to revisit, and keep an eye on the checkpoints. When you finish the first pass, use the review reserve for flagged questions, change answers only for a reason, and confirm none are blank before you submit. When you submit, you may see a pass or fail result on screen; AWS's policies say final results are posted to your AWS Certification account within five business days, and sometimes longer if a result is under review.

After a pass

A pass earns the AWS Certified Cloud Practitioner certification, valid for three years. AWS issues a digital badge you can share on professional networks and add to your résumé, and your certification account lists your benefits, which have included discounts on future exams; check the current benefits page. Keep the certification current before it expires. In November 2026, AWS's recertification options for Cloud Practitioner included completing the AWS Cloud Quest: Recertify Cloud Practitioner course, passing the latest version of the Cloud Practitioner exam, or passing an associate or professional exam, which also recertifies the foundational level. AWS's retake policy also says that once you pass an exam you cannot retake it for two years, so recertification by exam happens near the end of the three-year term.

Gwen's advice on next steps is practical. Mateo plans to aim for the Solutions Architect – Associate exam after the spring cutover, because he will have built the VetLedger and imaging environments by then. Kwame plans to go for the Developer – Associate exam while he refactors BookVet into serverless services. Both plan to keep their study logs: the habits from this course, reading for constraints, separating confused services and reviewing mistakes by type, carry straight into associate-level exams.

After a fail

A fail is information, not a verdict. AWS's policies, checked in November 2026, require a wait of 14 calendar days after a failed attempt before you can retake the exam, place no limit on the number of attempts, and charge the full fee for each attempt. Your score report shows your performance in each domain, which is the starting point for a short, focused plan. Treat the report like a practice-set review: find the weakest domains, return to the mistakes log, and look honestly at whether the problem was knowledge, confusion, reading or timing. Many candidates pass comfortably on a second attempt after two or three weeks of targeted study.

# Earliest retake date after a failed attempt (14 calendar days)
from datetime import date, timedelta
exam_day = date(2027, 2, 6)          # an example date only
retake = exam_day + timedelta(days=14)
print("Earliest retake:", retake.isoformat())

Earliest retake: 2027-02-20

Turning the certification into value at work

A certification is most useful when other people can see what it means in practice. Gwen suggests three things to do in the first month after a pass. First, explain one AWS idea to a colleague who does not work in IT: Mateo plans to walk Andre through why the clinics' booking site stays up when one data centre fails, using the multi-zone design from lesson 5. Second, take on one small piece of real AWS work that uses something from the course, such as setting up a budget alert or reviewing who has access to the production account. Third, write down what you would do differently if you were starting the migration again, now that you know the vocabulary. Each of these turns exam knowledge into working knowledge.

For a team, a group of certified people creates a shared language. Before the move to AWS, the clinic group's conversations about technology tended to happen between Mateo and whoever had a problem. With Lorraine, Hannah and Dr. Kaur all aware of terms such as Availability Zones, shared responsibility and Savings Plans, discussions about cost, risk and uptime can happen in the same room, with the same words. Gwen has seen this in other organizations: a handful of foundational certifications across finance, security and operations often does more for a migration than one more architect.

Keep learning between exams. AWS releases new services and features constantly, and some of today's details will change before the certification needs renewing. A small habit, such as reading the AWS What's New feed once a week or following the AWS blog for the services you use, keeps knowledge fresh without needing a study plan. When recertification comes around, much of the material will already be familiar.

Mateo and Kwame also agree to compare notes after their exams, whatever happens. Kwame's exam comes first, so he plans to tell Mateo how the online check-in went, how the pacing plan held up and which domains felt hardest, without sharing any question content, which the certification agreement forbids. That kind of honest debrief, Gwen says, is the best preparation a colleague can give.

Gwen closes the planning session by giving Mateo and Kwame the same sentence she wrote on the whiteboard in November: concepts, security, technology, billing. "You know what each word means now," she says, "and you know how to read a question about it. Go and show the exam." Their exams are in January and February 2027. Whatever the result, they have a plan for the day after.