SkarpChapter 1 of 26
Orientation: SAA-C03 Exam Blueprint, Strategy, and Mindset
Step into the exam with clarity: see how the SAA-C03 is structured, what the four domains really test, and how to build a study plan that mirrors the official blueprint instead of random service trivia.
Orientation: How This Exam Really Works
Why Orientation Matters
SAA-C03 is scenario-heavy. You are tested on design judgment, not memorizing service trivia. This step aligns your mental model with how the exam is actually built.
Core Exam Format
Expect around 65 questions in 130 minutes, mostly multiple-choice and multiple-response. You can flag questions and return to them, but the clock keeps running.
Scoring Model Basics
Scores range from 100–1000, with about 720 to pass. Questions are not equally weighted, and unscored trial questions are mixed in, so treat every item seriously.
Design Focus Areas
The exam cares about security, reliability, performance, cost, operations, and sustainability. You will apply these ideas inside realistic AWS scenarios.
The Four SAA-C03 Domains and Their Weight
Domain Overview
SAA-C03 is divided into four domains: secure, resilient, high-performing, and cost-optimized architectures. Their weight determines where most questions come from.
Domain 1 – Secure (30%)
Design Secure Architectures covers IAM, data protection, and network security. Expect many scenario questions about who can access what, and how data is protected.
Domain 2 – Resilient (26%)
Design Resilient Architectures focuses on high availability, fault tolerance, and disaster recovery. Think Multi-AZ, Multi-Region, backups, and failover strategies.
Domain 3 – High-Performing (24%)
Design High-Performing Architectures tests right-sizing, caching, and performance tuning for compute, storage, databases, and networking.
Domain 4 – Cost-Optimized (20%)
Design Cost-Optimized Architectures emphasizes choosing the cheapest design that still meets requirements, and continuously monitoring and improving costs.
Well-Architected Framework: The Exam’s Hidden Backbone
What is Well-Architected?
The AWS Well-Architected Framework provides best practices and questions to evaluate how well a workload aligns to AWS architectural guidance.
The Six Pillars
The six pillars are: Operational excellence, Security, Reliability, Performance efficiency, Cost optimization, and Sustainability. Know them in this order.
Security & Reliability
Security focuses on protecting data, systems, and assets using cloud technologies. Reliability is about a workload doing its job correctly and consistently over its lifecycle.
Performance & Cost
Performance efficiency is about using compute resources efficiently as demand and tech change. Cost optimization is about continuously improving to achieve outcomes at minimal cost.
Sustainability
Sustainability focuses on minimizing environmental impacts by maximizing utilization, minimizing resources, and reducing energy needed to deliver business value.
Shared Responsibility and Scenario Thinking
Shared Responsibility Model
AWS is responsible for security of the cloud; customers are responsible for security in the cloud, including how they configure services and protect data.
What AWS Handles
AWS manages data centers, hardware, networking, and managed service internals. You never patch the hypervisor or secure the physical facility.
What You Handle
You configure IAM, security groups, bucket policies, OS patches on EC2, data classification, and backup and recovery strategies for your workloads.
Exam Scenario Pattern
If a company wants to offload ops work, lean toward managed services. If a breach is due to misconfiguration, the fix is on the customer side, not AWS.
Reading Questions Through the Domain and Pillar Lens
Why Tag Domains and Pillars
Before reading options, decide which domain and Well-Architected pillar the scenario is testing. This filters out answers that optimize the wrong thing.
Example 1 – Security vs. Cost
Sensitive health data in S3 with strict protection needs. Security is primary, cost is secondary. The best answer enforces encryption in transit and at rest.
Reasoning Example 1
Versioning helps recovery, Glacier and One Zone-IA help cost, but only enabling SSE-S3 and TLS directly meets security best practices for sensitive data.
Example 2 – Reliability vs. Performance
Single-AZ EC2 app with global users seeing latency and downtime. Reliability and availability are the key issues, not just instance size.
Reasoning Example 2
Only adding an Auto Scaling group across multiple AZs with an ALB truly improves availability and resilience. Other options miss the core problem.
Design Your 4-Week Domain-Focused Study Plan
Now you will sketch a personal study plan that mirrors the four domains instead of jumping randomly between services.
Imagine you have 4 weeks before your first full mock exam in this course. Use this guided exercise to allocate your time.
Step 1: Quick self-assessment
On a scale of 1–5 (1 = very weak, 5 = very strong), rate yourself for each domain:
- Design Secure Architectures (IAM, encryption, network security)
- Design Resilient Architectures (HA, DR, Multi-AZ/Region)
- Design High-Performing Architectures (caching, right-sizing)
- Design Cost-Optimized Architectures (pricing models, storage tiers)
Write your four numbers in your notes.
Step 2: Allocate focus
- Any domain rated 1–2 gets double time.
- Domains rated 4–5 get maintenance time (lighter review, more practice questions).
For example, with 8 hours/week:
- Weak domain (score 1–2): ~3 hours/week
- Medium domain (score 3): ~2 hours/week
- Strong domain (score 4–5): ~1 hour/week
Step 3: Convert to concrete actions
For the coming week, write down:
- One Skarp lesson you will complete for each domain.
- One hands-on lab you will attempt (for example: "build a Multi-AZ web tier with an ALB" for the resilience domain).
- One short quiz or diagnostic you will take at the end of the week.
After you finish this exercise, your next step in this course is to take the diagnostic. Use your diagnostic results plus this self-assessment to refine your plan.
Building a Daily and Weekly Study Rhythm
Daily Study Rhythm
Each day: quick warm-up with flashcards, then a focused lesson, then apply via a lab or quiz. Small, consistent blocks beat long, irregular sessions.
Deep Study and Notes
During deep study, keep notes in four buckets: Security, Resilience, Performance, and Cost. This mirrors the exam domains and sharpens pattern recognition.
Weekly Review
End each week with a mini mock. Tag each missed question by domain and pillar, then let the course’s spaced review queue push weak items back to you.
Why Rhythm Beats Cramming
SAA-C03 tests your ability to see patterns in scenarios. A steady rhythm of study, practice, and review trains those patterns far better than last-minute cramming.
Quiz: Domains and Pillars in Action
Test your understanding of how domains and pillars show up in scenarios.
A media company wants to reduce costs for storing large volumes of infrequently accessed video files while still meeting durability requirements. Which SAA-C03 domain is MOST directly tested, and which Well-Architected pillar is PRIMARY here?
- Domain 4 – Design Cost-Optimized Architectures, Cost optimization pillar
- Domain 2 – Design Resilient Architectures, Reliability pillar
- Domain 3 – Design High-Performing Architectures, Performance efficiency pillar
- Domain 1 – Design Secure Architectures, Security pillar
Show Answer
Answer: A) Domain 4 – Design Cost-Optimized Architectures, Cost optimization pillar
The scenario is about reducing storage costs for infrequently accessed data while maintaining durability. That directly maps to Domain 4 (Design Cost-Optimized Architectures) and the Cost optimization pillar. Reliability and performance matter, but they are not the main focus of the question.
Quiz: Shared Responsibility and Best Answer Selection
Apply the shared responsibility model and domain thinking to a typical exam-style prompt.
An application running on Amazon EC2 was compromised because the OS had not been patched for over a year. According to the AWS shared responsibility model, which change best aligns with AWS best practices and reduces this risk?
- Ask AWS Support to automatically patch the EC2 instances' operating systems.
- Migrate the application to AWS Lambda or a fully managed service where AWS handles OS patching.
- Move the EC2 instances to a different Availability Zone managed by AWS.
- Enable S3 default encryption for all buckets in the account.
Show Answer
Answer: B) Migrate the application to AWS Lambda or a fully managed service where AWS handles OS patching.
Under the shared responsibility model, customers are responsible for OS patching on EC2. One way to reduce this burden is to move to a managed service (such as Lambda or another managed compute platform) where AWS handles the underlying OS. AWS Support cannot take over patching EC2 for you, and changing AZ or S3 encryption does not address the root cause.
Flashcards: Core Orientation Concepts
Use these cards to lock in the must-know definitions and lists for SAA-C03 orientation.
- AWS Well-Architected Framework (definition)
- The AWS Well-Architected Framework provides a consistent set of best practices for customers and partners to evaluate architectures, and a set of questions you can use to evaluate how well an architecture is aligned to AWS best practices.
- List the six AWS Well-Architected Framework pillars in order.
- Operational excellence, Security, Reliability, Performance efficiency, Cost optimization, Sustainability.
- Security pillar (definition)
- The security pillar describes how to take advantage of cloud technologies to protect data, systems, and assets in a way that can improve your security posture.
- Reliability pillar (definition)
- The reliability pillar encompasses the ability of a workload to perform its intended function correctly and consistently when it’s expected to. This includes the ability to operate and test the workload through its total lifecycle.
- Performance efficiency pillar (definition)
- The performance efficiency pillar focuses on the efficient use of computing resources to meet requirements and maintain that efficiency as demand changes and technologies evolve.
- Cost optimization pillar (definition)
- The cost optimization pillar includes the continual process of refinement and improvement of a system over its entire lifecycle to build and operate cost-aware systems that achieve business outcomes and minimize costs.
- Sustainability pillar (definition)
- The sustainability pillar focuses on minimizing the environmental impacts of running cloud workloads by maximizing utilization and minimizing the resources required, and by reducing the energy required to deliver business value.
- AWS shared responsibility model (definition)
- The AWS shared responsibility model describes how AWS is responsible for security of the cloud, while customers are responsible for security in the cloud, including the configuration of their services and data.
- Typical SAA-C03 domain weights (approximate)
- Domain 1 – Design Secure Architectures (~30%); Domain 2 – Design Resilient Architectures (~26%); Domain 3 – Design High-Performing Architectures (~24%); Domain 4 – Design Cost-Optimized Architectures (~20%).
- What is the usual passing scaled score for SAA-C03?
- A scaled score of about 720 out of 1000 is typically required to pass.
- How many minutes do you have for approximately 65 questions on SAA-C03?
- About 130 minutes, which is roughly 2 minutes per question.
Mindset and Tactics for Practice Questions and Labs
Using Practice Questions
For each question, first tag the domain and pillar, then use shared responsibility to eliminate unrealistic options, and finally pick the best, not just a good, answer.
Learning From Mistakes
After quizzes and mocks, review each miss: what domain and pillar did it test, and why was the correct option better? The gap guide will highlight your weakest domains.
Hands-On Labs as Glue
Labs turn theory into intuition. Build small patterns like Multi-AZ web tiers, CloudFront-backed S3 sites, and lifecycle-based backup strategies.
Narrate Domains and Pillars
While doing labs, say out loud which domain and pillar you are practicing. This habit links console actions directly to exam thinking.
Key Terms
- RPO/RTO
- Recovery Point Objective (how much data loss is acceptable) and Recovery Time Objective (how long it can take to restore service) – key metrics in resilience and disaster recovery design.
- Scaled score
- An exam score that has been converted from raw points to a standardized scale (for SAA-C03, 100–1000) to account for differences in exam difficulty.
- SAA-C03 domain
- A major content area of the AWS Solutions Architect – Associate exam, such as Design Secure Architectures or Design Resilient Architectures, each with a specific percentage weight.
- Security pillar
- The security pillar describes how to take advantage of cloud technologies to protect data, systems, and assets in a way that can improve your security posture.
- Reliability pillar
- The reliability pillar encompasses the ability of a workload to perform its intended function correctly and consistently when it’s expected to. This includes the ability to operate and test the workload through its total lifecycle.
- Sustainability pillar
- The sustainability pillar focuses on minimizing the environmental impacts of running cloud workloads by maximizing utilization and minimizing the resources required, and by reducing the energy required to deliver business value.
- Cost optimization pillar
- The cost optimization pillar includes the continual process of refinement and improvement of a system over its entire lifecycle to build and operate cost-aware systems that achieve business outcomes and minimize costs.
- Operational excellence pillar
- One of the six Well-Architected pillars, focusing on running and monitoring systems to deliver business value and continually improving supporting processes and procedures.
- Performance efficiency pillar
- The performance efficiency pillar focuses on the efficient use of computing resources to meet requirements and maintain that efficiency as demand changes and technologies evolve.
- AWS Well-Architected Framework
- The AWS Well-Architected Framework provides a consistent set of best practices for customers and partners to evaluate architectures, and a set of questions you can use to evaluate how well an architecture is aligned to AWS best practices.
- AWS shared responsibility model
- The AWS shared responsibility model describes how AWS is responsible for security of the cloud, while customers are responsible for security in the cloud, including the configuration of their services and data.