AWS SAA-C03 Study Plan: Architecture, Resilience, and Cost in 30, 60, and 90 Days

AWS SAA-C03 30-, 60-, and 90-day study plan for architecture, resilience, cost, review loops, and final-week priorities.

Use this study plan when you want a structured route through AWS Certified Solutions Architect - Associate (SAA-C03) instead of hopping between AWS service names. SAA-C03 is an architecture decision exam. It tests whether you can design secure, resilient, high-performing, and cost-optimized solutions under explicit constraints.

AWS’s current certification page describes SAA-C03 as focused on designing cost- and performance-optimized solutions across the breadth of AWS services. The exam does not require deep hands-on coding, but it does expect solution-design judgment: choose the safest architecture that satisfies the stated requirement without unnecessary complexity or cost.

Current exam facts

I verified these current AWS exam facts on May 16, 2026.

Item Value
Exam AWS Certified Solutions Architect - Associate
Exam code SAA-C03
Category Associate
Questions 65 total
Scoring 50 scored + 15 unscored (unscored items are not identified)
Question types Multiple choice and multiple response
Time 130 minutes
Passing score 720, scaled 100-1000
Cost 150 USD
Target candidate About 1 year of hands-on experience designing cloud solutions that use AWS services

AWS notes that the exam uses short names for some services, and a short-name list is available through the exam Help button. Review service short names before mocks so answer choices feel familiar instead of noisy.

Weight-driven study allocation

Domain Weight How to allocate study time
Secure Architectures 30% Spend the most time on IAM, resource policies, secure access paths, workload boundaries, KMS, TLS, backup, retention, and data protection.
Resilient Architectures 26% Drill decoupling, queues, event routing, scaling, Multi-AZ, failover, RTO/RPO, and fault-tolerant state.
High-Performing Architectures 24% Practice storage, compute, database, network, edge, and ingestion choices by bottleneck and access pattern.
Cost-Optimized Architectures 20% Study storage tiers, compute purchase models, right-sizing, database cost, network transfer, endpoints, and waste reduction.

Secure and resilient architectures are 56% of scored content together. That does not mean performance and cost are secondary. Many SAA-C03 questions hide a cost or performance constraint inside a security or resilience scenario.

Pick the right timeline

Starting point Typical study time Best-fit timeline
You design or operate AWS workloads today 45-70 hours 30-60 days
You know AWS basics but have less architecture trade-off depth 70-100 hours 60 days
You hold CLF-C02 but have little hands-on AWS design experience 90-130 hours 60-90 days
You are new to AWS and cloud architecture 130+ hours 90 days before scheduling

Choose the longer route if IAM policy layers, private networking, RDS/Aurora/DynamoDB fit, DR patterns, endpoint choices, and data-transfer cost still blur together.

The SAA-C03 study loop

Use one architecture loop every week.

    flowchart LR
	  R["Requirement"] --> C["Constraint"]
	  C --> P["Pattern"]
	  P --> T["Trade-off"]
	  T --> E["Eliminate"]
	  E --> M["Miss rule"]
Step What to ask
Requirement What must the workload achieve: security, resilience, performance, cost, operations, migration, or compliance?
Constraint Which wording controls the answer: lowest cost, most secure, least operational overhead, highly available, low latency, or fault tolerant?
Pattern Which architecture pattern fits before you choose a service name?
Trade-off What does the chosen answer improve, and what cost, complexity, or operational burden does it add?
Eliminate Which answers solve the wrong constraint or overbuild the scenario?
Miss rule What one-line architecture rule would have prevented the miss?

Minimum architecture baseline

You do not need a large lab, but you should be able to explain these patterns without guessing:

Pattern What you should know
Secure private access IAM roles, resource policies, endpoint policies, gateway endpoints, interface endpoints, security groups, and KMS key policy interactions
Web workload Route 53, CloudFront, WAF, ALB/NLB, Auto Scaling, private subnets, database tier, and multi-AZ placement
Decoupled system SQS, SNS, EventBridge, Step Functions, Lambda, retries, DLQs, idempotency, and failure isolation
Data store choice S3, EBS, EFS, FSx, RDS, Aurora, DynamoDB, ElastiCache, OpenSearch, and access-pattern fit
Resilience ladder Multi-AZ, read replicas, backups, pilot light, warm standby, active/passive, active/active, RTO, and RPO
Cost control S3 lifecycle, Savings Plans, Reserved Instances, Spot, right-sizing, serverless fit, NAT cost, endpoints, and transfer paths

30-day intensive plan

Use this route only if you already know AWS services and can study most days.

Week Focus What to produce
1 Secure architectures An access and data-protection checklist covering IAM roles, resource policies, SCPs, endpoints, WAF, Shield, KMS, TLS, backups, retention, and private placement.
2 Resilient architectures A resilience map covering queues, fanout, workflow orchestration, stateless tiers, Multi-AZ, failover, RTO/RPO, and DR patterns.
3 High-performing architectures A bottleneck chooser for storage, compute, database, network, edge, caching, and ingestion/transformation requirements.
4 Cost optimization and mixed review A cost-control matrix for storage tiers, compute pricing, database capacity, caching, NAT, endpoints, transfer charges, and overbuilt designs.

30-day rule

Every day should create one reusable architecture artifact.

Artifact Why it matters
Constraint table Prevents answering a security question with a performance answer or a cost question with an overbuilt HA design.
Path sketch Forces you to place public/private routes, load balancers, endpoints, security controls, and data stores correctly.
Resilience ladder Keeps Multi-AZ, backups, replicas, pilot light, warm standby, and active/active distinct.
Bottleneck map Converts vague “slow app” symptoms into storage, compute, database, network, or ingestion fixes.
Cost matrix Keeps cheapest valid design separate from cheapest possible component.
Miss log Turns plausible distractors into reusable elimination rules.

60-day balanced plan

This is the best default route for most candidates.

Weeks Focus What to do
1-2 Secure Architectures Drill secure access, IAM roles, resource policies, private endpoints, WAF/Shield, workload boundaries, KMS, TLS, backups, retention, and data controls.
3-4 Resilient Architectures Practice loose coupling, queues, event routing, scaling, cache offload, Multi-AZ, failover, backups, RTO/RPO, and DR trade-offs.
5 High-Performing Architectures Study storage, compute, database, network, edge, and data-ingestion choices by bottleneck and access pattern.
6 Cost-Optimized Architectures Drill S3 lifecycle, EBS sizing, compute purchase models, serverless fit, database cost, network transfer, endpoints, and NAT charges.
7 Mixed architecture scenarios Run mixed sets and group misses by constraint: security, resilience, performance, cost, data, network, or operations.
8 Final repair and scheduling decision Reread weak lessons, review the cheat sheet, answer sample questions, and schedule only if misses are narrow.

90-day part-time plan

Use this route if you are learning AWS architecture while studying.

Phase Weeks Outcome
Security and access foundation 1-3 You can design role-based access, private service paths, secure workloads, and data protection without relying on public shortcuts.
Resilience and failover 4-5 You can choose decoupling, scaling, Multi-AZ, backup, restore, and DR patterns by failure model and recovery target.
Performance and access patterns 6-8 You can choose storage, compute, database, network, edge, and ingestion patterns by bottleneck and workload shape.
Cost and mixed trade-offs 9-10 You can preserve requirements while reducing waste across storage, compute, database, and network paths.
Exam execution 11-12 You can answer mixed scenario questions under time pressure and explain repeated misses as architecture rules.

What to drill by domain

Domain Drill questions until you can answer…
Secure Architectures Which identity, network, workload, key, transport, backup, or data-control layer satisfies the security requirement?
Resilient Architectures Does the requirement call for decoupling, scaling, Multi-AZ, failover, backup, DR, RTO, or RPO?
High-Performing Architectures Which layer is the bottleneck: storage, compute, database, network, edge, or ingestion/transformation?
Cost-Optimized Architectures Which lower-cost design still satisfies the security, resilience, performance, and operational constraints?

High-yield architecture comparisons

Decision Choose by asking…
Gateway endpoint vs interface endpoint vs NAT Is the target S3/DynamoDB, another supported AWS service over PrivateLink, or outbound internet-style access?
Security group vs NACL Do you need stateful instance/ENI-level filtering or stateless subnet-level filtering?
ALB vs NLB Do you need Layer 7 HTTP routing or Layer 4 high-throughput/low-latency traffic handling?
CloudFront vs Global Accelerator Is the need HTTP caching/content delivery or global application entry-path performance?
Multi-AZ vs read replica Is the requirement availability/failover or read scaling/reporting?
Backup/restore vs pilot light vs warm standby What RTO/RPO and cost posture does the business actually require?
SQS vs SNS vs EventBridge Is the need buffering, fanout notification, or event routing/filtering?
RDS/Aurora vs DynamoDB Is the access pattern relational/SQL/transactions or key-value/document scale?
Savings Plans vs Spot Is usage steady enough for commitment, or interruptible enough for spare-capacity pricing?

Final-week checklist

Use the final week for mixed-scenario decision speed.

Day Work
7 days out Reread the cheat sheet and summarize each domain as one decision problem.
6 days out Drill secure architectures: IAM, endpoints, WAF/Shield, KMS, TLS, backups, private access, and data controls.
5 days out Drill resilient architectures: queues, fanout, scaling, Multi-AZ, failover, RTO/RPO, and DR patterns.
4 days out Drill high-performing architectures: storage, compute, databases, network, edge, cache, and ingestion bottlenecks.
3 days out Drill cost optimization: S3 lifecycle, purchase models, rightsizing, serverless fit, endpoints, NAT, and transfer cost.
2 days out Run one mixed timed block and convert repeated misses into one-line architecture rules.
1 day out Review only weak rules, official facts, high-yield comparisons, and service short names.

Readiness signals

You are close to ready when:

  • You can identify the controlling constraint before reading every answer.
  • You can explain why the wrong answer solves a different domain or overbuilds the scenario.
  • You can separate secure access, workload placement, data protection, resilience, performance, and cost controls.
  • You can choose between common pairs such as endpoint vs NAT, Multi-AZ vs read replica, ALB vs NLB, and CloudFront vs Global Accelerator.
  • You can keep a steady pace across 65 questions in 130 minutes.

If you only have 48 hours

This is only reasonable if you are already near-ready.

  1. Read the cheat sheet twice: once before practice and once after reviewing misses.
  2. Drill one mixed timed block and classify every miss by domain and constraint.
  3. Spend one focused block on security/resilience and one on performance/cost.
  4. Review gateway endpoints, interface endpoints, NAT, IAM/KMS, RDS/Aurora/DynamoDB, ALB/NLB, CloudFront/Global Accelerator, SQS/SNS/EventBridge, and DR patterns.
  5. Recheck the current official AWS page and exam guide before scheduling or buying an exam attempt.

Booking signal

Schedule only when your misses are narrow and explainable. If you still pick services by familiarity instead of requirement, constraint, pattern, trade-off, and elimination logic, keep studying. SAA-C03 rewards architecture judgment more than service-name recall.

Revised on Monday, June 15, 2026