SAA-C03 — AWS Certified Solutions Architect – Associate Study Plan
Time-based study plan for AWS Certified Solutions Architect – Associate (SAA-C03) candidates.
How to use this Study Plan
This independent Study Plan is for candidates preparing for the real AWS Certified Solutions Architect – Associate (SAA-C03) exam from AWS. It is designed for practical scheduling: what to study, when to take timed practice, how to review missed questions, and when to stop adding new material.
The SAA-C03 exam rewards architecture judgment, not simple service recall. Your plan should repeatedly test whether you can choose the best AWS design for requirements such as security, resilience, performance, cost, operations, migration, and scalability.
Use this page with the official AWS exam guide, AWS documentation, hands-on review, and original practice questions.
Which plan should you use?
| Time left | Best for | Daily time target | Main goal | Risk level |
|---|---|---|---|---|
| 7 days | Final review only | 2-4 hours | Identify weak areas, review decisions, take timed mocks | High if you have not studied yet |
| 14 days | Focused sprint | 1.5-3 hours | Cover core architecture topics and practice heavily | Moderate to high |
| 30 days | Balanced preparation | 60-120 minutes | Learn, drill, review, and simulate the exam | Good default |
| 60 days | Full preparation | 45-90 minutes | Build steady service knowledge and architecture judgment | Lower |
| 90 days | Slower full preparation | 30-60 minutes | Best for busy schedules or newer AWS users | Lowest if consistent |
If you are not sure, choose the 30-day plan. If you have less time than the daily target, extend the schedule instead of rushing through topics without review.
What SAA-C03 preparation should emphasize
For AWS Certified Solutions Architect – Associate (SAA-C03), organize study around architecture decisions. Do not study services as isolated facts only.
| Area | What to practice | Example decision skill |
|---|---|---|
| IAM and security | IAM policies, roles, least privilege, KMS, Secrets Manager, encryption, identity federation concepts | Choose the secure access pattern with the least operational burden |
| Networking | VPCs, subnets, route tables, security groups, NACLs, NAT, VPC endpoints, hybrid connectivity concepts | Decide how private workloads reach AWS services or the internet |
| Compute | EC2, Auto Scaling, Elastic Load Balancing, Lambda, containers at a conceptual level | Select scalable compute for workload requirements |
| Storage | S3, EBS, EFS, FSx concepts, lifecycle policies, replication, backup | Match storage to access pattern, durability, sharing, and cost needs |
| Databases | RDS, Aurora, DynamoDB, ElastiCache, Redshift concepts | Choose relational, key-value, caching, or analytics storage appropriately |
| Resilience | Multi-AZ, backups, replication, failover, decoupling, disaster recovery patterns | Improve availability without over-engineering |
| Integration | SQS, SNS, EventBridge, Step Functions, API Gateway | Decouple components and handle asynchronous workloads |
| Observability and operations | CloudWatch, CloudTrail, AWS Config, Systems Manager, health and event tools | Detect, audit, automate, and troubleshoot architecture issues |
| Cost and governance | Right sizing, managed services, storage classes, purchase options conceptually, Organizations, tagging | Reduce cost while meeting requirements |
| Architecture scenarios | Tradeoffs across security, reliability, performance, operations, and cost | Eliminate plausible but less suitable answers |
Daily practice rhythm
Use the same basic rhythm almost every day. The goal is to turn study time into measurable improvement.
| Available time | Session structure |
|---|---|
| 45 minutes | 10 min missed-question review, 25 min focused topic review, 10 min quick quiz |
| 60 minutes | 10 min error log, 30 min topic study, 20 min practice questions |
| 90 minutes | 15 min error log, 35 min topic study, 30 min practice questions, 10 min summary |
| 2 hours | 15 min review, 45 min topic/lab/diagram work, 45 min timed questions, 15 min correction |
| 3+ hours | Split into two blocks: topic learning first, timed practice and review second |
The daily rule
Each study day should produce at least one of these outputs:
- A corrected missed-question entry.
- A service comparison note.
- A small architecture diagram.
- A timed question score with reviewed explanations.
- A weak-area list for the next session.
Passive watching or reading without questions should not count as a full study session.
Diagnostic-first practice
Start with a diagnostic set before building your schedule.
| When | What to do | How to use the result |
|---|---|---|
| Day 1 of any plan | Take a mixed untimed or lightly timed diagnostic set | Identify weak domains and service confusion |
| After first review block | Take a focused timed set | Check whether the review worked |
| Midpoint of plan | Take a longer mixed timed set | Find cross-topic weaknesses |
| Final week | Take full-length timed practice | Practice endurance, pacing, and decision-making |
Do not treat the first diagnostic score as a prediction. Treat it as a map.
Missed-question review method
A missed question is useful only if you convert it into a rule you can reuse.
| Step | Action | Example |
|---|---|---|
| 1 | Identify why you missed it | Misread requirement, weak service knowledge, confused two services, overbuilt the solution |
| 2 | Write the architecture clue | “Private workload needs AWS service access without public internet exposure” |
| 3 | Write the correct decision pattern | Consider VPC endpoints when the requirement fits |
| 4 | Write the distractor pattern | NAT, internet gateway, or public subnet may be tempting but may not meet the security requirement |
| 5 | Re-test within 48 hours | Do 5-10 related questions or redraw the architecture |
Error log template
Use a simple table or spreadsheet.
| Field | What to record |
|---|---|
| Date | When you missed it |
| Topic | IAM, VPC, S3, RDS, DynamoDB, etc. |
| Requirement clue | The words that should have guided the answer |
| Wrong assumption | What you thought incorrectly |
| Correct rule | The reusable decision rule |
| Retest date | When you will drill it again |
7-day final review plan
Use this if your exam is one week away. This is not enough time to learn AWS from scratch. The goal is to stabilize your weak areas, improve timing, and stop avoidable mistakes.
| Day | Focus | Study actions |
|---|---|---|
| 1 | Diagnostic and triage | Take a mixed diagnostic set. Build a weak-area list. Review the official exam guide topics. Do not start with random videos. |
| 2 | Security and networking | Review IAM roles, policies, KMS, security groups, NACLs, VPC routing, NAT, endpoints, and private/public subnet patterns. Do focused questions. |
| 3 | Compute, scaling, and resilience | Review EC2, Auto Scaling, load balancers, Lambda, multi-AZ designs, backups, failover, and decoupling. Take a timed topic set. |
| 4 | Storage and databases | Review S3, EBS, EFS, lifecycle, replication, RDS/Aurora, DynamoDB, caching, and backup choices. Drill service-selection questions. |
| 5 | Full timed mock | Take one full-length timed practice exam or the longest timed set you have. Review every missed and guessed question the same day. |
| 6 | Weak-area sprint | Revisit only your top weak areas. Redraw common architectures. Do short timed mixed sets. Stop adding unfamiliar low-yield material. |
| 7 | Final review | Review notes, error log, and common decision rules. Do a small confidence set only. Rest and prepare exam logistics. |
7-day priorities
Focus on these before anything else:
- IAM access patterns and encryption choices.
- VPC routing, private subnets, endpoints, and security boundaries.
- High availability and fault-tolerant architecture.
- S3, RDS/Aurora, DynamoDB, and storage selection.
- Decoupling with SQS, SNS, EventBridge, and managed services.
- Cost-aware architecture tradeoffs.
Avoid spending the final week memorizing obscure details that have not appeared in your missed-question patterns.
14-day focused plan
Use this if you have two weeks and can study most days. The plan combines rapid review with daily practice.
| Day | Main topic | Required practice |
|---|---|---|
| 1 | Diagnostic and plan setup | Mixed diagnostic set, error log, weak-area ranking |
| 2 | IAM and security foundations | IAM roles, policies, KMS, secrets, encryption, shared responsibility concepts |
| 3 | VPC and networking | Subnets, routes, gateways, endpoints, security groups, NACLs, hybrid concepts |
| 4 | Compute and scaling | EC2, Auto Scaling, load balancing, Lambda, container service concepts |
| 5 | Storage | S3, EBS, EFS, lifecycle, replication, backup and restore patterns |
| 6 | Databases | RDS/Aurora, DynamoDB, caching, database migration and read-scaling concepts |
| 7 | Timed mixed review | Timed set, full correction, update weak-area list |
| 8 | Resilient architectures | Multi-AZ, disaster recovery patterns, decoupling, queues, events |
| 9 | High-performing architectures | Caching, CDN, read replicas, async processing, performance tradeoffs |
| 10 | Cost-optimized architectures | Storage class selection, right-sizing concepts, managed services, governance |
| 11 | Operational excellence | CloudWatch, CloudTrail, Config, Systems Manager, monitoring, automation |
| 12 | Full timed mock | Simulate exam timing as closely as possible. Review thoroughly. |
| 13 | Weak-area sprint | Redo missed topics. Create one-page architecture decision sheet. |
| 14 | Light final review | Short mixed set, error log review, logistics, rest |
14-day pacing
- Days 1-6: learn and drill.
- Days 7-11: integrate topics into architecture scenarios.
- Days 12-14: simulate, correct, and stabilize.
- Stop adding new material after Day 12 unless it directly explains a recurring miss.
30-day balanced plan
Use this if you want a realistic preparation window without rushing. This is the best default plan for many working professionals.
Weekly structure
| Week | Goal | Main outputs |
|---|---|---|
| 1 | Build core AWS architecture foundations | Diagnostic, IAM/VPC/compute notes, first error log |
| 2 | Cover data, storage, integration, and resilience | Service comparison charts and focused drills |
| 3 | Practice scenario decisions and weak areas | Timed mixed sets, architecture diagrams, targeted review |
| 4 | Simulate and finalize | Full mocks, final weak-area sprint, readiness checks |
30-day schedule
| Days | Focus | Actions |
|---|---|---|
| 1 | Diagnostic | Take a mixed diagnostic set. Rank weak topics. Set daily study blocks. |
| 2-3 | IAM and security | Review IAM users/groups/roles, resource policies, encryption, KMS, secrets, identity federation concepts. Drill security questions. |
| 4-5 | VPC networking | Study public/private subnets, route tables, NAT, internet gateways, VPC endpoints, security groups, NACLs, peering and connectivity concepts. Draw diagrams. |
| 6 | Compute basics | Review EC2, AMIs, instance storage concepts, load balancers, Auto Scaling. |
| 7 | Weekly review | Timed mixed set. Correct all misses. Update error log. |
| 8-9 | Storage | Review S3 use cases, lifecycle, replication, EBS, EFS, backup patterns, static website and CDN concepts. |
| 10-11 | Databases | Review RDS, Aurora, DynamoDB, ElastiCache, read scaling, backups, high availability, migration concepts. |
| 12 | Serverless and integration | Review Lambda, API Gateway, SQS, SNS, EventBridge, Step Functions concepts. |
| 13 | Resilience patterns | Multi-AZ, failover, decoupling, disaster recovery strategies, backup and restore. |
| 14 | Weekly review | Timed mixed set. Redraw any architecture you missed. |
| 15-16 | Security scenario practice | Combine IAM, KMS, VPC, logging, and private access decisions in scenario questions. |
| 17-18 | Performance scenario practice | Caching, CDN, read replicas, async workflows, scaling choices. |
| 19 | Cost and governance | Cost-aware architecture, storage lifecycle, managed services, tagging, Organizations and governance concepts. |
| 20 | Operations and observability | CloudWatch, CloudTrail, Config, Systems Manager, alarms, logs, event-driven operations. |
| 21 | Mid-plan mock | Take a long timed mixed set or full mock. Review deeply. |
| 22-23 | Weak area 1 | Study your biggest weak area. Do focused questions and hands-on diagram review. |
| 24-25 | Weak area 2 | Repeat for your second biggest weak area. |
| 26 | Architecture comparison day | Compare similar services and patterns: SQS vs SNS vs EventBridge, RDS vs DynamoDB, EFS vs S3 vs EBS, NAT vs endpoint. |
| 27 | Full timed mock | Simulate exam timing. Mark guessed questions for review. |
| 28 | Mock correction | Review all missed and guessed questions. Convert misses into rules. |
| 29 | Final weak-area sprint | Short drills only. No broad new content. |
| 30 | Final review | Review notes, error log, architecture rules, and exam logistics. Rest. |
30-day weekly rhythm
| Day type | Activity |
|---|---|
| 4 days per week | Topic study plus focused questions |
| 1 day per week | Hands-on or diagram review |
| 1 day per week | Timed mixed practice |
| 1 day per week | Light review or rest |
Rest days matter. If you skip rest entirely, review quality usually drops.
60/90-day full preparation path
Use this if you are starting earlier, have limited daily time, or want more hands-on reinforcement.
60-day path
| Phase | Days | Focus | Practice target |
|---|---|---|---|
| 1 | 1-5 | Orientation and diagnostic | Exam guide review, diagnostic set, study tracker |
| 2 | 6-15 | Security and networking | IAM, KMS, VPC, subnets, routes, endpoints, hybrid concepts |
| 3 | 16-25 | Compute and storage | EC2, scaling, load balancing, Lambda concepts, S3, EBS, EFS |
| 4 | 26-35 | Databases and integration | RDS/Aurora, DynamoDB, caching, SQS, SNS, EventBridge, API Gateway |
| 5 | 36-45 | Architecture quality | Resilience, performance, cost optimization, operations, governance |
| 6 | 46-52 | Scenario practice | Mixed timed sets, service comparison drills, architecture diagrams |
| 7 | 53-57 | Full mock and correction | Full timed mock, deep review, weak-area sprint |
| 8 | 58-60 | Final review | Error log, decision rules, light practice, rest |
90-day path
For 90 days, use the same phases but stretch them:
| Phase | Suggested length | Additions |
|---|---|---|
| Orientation and diagnostic | 1 week | Build a service inventory and study tracker |
| Security and networking | 2 weeks | More VPC diagrams and IAM policy reasoning |
| Compute, storage, and databases | 3 weeks | More hands-on review and service comparison notes |
| Integration and resilience | 2 weeks | More event-driven and decoupled architecture scenarios |
| Cost, operations, and governance | 1-2 weeks | Monitoring, audit, tagging, and cost tradeoff practice |
| Mixed practice and mocks | Final 2 weeks | Timed sets, full mocks, error-log review |
The 90-day plan should not become casual. Keep weekly deadlines and timed practice.
Hands-on concept review checklist
SAA-C03 is an architecture exam, but hands-on review helps make service behavior real. You do not need to build large projects. Use small diagrams, console review, or sandbox exercises where appropriate.
| Concept | Review task |
|---|---|
| VPC architecture | Draw a VPC with public and private subnets across multiple Availability Zones, route tables, NAT, and security boundaries |
| Private access | Compare internet gateway, NAT, VPC endpoints, and private connectivity scenarios |
| Highly available web app | Diagram users, Route 53, CloudFront, ALB, Auto Scaling, private app subnets, and database tier |
| Object storage | Review S3 bucket security, encryption, lifecycle, versioning, replication, and CloudFront integration |
| Relational database | Compare RDS and Aurora availability, read scaling, backups, and failover concepts |
| NoSQL workload | Practice when DynamoDB fits better than relational storage |
| Decoupled processing | Diagram producer, SQS queue, worker fleet or Lambda, dead-letter queue concept, and monitoring |
| Event-driven workflow | Compare SNS, SQS, EventBridge, and Step Functions at a use-case level |
| Monitoring and audit | Identify which tool helps with metrics, logs, API activity, configuration history, and operational events |
| Cost review | Identify overbuilt designs and select managed or right-sized alternatives |
Service comparison drills
Many SAA-C03 questions are solved by eliminating services that do not fit the requirement. Build comparison notes like these.
| Compare | Ask yourself |
|---|---|
| Security group vs NACL | Is the control instance/resource-level or subnet-level? Stateful or stateless behavior? |
| NAT gateway vs VPC endpoint | Is the workload reaching the public internet or privately accessing supported AWS services? |
| S3 vs EBS vs EFS | Is the data object storage, block storage for one instance, or shared file storage? |
| RDS/Aurora vs DynamoDB | Is the workload relational with SQL patterns or key-value/document access at scale? |
| Read replica vs cache | Is the issue database read scaling or repeated low-latency access to cached data? |
| SQS vs SNS vs EventBridge | Is the pattern queue-based decoupling, pub/sub notification, or event routing? |
| CloudWatch vs CloudTrail vs Config | Are you monitoring metrics/logs, auditing API calls, or tracking resource configuration? |
| Multi-AZ vs replication/backup | Is the requirement high availability, disaster recovery, or data protection? |
| ALB vs NLB | Is the requirement application-layer routing or very high-performance network-level routing? |
| Managed service vs self-managed EC2 | Is the priority reduced operations, scalability, control, or customization? |
Timed mock exams
Timed mocks should be used after you have enough topic coverage to learn from them. Taking too many too early can waste good questions.
| Plan | When to take timed mocks |
|---|---|
| 7-day | One diagnostic early and one full timed mock around Day 5 |
| 14-day | One timed mixed set around Day 7 and one full mock around Day 12 |
| 30-day | One longer timed set around Day 21 and full mock around Day 27 |
| 60-day | Timed sets during the final third, full mock in the last 7-10 days |
| 90-day | Monthly mixed checks, then full mocks in the final 2 weeks |
How to review a mock
Do not only review wrong answers. Review these four groups:
- Correct but guessed.
- Correct but slow.
- Incorrect due to knowledge gap.
- Incorrect due to reading or elimination error.
For each mock, produce a short summary:
| Question group | What to do next |
|---|---|
| Missed due to weak topic | Schedule focused review within 24-48 hours |
| Missed due to confusion between services | Create a comparison table |
| Missed due to overbuilding | Practice choosing the simplest design that meets requirements |
| Missed due to speed | Practice timed sets and flagging strategy |
| Correct but guessed | Treat as unstable knowledge and review it |
Final-week rules
During the final week, your goal is to reduce errors, not collect new resources.
Do
- Review your missed-question log daily.
- Practice mixed scenario questions.
- Redraw common AWS architectures from memory.
- Review IAM, VPC, storage, databases, resilience, and cost tradeoffs.
- Take timed practice under realistic conditions.
- Sleep normally before the exam.
Do not
- Start a new full course in the final days.
- Memorize random service limits or pricing details.
- Ignore guessed questions that happened to be correct.
- Spend all your time on your favorite topic.
- Take a full mock the night before if it will damage confidence or rest.
When to stop adding new material
Stop broad new content:
| Time left | Rule |
|---|---|
| 7 days | Add only material tied to repeated misses |
| 3 days | No new broad topics; focus on error log and core comparisons |
| 24 hours | Light review only; no heavy mocks or deep new documentation |
Exam-readiness checks
You are closer to ready when you can do the following consistently:
- Explain why the correct answer is better than the distractors.
- Identify requirement clues such as “least operational overhead,” “highly available,” “cost-effective,” “private access,” or “decoupled.”
- Choose between similar AWS services without relying on keyword memorization alone.
- Finish timed practice without rushing the final questions.
- Recognize when a solution is secure but unnecessarily complex.
- Recognize when a solution is cheap but does not meet availability or security requirements.
- Correctly review guessed questions and avoid repeating the same mistake.
If you are behind schedule
Use triage instead of trying to cover everything equally.
| Problem | Adjustment |
|---|---|
| You have not started and exam is within 7 days | Take a diagnostic, focus on IAM, VPC, storage, databases, resilience, and timed practice |
| You keep missing networking | Draw VPC diagrams daily until route and access patterns are clear |
| You keep confusing data services | Build a comparison chart for S3, EBS, EFS, RDS/Aurora, DynamoDB, and caching |
| You score well untimed but poorly timed | Practice shorter timed sets and flag hard questions earlier |
| You forget reviewed topics | Add spaced review: retest each missed topic after 1 day, 3 days, and 7 days |
| You are overloaded by resources | Pick one primary content source, one question source, and your error log |
Practical next step
Start with a mixed diagnostic set for AWS Certified Solutions Architect – Associate (SAA-C03). Then choose the 7-day, 14-day, 30-day, or 60/90-day path based on your exam date. Keep an error log from the first session, and make every study block end with practice or correction.