AWS Solutions Architect Associate (SAA-C03) in 2026: An Honest Study Plan from Someone Who Actually Took It

What the SAA-C03 actually tests in 2026

I sit the AWS Solutions Architect Associate exam every two years to keep this guide honest. The version Amazon ships in 2026 is meaningfully different from the one most blog posts describe. There are sixty-five questions, the time limit is 130 minutes, and the passing score is approximately 720 out of 1000 (AWS does not publish exact mappings, but the curve has been stable for three years). The four content domains and their weights as of the current exam blueprint are: Design Secure Architectures (30%), Design Resilient Architectures (26%), Design High-Performing Architectures (24%), and Design Cost-Optimized Architectures (20%).

The thing that has changed the most in 2026 is the volume of AI-and-data-centric questions. Expect three to six questions that involve Bedrock, SageMaker, OpenSearch, or Glue. These were rare in earlier versions and are now reliably on every form.

Who this guide is for, and who it is not for

This plan assumes you have at least some hands-on AWS experience — even six months of touching AWS in a job, internship, or serious side project — and roughly twenty hours per week to study. If you are completely new to the cloud, do the AWS Cloud Practitioner first; jumping straight into SAA without any AWS context is the most common reason I see people fail.

If you already have a year of professional AWS experience, you can probably compress this six-week plan into three or four weeks. Adjust the daily hours up rather than skipping topics — the exam covers breadth, and breadth is exactly what shortcuts erode.

Week 1: The foundations you cannot skip

Spend the first week on IAM, VPC, and the EC2-EBS-S3 triangle. These three areas show up in roughly forty percent of exam questions, often woven into scenarios that look like they are testing something else. If you do not have a clean mental model of how an IAM policy is evaluated, what a security group can and cannot do that a NACL can, and how S3 storage classes price out, you will lose easy points all the way through the test.

Concrete daily structure: ninety minutes of video lectures (Stephane Maarek's course on Udemy is the most up-to-date paid option, AWS Skill Builder's free Cloud Quest is a solid no-cost alternative), sixty minutes of hands-on labs in the AWS console, and thirty minutes of review notes at the end of each session. Build a real VPC with public and private subnets by hand at least twice during this week — typing the steps into the console is what makes them stick.

Week 2: Storage, databases, and the "what is the right service" muscle

Week two covers the data layer. RDS, Aurora, DynamoDB, ElastiCache, EFS, FSx, Storage Gateway, and the various S3 features (Lifecycle, Replication, Object Lock, Intelligent-Tiering). This is the week that builds the single most-tested skill on the exam: given a scenario, pick the right service.

The pattern that wins exam points is to read each scenario looking for three specific signals — access pattern (read-heavy, write-heavy, mixed), latency requirement (microseconds, milliseconds, seconds), and durability requirement (eleven nines, regional, global). Those three signals collapse the candidate services to one or two on almost every question. Drill that pattern explicitly during this week with practice questions.

Week 3: Compute, scaling, and high availability

Week three is EC2 in depth, plus Lambda, Fargate, ECS, EKS, Auto Scaling, ELB (ALB, NLB, GWLB), and the Route 53 routing policies. The exam loves edge cases here. Learn the difference between target tracking, step, and simple scaling. Learn what an ALB can do that an NLB cannot, and the situations in which only an NLB will work. Learn the seven Route 53 routing policies in enough depth that you can pick the right one in fifteen seconds.

Hands-on this week: deploy a containerised application to ECS Fargate with an ALB in front of it, then break it on purpose and watch the health checks. Then redeploy the same application to Lambda and notice what becomes simpler and what becomes harder. The exam asks the comparison directly.

Week 4: Security, monitoring, and the "least privilege" mindset

Week four is KMS, Secrets Manager, Parameter Store, GuardDuty, Inspector, Macie, Security Hub, Config, CloudTrail, CloudWatch, and the cross-cutting question of how IAM policies, resource policies, and SCPs interact. About a third of the exam questions touch this material, and they are the questions where careful reading matters most.

The mental model that helps here is to separate "identity-based" controls (what an IAM principal is allowed to do) from "resource-based" controls (who is allowed to touch this resource) from "organisation-wide" controls (SCPs and AWS Organizations guardrails). Most security questions on the exam are testing whether you understand which layer would solve a given problem.

Week 5: Cost optimisation, migration, and the integration questions

Week five covers the smaller domains — Savings Plans versus Reserved Instances versus Spot, the migration services (DataSync, Snow family, Database Migration Service, Application Migration Service), and the integration glue (SNS, SQS, EventBridge, Step Functions, Kinesis). Cost optimisation only weighs twenty percent on the blueprint, but the questions are usually free points if you have read the pricing pages once.

This is also the week to start full-length practice exams. Tutorial Dojo's six SAA-C03 practice exams are the gold standard; do them in timed mode, score them, and then review every wrong answer until you understand why the right answer is right and the other three are wrong. The review is where the score moves, not the practice itself.

Week 6: Practice exams, weak-area drilling, and the final week

Week six is where most candidates underperform. The temptation is to keep cramming new material; the right move is to stop adding material and instead drill your weakest two domains until your practice exam scores stabilise above 80%. If you are scoring below 75% on practice exams in week six, push the real exam back by a week. The reschedule fee is far cheaper than retaking the exam.

Two days before the exam, stop doing practice questions and instead read your own notes from weeks one through five. Sleep, hydration, and a calm test-day morning are worth more than any additional study hour at this point.

What to do on exam day

Take the test in the morning if your schedule allows it. Bring a government photo ID exactly as your name appears in the AWS Certification portal — name mismatches are the single most common reason people get turned away. If you are testing remotely with Pearson VUE, have your testing room cleared an hour in advance and plan for the proctor's identification check to take fifteen to twenty minutes.

Use the "flag for review" feature aggressively in the first pass. Spend no more than ninety seconds on any question the first time through; flag the hard ones, finish the easy ones, then come back. Most candidates leave time on the table by getting stuck on three or four questions in the middle.

What happens after you pass

You will get a provisional pass-or-fail result on screen at the end of the exam, and an official badge in your Credly account within five business days. The certification is valid for three years. The natural next step is the Solutions Architect Professional, but I usually advise candidates to spend at least a year doing real architecture work before attempting the Pro — the questions assume operational experience the Associate exam does not.

If you find an error in this guide, or AWS changes the blueprint and I have not yet updated, please email me at priya@wikicounsellor.com. The certification space moves fast and I would rather hear about a stale paragraph than leave it up.