AWS Solutions Architect Associate: A Study Guide

A study guide for the AWS Certified Solutions Architect - Associate exam, SAA-C03, built from the official exam guide: format and passing score, the four design domains and their tasks, how scenario questions are constructed, a method for studying by trade-off, and how the exam relates to data engineering.

GloryTecks Team

Training & Placement Faculty

6 May 2026 5 min read

Last updated: 1 October 2026

Share:

The AWS Certified Solutions Architect - Associate is AWS's general architecture certification at associate level, and it is often misunderstood. It is not a test of whether you can operate AWS. It is a test of design judgement: given a requirement, which combination of services meets it securely, reliably, quickly and cheaply. AWS's exam guide states that the exam validates the ability to design solutions based on the AWS Well-Architected Framework (AWS exam guide: SAA-C03).

Study for it as a design exam and it becomes manageable. Study it as a list of services to memorise and it does not.

The exam in numbers

ItemDetail
Length130 minutes
Questions65, multiple choice or multiple response
Scored questions50; 15 are unscored and not identified
Passing score720 on a scale of 100 to 1,000
Cost150 USD

Length, format and cost are from the certification page (AWS: Solutions Architect - Associate). As with other AWS exams, unanswered questions count as incorrect, and scoring is compensatory across sections. Check the page for current details before booking.

The exam guide's target candidate has at least one year of hands-on experience designing cloud solutions on AWS. The certification page adds that deep coding experience is not required, and that people with one to three years of IT experience have used it as a starting point.

The four domains

The domain names are four qualities of a good design, and they map closely to pillars of the Well-Architected Framework (AWS: Well-Architected pillars).

DomainWeightTasks
1. Design Secure Architectures30%Secure access to AWS resources; secure workloads and applications; appropriate data security controls
2. Design Resilient Architectures26%Scalable and loosely coupled architectures; highly available and fault-tolerant architectures
3. Design High-Performing Architectures24%Storage; elastic compute; databases; network architectures; data ingestion and transformation
4. Design Cost-Optimized Architectures20%Cost-optimised storage, compute, database and network designs

Security is the largest domain, and the last place to skimp.

How the questions work

Almost every question is a short scenario followed by a qualifier. The scenario describes a system and a need. The qualifier tells you which quality to optimise:

  • "most cost-effective"
  • "least operational overhead"
  • "highest availability"
  • "most secure"

Usually two or more of the options would work. Only one is best for the stated qualifier. A design that is correct but expensive is wrong when the question asks for cost-effective, and a design that is cheap but needs servers to manage is wrong when it asks for least operational overhead.

A reading method that helps:

  1. Read the last sentence first to find the qualifier.
  2. Underline the constraints in the scenario: data size, latency, durability, compliance, existing systems.
  3. Eliminate options that break a constraint.
  4. Choose between the survivors on the qualifier alone.

What to study in each domain

Secure (30%). IAM users, roles and policies; the principle of least privilege; cross-account access; VPC security groups and network ACLs; private connectivity to services; encryption at rest and in transit with KMS; secrets management. Read AWS IAM explained, VPC basics for data engineers and securing data on AWS with encryption and KMS.

Resilient (26%). Regions and Availability Zones; load balancing and auto scaling; decoupling with queues and events; multi-AZ databases and read replicas; backup and disaster recovery strategies and what each costs.

High-performing (24%). Choosing between S3, EBS and EFS; instance families; relational, key-value and warehouse databases; caching and content delivery; and, notably for data people, ingestion and transformation: streaming versus batch, Kinesis, Glue, and data lake patterns. S3 vs EBS vs EFS is typical of the comparisons asked.

Cost-optimised (20%). S3 storage classes and lifecycle rules; on-demand, reserved, savings plans and Spot purchasing; right-sizing; data transfer costs; serverless versus provisioned. S3 lifecycle policies covers one common topic.

Study by trade-off, not by service

The most effective preparation is a notebook of comparisons. For each pair, write when you would choose each and why:

DecisionWhat separates the options
S3 or EBS or EFSObject, block or shared file access
RDS or DynamoDBRelational queries or key-based access at scale
SQS or SNS or EventBridgeQueue for one consumer, fan-out to many, or routing by rules
Security group or network ACLStateful and per-instance, or stateless and per-subnet
Multi-AZ or read replicaAvailability, or read scaling
Reserved capacity or SpotSteady workloads, or interruptible ones
Lambda or containers or EC2Short event-driven code, portable services, or full control

When you can explain each row without notes, most scenario questions resolve themselves.

A study method

  1. Read the exam guide, including the task statements in each domain.
  2. Learn the core services hands-on: VPC, EC2, S3, IAM, RDS, a load balancer and auto scaling. Build a small two-tier application once, then delete it.
  3. Build the comparison notebook as you go.
  4. Read the Well-Architected Framework overview, enough to recognise each pillar's concerns.
  5. Take practice questions, using AWS's official set first. For every wrong answer, find the constraint or qualifier you missed.
  6. Sit the exam when practice results are steady.

How long this takes depends on experience. If you are new to IT, AWS suggests the Cloud Practitioner first; see the Cloud Practitioner guide.

Is it the right exam for data engineers?

It is a general architecture exam. Networking, compute and resilience take up much of it, and analytics services appear only as part of one domain. For someone whose work is pipelines and warehouses, the Data Engineer - Associate exam is the closer match.

It is still valuable. Data platforms sit inside VPCs, depend on IAM, and fail in the ways this exam teaches you to design against. Many data engineers take it first for that breadth, then the data exam. The AWS certification path for data roles discusses the order.

How hard is the AWS Solutions Architect Associate exam?

It is an intermediate exam. The difficulty is in choosing the best of several workable designs, which takes practice with scenarios, not only reading.

Does the exam require coding?

No. AWS says deep hands-on coding experience is not required, though basic programming concepts help.

How many domains does SAA-C03 have?

Four: secure, resilient, high-performing and cost-optimised architectures, weighted 30, 26, 24 and 20 percent.

Should a data engineer take Solutions Architect or Data Engineer Associate?

The Data Engineer exam matches the role more closely. Solutions Architect gives broader AWS foundations and is a common first step.

AWS data services and cloud architecture for data pipelines are covered in the Data Engineering course.

Sources

GloryTecks Team

Training & Placement Faculty

The GloryTecks faculty team mentors learners across Data Science, AI and Data Engineering, with a focus on real-time projects and placement readiness in Hyderabad.

Want to master AWS?

Join GloryTecks’ expert-led Data Engineering training in Hyderabad with real-time projects and 100% placement support.

Explore course