A good study guide should do more than list topics. It should tell you what to spend your limited time on and in what order. This guide covers the four SAA-C03 domains and how much each is actually worth, the services worth knowing cold before you touch a practice exam, a realistic 4 to 6 week plan you can stretch or compress based on your background, and how to practice in a way that builds real readiness rather than a false sense of it.
SAA-C03 at a glance
AWS Certified Solutions Architect - Associate (SAA-C03) has 65 questions, a mix of multiple choice and multiple response, to be completed in 130 minutes. It costs roughly USD 150, though pricing varies by country and currency. Scoring is compensatory across domains and reported as a scaled score from 100 to 1000, with 720 needed to pass, commonly summarized as about 72 percent, though it is a scaled score rather than a literal percentage of questions answered correctly.
The four SAA-C03 domains and their weights
Everything on the exam falls under one of four domains, and they are not weighted equally. Knowing the split helps you allocate study time proportionally instead of spending equal effort everywhere.
- Design Secure Architectures (about 30 percent, the heaviest domain): identity and access management with IAM, least-privilege permissions, encryption at rest and in transit with KMS, and network-level controls like security groups and network ACLs.
- Design Resilient Architectures (about 26 percent): high availability and fault tolerance, Multi-AZ deployments, decoupling components with queues and events, Auto Scaling, load balancing, and backup and recovery strategies.
- Design High-Performing Architectures (about 24 percent): choosing the right compute, storage, and database options for a performance goal, caching with services like ElastiCache and CloudFront, and scaling patterns.
- Design Cost-Optimized Architectures (about 20 percent, and the most commonly under-studied domain): storage class selection, right-sizing, choosing between On-Demand, Reserved Instances, and Savings Plans, and data transfer cost awareness.
Key services to know cold
SAA-C03 draws from a wide catalog, but a manageable core set of services accounts for the large majority of questions. Prioritize genuine understanding of these before branching out to less common services.
Compute and application services
EC2 instance types and purchasing options, Auto Scaling groups, Elastic Load Balancing (Application, Network, and Gateway Load Balancers and when each fits), Lambda and basic serverless patterns, and Elastic Beanstalk at a conceptual level.
Storage
S3 storage classes and lifecycle policies, S3 versioning and replication, EBS volume types and when to choose them, EFS for shared file storage, and the difference between block, object, and file storage at a conceptual level.
Databases
RDS with Multi-AZ for availability and read replicas for read scaling, Aurora as a managed relational option, DynamoDB for key-value and document workloads, and a general sense of when a relational versus non-relational database fits a scenario.
Networking
VPC fundamentals including subnets, route tables, and internet and NAT gateways, security groups versus network ACLs, Route 53 routing policies, CloudFront for content delivery, and a conceptual grasp of Direct Connect and VPN for hybrid connectivity.
Security and identity
IAM users, groups, roles, and policies, the principle of least privilege, KMS for encryption key management, and AWS Organizations and Service Control Policies at a conceptual level for multi-account scenarios.
Monitoring and management
CloudWatch for metrics and alarms, CloudTrail for auditing API activity, and a basic understanding of AWS Well-Architected Framework pillars, since several questions are framed around trade-offs the framework describes.
A 4 to 6 week study plan
This plan assumes roughly one to two hours of study most days. If you are newer to AWS, stretch each week into two; if you already work hands-on with AWS daily, you can compress it.
- Week 1: Foundations and Design Secure Architectures. Get comfortable in the AWS console if you are not already, then study IAM, security groups and NACLs, and KMS. This domain is the heaviest, so give it real time up front.
- Week 2: Design Resilient Architectures. Study Multi-AZ RDS, Auto Scaling, load balancer types, decoupling with SQS and SNS, and backup and recovery approaches across services.
- Week 3: Design High-Performing Architectures. Study compute and database selection for performance, caching with ElastiCache and CloudFront, and read replicas versus Multi-AZ for different goals.
- Week 4: Design Cost-Optimized Architectures, plus networking fundamentals (VPC, Route 53, Direct Connect and VPN at a conceptual level) if you have not covered them yet. Do not shortchange this week; it is the most commonly under-prepared domain.
- Week 5: Full-length, timed practice exams. Take at least two to three complete attempts under exam-like conditions, and spend as much time reviewing each one afterward as you spent taking it.
- Week 6 (extend here if you started as a beginner): Targeted review of whichever domain your practice attempts show as weakest, followed by one or two final full-length attempts to confirm you are consistently and comfortably above the passing line before you book.
Treat weeks as flexible milestones rather than a rigid calendar. The plan works whether you compress it into four intense weeks or stretch it to eight or more; what matters is covering every domain deliberately and finishing with real full-length practice, not skipping straight from notes to the exam.
How to practice effectively
- Get at least some hands-on time in the AWS console or free tier. Concepts like Auto Scaling policies or S3 lifecycle rules stick far better once you have configured them yourself, even briefly.
- Use practice questions with full explanations, not just an answer key, so you learn why the best answer fits the stated constraint and why the runner-up options fall short.
- Take full-length, timed mock exams to build the pacing and stamina 65 scenario questions in 130 minutes actually requires.
- Review every miss by domain so patterns become visible. A single wrong answer teaches little; a cluster of misses in one domain tells you exactly where to focus next.
- Avoid memorizing specific practice questions. SAA-C03 tests reasoning under constraints, and real exam wording will differ, so re-derive the answer from the scenario each time rather than recognizing it.
Bottom line
SAA-C03 rewards a structured approach: study the four domains in proportion to their real weight, build a working knowledge of the core service catalog, and finish with enough full-length, timed practice to trust your pacing and your domain balance. Four to six weeks is a realistic target for most people with some technical background, and the plan stretches cleanly for beginners or compresses for people already working with AWS.