AWS Certified Solutions Architect – Associate

Overview

SAA-C03 is a scenario exam, not a trivia exam. Almost every question is a short paragraph describing a workload and a constraint — "must survive an AZ failure", "must be the lowest cost", "must not traverse the public internet" — followed by four architectures that all technically work. Your job is to pick the one that satisfies the constraint the question actually emphasises.

That framing matters for how you study. Memorising service descriptions gets you to roughly 60%. The remaining gap is knowing the defaults and limits well enough to eliminate three plausible answers quickly: which services are regional versus global, what fails over automatically and what needs to be designed for, and which option is cheaper once data transfer is counted.

AWS recommends around a year of hands-on experience. That is a reasonable bar but not a hard one — people pass from a strong cloud background plus deliberate lab time.

How to prepare

1. Read the exam guide first, not last. The four domains above are the blueprint, and the appendix lists the in-scope services explicitly. Anything not on that list is not tested; that exclusion alone saves weeks.

2. Build the core mental model. Before drilling services, be fluent in: VPC layout (subnets, route tables, NAT vs internet gateway, security groups vs NACLs), IAM evaluation logic (roles, policies, trust, explicit deny wins), and the S3/EBS/EFS storage split. These three underpin questions in every domain.

3. Learn each service by its decision boundary. For every service, be able to answer: what does it replace, when does it stop being the right answer, and what does it cost to move data in and out. "RDS vs Aurora vs DynamoDB" and "SQS vs SNS vs EventBridge vs Kinesis" are the boundaries that show up most.

4. Actually build two or three things. A three-tier app in a VPC with an ALB, private instances and a managed database will teach you more about resilience questions than any number of flashcards. Free Tier covers most of it — set a billing alarm on day one.

5. Read the Well-Architected Framework pillars. The exam's "best" answer is usually the one Well-Architected would pick. The security and cost-optimisation pillars in particular map almost directly onto the two heaviest domains.

6. Rehearse the timing. 130 minutes for 65 questions is about two minutes each, which is comfortable — but only if you flag and move on instead of arguing with a question. Do at least one full-length timed run before exam day so pacing is automatic.

A realistic schedule

| Weeks | Focus | | --- | --- | | 1–2 | Exam guide, IAM, VPC networking, S3/EBS/EFS | | 3–4 | Compute and scaling, databases, decoupling and messaging | | 5 | Resilience and DR patterns, monitoring, cost optimisation | | 6 | Timed runs, review weak domains, Well-Architected pillars |

Six weeks at 6–8 hours per week is a typical pace for someone already working in tech. Cut it to three or four weeks if you use AWS daily.

Exam-day notes

• You can take it at a Pearson VUE test center or online proctored from home. Online proctoring has a strict clean-desk rule and a room scan; a cluttered desk is the most common avoidable failure.
• Scoring is scaled 100–1000 with a 720 pass mark, and it is compensatory — you do not need to pass each domain individually.
• Some questions are unscored research items, so a couple of odd ones are expected.
• Results are usually available within a few business days, not immediately.
• The certification is valid for three years and can be renewed by passing any higher-level AWS exam.