How to Pass the AWS Solutions Architect Associate (SAA) Exam in 5 Weeks

The 5-Week Blueprint

Earning the AWS Solutions Architect Associate certification isn't about memorizing a dump of questions. It's about building a working mental model of AWS services and their trade-offs. In five weeks, you can go from zero to confidently passing the SAA-C03 exam—if you follow a focused, daily practice.

This plan assumes you have some basic IT experience but no prior AWS knowledge. You'll spend roughly 2 hours on weekdays and 4–6 hours on weekends. The goal is not to consume content passively but to actively recall and apply concepts.

Week 1: Foundation & IAM

Start with the AWS global infrastructure, shared responsibility model, and the Well-Architected Framework. Then, dive deep into Identity and Access Management (IAM). This is not glamorous, but it's the bedrock of every architecture decision. Create users, groups, roles, and policies in the console. Understand resource-based policies vs. identity-based policies.

**Real resource:** Adrian Cantrill's SAA course (learn.cantrill.io) dedicates nearly two hours to IAM, including scenario-based demos. He explains why you never use the root account—ever.

By Sunday, you should be able to write a policy that grants cross-account access to an S3 bucket without looking it up.

Week 2: Compute, Storage, and Databases

This week covers the heavy lifters: EC2, S3, EBS, EFS, RDS, Aurora, DynamoDB, and ElastiCache. Don't just read about instance types—launch a t3.micro, configure security groups, and attach an EBS volume. The exam frequently tests choosing between EBS, instance store, and EFS for a given workload, so compare their latency, durability, and cost profiles side by side.

A common trap: thinking DynamoDB is always cheaper. For sporadic, unpredictable workloads, Aurora Serverless v2 might be more cost-effective. The SAA exam loves “least operational overhead” scenarios—practice identifying those keywords.

**Citation:** The official AWS exam guide breaks down domain “Design Resilient Architectures” at 30% weight. Mastering EC2 Auto Scaling, RDS Multi-AZ, and S3 versioning will earn you a large chunk.

Week 3: Networking and Security

Get comfortable with VPCs, subnets, route tables, NAT gateways, VPC endpoints, and the nuances of security groups vs. network ACLs. Build a three-tier VPC from scratch (public, private, database subnets). The hands-on muscle memory will pay off when you encounter “lowest latency” questions requiring a Gateway endpoint for S3, not a NAT gateway.

Security also means KMS, Secrets Manager, and AWS Shield. For the exam, know when to reach for AWS WAF vs. Shield Advanced. Use CloudFront with S3 for DDoS protection and latency reduction—a classic architecture pattern.

Week 4: Serverless, Monitoring, and Cost Optimization

Week four shifts to modern patterns: Lambda, API Gateway, SQS, SNS, Step Functions, and EventBridge. The exam expects you to decouple applications. Learn the difference between a FIFO queue and a standard queue, and why a DLQ (dead-letter queue) is essential.

Monitoring with CloudWatch, CloudTrail, and AWS Config rounds out the week. Cost optimization topics—Savings Plans, Reserved Instances, Spot Fleets—are woven throughout the exam. You don't need deep financial knowledge, just the ability to spot wasteful designs.

**Hands-on:** Deploy a serverless thumbnail generator: S3 upload triggers a Lambda that writes to DynamoDB. This single project touches five core services.

Week 5: Capture Weaknesses and Simulations

No new content this week. Take full-length practice exams under timed conditions. Tutorials Dojo by Jon Bonso is the gold standard—its explanations are deeper than the exam. After each test, review every wrong answer and the distractors. Create a “gap list” of services you still confuse (e.g., SQS vs. Kinesis, Global Accelerator vs. CloudFront). Re-watch specific lessons on those topics.

Schedule your actual exam for the last day of week 5, ideally a Friday. You'll walk in with 4–6 completed practice tests averaging 80+%. The real exam feels easier because you've trained your brain to parse scenario questions.

Final Day: Exam Mindset

Sleep well, review your gap list, not a full course.

During the exam, eliminate obviously incorrect answers first. The AWS exam will try to distract you with plausible but suboptimal options.

Flag questions and revisit. You have 130 minutes for 65 questions—plenty if you manage time.

Remember: the credential isn't the endgame. You're building a foundation for designing real systems. Sapior helps you go from diagrams to production without the infrastructure grind—so once you're certified, you can ship faster.