AWS SAA-C03 Study Plan — A Practical 6-Week Path Through Secure, Resilient, High-Performing, and Cost-Aware Design

Use this plan if you want a disciplined path through SAA-C03 instead of hopping randomly between AWS services. The exam rewards architecture judgment, not isolated memorization, so each week should combine reading, one small hands-on build, and one timed drill set.

Before you start

Keep these three things open through the whole cycle:

• the official exam guide on the resources page
• this guide’s domain chapters
• a running miss log where you record the rule you missed, not just the question ID

The study loop is simple: read the domain -> build one small pattern -> drill weak areas -> review every miss -> repeat with mixed sets.

Use AWS official prep assets deliberately

AWS’s current certification page points candidates to a 4-step prep flow, the live exam guide, exam-style practice assets, and the AWS service short-names list. Use those resources in the right order instead of clicking them all at once:

• start with the live resources page and the official exam guide
• use AWS Skill Builder and official exam-style practice only after you already know the domain structure
• review the AWS service short names list before mocks so answer choices feel familiar instead of noisy
• re-open the AWS certification and policy pages in the final week, not only on booking day

Weekly rhythm that keeps the plan realistic

The miss log matters more than the raw score. Record the architecture rule you missed, such as “gateway endpoint before NAT for private S3 access,” not just “question 27 wrong.”

Repeatable study loop

    flowchart LR
	  R["Read one focused lesson"] --> B["Build or sketch one pattern"]
	  B --> D["Run a short timed drill"]
	  D --> M["Write the architecture rule you missed"]
	  M --> O["Re-open only the matching lesson or appendix"]
	  O --> N["Next domain or mixed set"]

What to notice:

• the miss log stores rules, not only scores
• the re-open step should be narrow and targeted
• this loop keeps you from rereading the entire guide every time a mock exposes one weak area

Week 1: secure architectures

Start with 1. Secure Architectures, then work through 1.1 Secure Access, 1.2 Secure Workloads & Applications, and 1.3 Data Security Controls.

Hands-on goal:

• create one IAM role flow that uses role assumption rather than long-term keys
• compare a private S3 access path through a gateway endpoint versus internet egress
• configure or review one encryption-at-rest and one encryption-in-transit pattern

Week 2: resilient architectures

Work through 2. Resilient Architectures, 2.1 Scalable & Loosely Coupled, and 2.2 Highly Available & Fault-Tolerant.

Hands-on goal:

• sketch one event-driven design with SQS or EventBridge between tiers
• compare Multi-AZ, read replica, and multi-Region decisions for one sample workload
• map one backup-and-restore, pilot-light, and warm-standby recovery ladder

Week 3: high-performing architecture, part 1

Study 3. High-Performing Architectures, then cover 3.1 Storage Solutions and 3.2 Compute Solutions.

Hands-on goal:

• compare EBS, EFS, FSx, and S3 for one workload with a concrete access pattern
• review one EC2 Auto Scaling target-tracking policy and one serverless alternative
• explain when CloudFront or Global Accelerator improves performance without changing the core app

Week 4: high-performing architecture, part 2

Finish 3.3 Database Solutions, 3.4 Network Architectures, and 3.5 Data Ingestion & Transformation.

Hands-on goal:

• compare Aurora, RDS, DynamoDB, and ElastiCache for one read-heavy and one write-heavy system
• review a multi-tier VPC path with ALB, NLB, endpoints, and hybrid connectivity choices
• outline one ingestion flow that moves data from transfer to transformation to analytics

Week 5: cost-optimized architectures

Work through 4. Cost-Optimized Architectures, 4.1 Storage Solutions, 4.2 Compute Solutions, 4.3 Database Solutions, and 4.4 Network Architectures.

Hands-on goal:

• compare S3 classes and lifecycle rules against real retention requirements
• review Savings Plans, Reserved Instances, Spot, and right-sizing decisions for one stack
• identify where endpoints, NAT placement, CloudFront, and cross-AZ traffic change monthly cost

Domain weight reminder for final review

AWS weights the current domains this way:

• Domain 1: Secure Architectures 30%
• Domain 2: Resilient Architectures 26%
• Domain 3: High-Performing Architectures 24%
• Domain 4: Cost-Optimized Architectures 20%

That should affect final review time. Do not spend your last two days only on whichever domain feels most interesting.

Week 6: mixed architecture drills and mocks

Switch from domain study into mixed scenario work. Use the cheat sheet for rapid review, the glossary for confused terms, and the resources page to re-open the live exam guide before booking.

Final-week checklist:

• take at least two full timed mock sets
• review every miss until you can explain the stronger answer in one sentence
• re-open the secure, resilient, and cost sections because many “performance” questions still hide security or cost traps

Miss log routing rules

If a mock miss sounds like one of these, re-open the narrowest matching page first:

This is the fastest way to keep mock review targeted instead of turning it into random rereading.

If you are behind schedule

Compress the plan without flattening it:

• keep Week 1 and Week 2 intact because Secure plus Resilient still carry the most weight together
• combine Week 3 and Week 4 only if you already know the core AWS service families
• never skip Week 6 mixed sets and miss-log review
• if time is tight, trim labs to one strong pattern per week rather than dropping labs entirely

Last 72 hours

• stop trying to learn every AWS service family in the catalog
• focus on confused pairs such as Multi-AZ versus read replica, ALB versus NLB, CloudFront versus Global Accelerator, and gateway endpoint versus interface endpoint
• re-open the resources page and confirm the live exam guide and policies one more time
• do short mixed review blocks and one last calm timed set instead of marathon cramming

Minimum lab baseline before the exam

Before exam day, try to be able to explain or reproduce these patterns from memory:

• ALB plus Auto Scaling across multiple AZs
• S3 or DynamoDB access from private subnets through endpoints
• RDS Multi-AZ versus read replica
• SQS or EventBridge for decoupling
• one backup-and-restore or warm-standby disaster recovery path

If you already architect on AWS weekly, compress this plan into three or four weeks. Keep the mixed sets and miss-log review. SAA-C03 punishes shallow service recognition more than it rewards memorized marketing language.