AWS Solutions Architect Associate (SAA-C03) Study Guide

AWS Certified Solutions Architect – Associate (SAA-C03) validates the ability to design solutions based on the AWS Well-Architected Framework. AWS describes it as focused on secure, resilient, high-performing, and cost-optimized architectures.

This guide was reviewed against the current AWS certification page and SAA-C03 exam guide. AWS recommends at least one year of hands-on experience designing cloud solutions, although it does not make that experience a formal prerequisite.

Understanding the SAA-C03 Exam Structure

Before diving into study materials, understanding the exam format is crucial for developing an effective preparation strategy. The SAA-C03 exam tests your ability to design cost-optimized, secure, and resilient systems on AWS, focusing heavily on real-world architectural scenarios rather than simple fact recall.

Exam Format and Logistics

The SAA-C03 consists of 65 questions that you must complete within 130 minutes. These questions include two formats: multiple-choice (one correct answer from four options) and multiple-response (two or more correct answers from five or more options). The exam is available in both online proctored and test center formats, giving you flexibility in how you take the test.

AWS uses scaled scoring with a range of 100-1000 points, and you need a minimum score of 720 to pass. Importantly, not all questions count toward your score—some are unscored questions being evaluated for future exams. Since you won't know which questions are unscored, treat every question with equal importance and attention.

Exam Domains and Weightings

The SAA-C03 exam is divided into four domains, each carrying different weight in your final score. Understanding these weightings helps you allocate your study time effectively:

• Domain 1 - Design Secure Architectures (30%):

  This is the heaviest weighted domain, covering IAM, data encryption, network security, and application security. You'll need to demonstrate knowledge of security best practices across all AWS layers.

• Domain 2 - Design Resilient Architectures (26%):

  Focuses on creating highly available and fault-tolerant systems using services like Auto Scaling, ELB, Multi-AZ deployments, and disaster recovery strategies.

• Domain 3 - Design High-Performing Architectures (24%):

  Tests your ability to design scalable and elastic solutions, choose appropriate compute and storage options, and implement caching strategies for optimal performance.

• Domain 4 - Design Cost-Optimized Architectures (20%):

  Evaluates your understanding of cost-effective storage solutions, compute options, data transfer optimization, and overall cost management strategies.

Creating Your Study Plan

AWS recommends at least one year of hands-on design experience for the target candidate. Your preparation time therefore depends on which task statements you can already demonstrate and which services you have used.

Build a Timeline from the Exam Guide

1. Read every task statement in the official guide and mark it as familiar, needs review, or needs hands-on work.
2. Schedule short architecture exercises for gaps rather than assigning the same number of weeks to every learner.
3. Use exam-style questions periodically to locate weak domains.
4. Revisit the guide before scheduling and confirm that you can explain trade-offs across all four domains.

Essential Study Resources

Use several resource types for different jobs:

Official exam scope: Start with the SAA-C03 exam guide. It contains the current task statements, technologies, and in-scope and out-of-scope service references.

Architecture guidance: Use the AWS Well-Architected Framework, whose six pillars are operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability.

Courses and labs: Choose material that names SAA-C03, maps lessons to the current domains, and includes hands-on design work. A course length or rating alone does not show that it is current.

Practice questions: Use AWS’s official practice resources and other original question sets to identify gaps. Review the underlying documentation for every missed or uncertain answer; do not memorize question wording.

Study Architecture Trade-offs

The official guide includes service references rather than promising how often a service appears. Build broad familiarity with the listed services and deeper knowledge where task statements require architecture trade-offs.

For each scenario, identify:

1. workload requirements and constraints;
2. data access and consistency needs;
3. network boundaries and connectivity;
4. identity, authorization, and encryption;
5. availability and recovery objectives;
6. performance and scaling behavior;
7. operational effort and cost.

Compute

Compare managed, serverless, container, and virtual-machine options using the requirements in the scenario. Review current documentation for service quotas, supported features, and purchasing models instead of memorizing values from an article.

Storage and Data

Choose among object, block, file, relational, key-value, and other data services by access pattern, durability, availability, consistency, latency, lifecycle, and cost. Verify storage classes and retrieval characteristics in current AWS documentation.

Networking

Practice reasoning about subnets, route tables, gateways, security groups, network ACLs, VPC endpoints, peering, Transit Gateway, VPN, Direct Connect, DNS, and content delivery at the depth required by the guide.

Security

Apply least privilege, separation of duties, encryption, network controls, logging, and incident-response considerations to each design. Do not assume one named service is always the secure answer; use the stated requirement.

Reliability, Performance, and Cost

Compare single points of failure, scaling, backup, recovery, caching, and data-transfer choices. A design is only “optimized” relative to its actual constraints.

Hands-On Practice and Labs

Hands-on work helps connect architecture choices with operational consequences. Use an AWS account only if it fits your learning goals, review the current AWS Free Tier terms, and set budgets before creating resources because hands-on exercises can incur charges.

Protect the root user, use least-privilege access, and follow the current AWS account security guidance. Delete exercise resources when you finish.

Essential Hands-On Projects

Build these projects to gain practical experience with core services:

1. Static Website Hosting with S3:

   Build a private S3 origin behind CloudFront, then compare that design with direct S3 website hosting. Record the security, cost, and operational trade-offs.

2. Highly Available Web Application:

   Launch EC2 instances in public and private subnets across multiple Availability Zones. Configure an Application Load Balancer (ALB) to distribute traffic and an Auto Scaling Group to handle demand changes. Connect to an RDS database resource in a private subnet.

3. Serverless API:

   Create a Lambda function behind API Gateway, store sample data in DynamoDB, grant least-privilege access, and inspect logs in CloudWatch.

4. VPC Peering Investigation:

   Create two VPCs in different regions or the same region. Establish a VPC peering connection. Configure route tables and security groups to allow communication between EC2 instances in both VPCs using private IP addresses.

Exam Day Strategies and Tips

Knowledge of the material and familiarity with the exam interface both matter. These tactics help you use the available time deliberately:

• Read the Question Carefully:

  Identify keywords like "highly available", "cost-effective", "most operationally efficient", or "minimise latency". These keywords often determine the correct answer among several technically feasible options.

• Process of Elimination:

  Eliminate obviously incorrect answers first. This usually leaves you with two plausible options. Compare them against the specific requirements in the question (e.g., one might be cheaper but less resilient).

• Time Management:

  Use the published duration and item count to make a rough pacing plan, while allowing more time for complex items. Use flag-and-review only where the interface permits it.

• Review Flagged Questions:

  Use remaining time to revisit flagged and unanswered items. Change an answer when a requirement or documented rule supports the change, not merely because it feels uncertain.

Common Mistakes to Avoid

These are common review gaps rather than claims about why candidates fail:

• Confusing Services:

  Distinguish services by the requirement they meet rather than memorizing pairs of names.

• Ignoring Defaults:

  Verify defaults in current documentation. For example, default and custom network ACLs do not start with the same rules.

• Overlooking Service Scope:

  Check whether a resource or control is global, regional, or Availability Zone–scoped instead of relying on a simplified service list.

• Relying on "Buzzwords":

  Don't just pick an answer because it contains a popular buzzword like "Serverless" or "AI". Ensure it actually solves the problem described.

Conclusion and Next Steps

Preparing for SAA-C03 can strengthen your ability to reason about AWS architecture trade-offs. A structured plan, hands-on design work, and careful review of the current guide improve preparation, but no resource can promise a first-attempt result.