SAA-C03 — AWS Certified Solutions Architect – Associate Quick Review

Concise SAA-C03 Quick Review for AWS architecture decisions, high-yield traps, and IT Mastery question-bank practice.

Quick Review purpose

This Quick Review is for candidates preparing for the real AWS Certified Solutions Architect – Associate (SAA-C03) exam from AWS. Use it to refresh high-yield architecture decisions before moving into topic drills, mock exams, and detailed explanations.

The SAA-C03 exam is not mainly a memorization test. It rewards choosing the AWS service or architecture pattern that best satisfies requirements such as:

  • High availability and fault tolerance
  • Security and least privilege
  • Performance and scalability
  • Cost optimization
  • Operational simplicity
  • Migration constraints
  • Data durability, retention, and access patterns

This page is IT Mastery review support and is not affiliated with AWS.

How to think like SAA-C03

Many questions describe a business workload and ask for the best or most cost-effective architecture. The right answer usually follows from the stated constraints.

If the question says…Think first about…Common trap
“Least operational overhead”Managed or serverless servicesChoosing EC2 because it is familiar
“Highly available across AZs”Multi-AZ design, managed HA, load balancingSingle EC2 instance, single NAT gateway, single DB instance
“Decouple components”SQS, SNS, EventBridge, KinesisDirect synchronous calls between services
“Cost-effective for variable traffic”Auto Scaling, serverless, Spot where appropriateOverprovisioned always-on instances
“Static website or static assets”S3 plus CloudFrontEC2 web servers for static content
“Shared file system for Linux EC2”Amazon EFSEBS attached to multiple instances generally not the right default
“Object storage, massive scale”Amazon S3EFS or EBS for object-style data
“Relational database with minimal admin”Amazon RDS or AuroraSelf-managed database on EC2
“NoSQL key-value, single-digit millisecond access”DynamoDBRDS when no relational features are needed
“Real-time streaming ingestion”Kinesis Data Streams / Firehose / MSKSQS for ordered streaming analytics
“Hybrid private connectivity”Site-to-Site VPN, Direct Connect, Transit GatewayPublic internet without stated acceptability
“Global low-latency content delivery”CloudFrontMulti-Region EC2 without caching

Core architecture principles

Availability, durability, and fault tolerance

ConceptSAA-C03 review
AvailabilityCan users access the system when needed? Use Multi-AZ, load balancing, Auto Scaling, health checks, and failover.
DurabilityIs data preserved after hardware or service failures? Use S3, backups, replication, snapshots, and managed database durability features.
Fault toleranceCan the workload keep running after component failure? Design without single points of failure.
Disaster recoveryHow quickly and how much data can be recovered? Understand backup/restore, pilot light, warm standby, and multi-site active-active at a conceptual level.
ElasticityCan capacity increase and decrease automatically? Use Auto Scaling, serverless services, and managed scaling.

Shared responsibility model

AWS is responsible for security of the cloud. Customers are responsible for security in the cloud.

AreaAWS responsibilityCustomer responsibility
Physical data centersFacilities, hardware, physical controlsSelect Regions/AZs as needed
Managed services infrastructureUnderlying hosts and service platformConfigure access, encryption, networking, logging
EC2Physical host, hypervisorOS patching, security groups, IAM, app security
S3Storage infrastructureBucket policies, public access settings, encryption choices, lifecycle
RDSManaged database platformDB configuration, user access, backups/retention choices, parameter settings

Exam trap: AWS manages more for serverless and managed services, but customers still configure identity, access, data classification, network exposure, and logging.

Networking and VPC review

VPC fundamentals

FeatureWhat to remember
VPCIsolated virtual network in a Region.
SubnetLives in one Availability Zone. Public/private depends on routing, not the name.
Public subnetRoute table sends internet-bound traffic to an Internet Gateway.
Private subnetNo direct route to Internet Gateway for inbound internet access.
Internet GatewayAllows public internet connectivity for resources with public IPs and proper routing.
NAT GatewayLets private subnet resources initiate outbound internet traffic. Managed and preferred over NAT instances for most exam scenarios.
Route tableControls where network traffic is directed.
Security groupStateful instance-level or ENI-level firewall. Allows rules only.
Network ACLStateless subnet-level firewall. Allows and denies rules.
VPC endpointPrivate access to supported AWS services without using public internet paths.

Security groups vs network ACLs

Decision pointSecurity groupNetwork ACL
ScopeENI/resource levelSubnet level
StateStatefulStateless
Rule typeAllow onlyAllow and deny
Return trafficAutomatically allowedMust be explicitly allowed
Common useControl instance or load balancer trafficBroad subnet guardrails or explicit deny patterns

Common candidate mistake: Choosing a network ACL when the question asks for normal application access control. Security groups are the default control for instance-level access.

Public, private, and database subnets

WorkloadTypical placement
Public load balancerPublic subnets across multiple AZs
EC2 application serversPrivate subnets behind a load balancer
RDS databasePrivate subnets in a DB subnet group
NAT GatewayPublic subnet, with private subnets routing outbound internet traffic through it
Bastion host, if usedPublic subnet, tightly restricted inbound access

VPC connectivity options

NeedGood AWS option
Connect VPCs one-to-oneVPC peering
Connect many VPCs and on-premises networks centrallyTransit Gateway
Private connection from on-premises to AWSDirect Connect
Encrypted tunnel over internetSite-to-Site VPN
Private access to AWS services from VPCVPC endpoints
Private service exposure across VPCs/accountsAWS PrivateLink
Hybrid DNS resolutionRoute 53 Resolver endpoints

Trap: VPC peering is not transitive. If VPC A peers with B and B peers with C, A does not automatically reach C through B.

Route 53, CloudFront, and edge networking

ServiceUse when…
Route 53You need DNS, health checks, routing policies, domain registration, or failover routing.
CloudFrontYou need global content delivery, caching, TLS at the edge, signed URLs/cookies, or lower latency for static/dynamic content.
Global AcceleratorYou need static anycast IPs and optimized routing to regional endpoints, often for non-HTTP or latency-sensitive apps.
AWS WAFYou need web-layer filtering, managed rules, IP sets, or protection against common web exploits.
ShieldYou need DDoS protection capabilities.

Route 53 routing policy quick table

Routing policyBest fit
SimpleBasic DNS response, no special routing logic
WeightedSplit traffic by percentage, such as blue/green or A/B
Latency-basedSend users to the Region with lowest latency
FailoverActive-passive failover using health checks
GeolocationRoute based on user location
GeoproximityRoute by geographic proximity, optionally with bias
Multivalue answerReturn multiple healthy records

Compute and load balancing

EC2 purchasing and capacity

OptionBest fitWatch for
On-DemandShort-term, unpredictable workloadsHigher cost than commitment models
Reserved InstancesSteady EC2 usage with commitmentLess flexible than On-Demand
Savings PlansFlexible commitment-based savingsApplies depending on plan type and usage
Spot InstancesFault-tolerant, interruptible workloadsCan be interrupted; not ideal for critical single-instance apps
Dedicated HostsCompliance or licensing requiring physical host visibility/controlHigher cost and management overhead
Capacity ReservationsNeed capacity assurance in a specific AZDoes not automatically reduce cost unless combined appropriately

Auto Scaling

FeatureReview point
Launch templatePreferred modern way to define EC2 configuration for Auto Scaling.
Desired capacityTarget number of instances.
Minimum/maximumBounds for scaling.
Scaling policyAdds/removes capacity based on metrics or schedules.
Health checksAuto Scaling can replace unhealthy instances.
Multi-AZUse subnets in multiple AZs for high availability.

Trap: Auto Scaling improves elasticity and availability, but it does not by itself make a stateful application safe. Store state outside instances, such as in RDS, DynamoDB, EFS, S3, or ElastiCache.

Elastic Load Balancing

Load balancerLayerUse when…
Application Load BalancerLayer 7HTTP/HTTPS routing, host/path rules, containers, WebSockets, target groups
Network Load BalancerLayer 4Very high performance TCP/UDP/TLS, static IP needs, low latency
Gateway Load BalancerLayer 3/4 appliance insertionDeploying third-party virtual appliances like firewalls
Classic Load BalancerLegacyUsually not the preferred answer for new architectures

Containers and serverless compute

ServiceBest fit
LambdaEvent-driven serverless functions, short-lived tasks, minimal infrastructure management
ECSManaged container orchestration on AWS
EKSKubernetes workloads on AWS
FargateServerless compute engine for containers; no EC2 management
Elastic BeanstalkPlatform management for applications with less infrastructure control
App RunnerSimple managed container/web app deployment
BatchBatch jobs, queues, and compute environments

Decision rule: If the question emphasizes “run containers without managing servers,” look for Fargate. If it emphasizes “Kubernetes,” look for EKS.

Storage review

S3 high-yield concepts

FeatureWhat to know
BucketRegional container for objects. Bucket names are globally unique.
ObjectData plus metadata, addressed by key.
VersioningPreserves multiple versions and helps recover from accidental deletion/overwrite.
Lifecycle policiesMove or expire objects based on age/rules to optimize cost.
ReplicationCopy objects across buckets, often cross-Region or same-Region.
S3 Object LockWrite-once-read-many retention use cases.
Block Public AccessImportant guardrail against accidental public exposure.
Bucket policyResource-based access policy for bucket/object permissions.
Presigned URLTime-limited access to a private object.
Transfer AccelerationFaster long-distance uploads using edge locations.
Event notificationsTrigger workflows via Lambda, SQS, or SNS.

S3 storage class selection

Storage classBest fit
S3 StandardFrequently accessed data
S3 Intelligent-TieringUnknown or changing access patterns
S3 Standard-IAInfrequently accessed data needing rapid access
S3 One Zone-IAInfrequently accessed, re-creatable data stored in one AZ
S3 Glacier Instant RetrievalArchive data needing immediate retrieval
S3 Glacier Flexible RetrievalArchive data with flexible retrieval time
S3 Glacier Deep ArchiveLowest-cost long-term archive with slower retrieval

Common trap: Do not choose One Zone-IA for data that must remain resilient to AZ loss unless the scenario says the data is easily re-created.

EBS, EFS, FSx, and instance store

StorageScopeBest fit
EBSBlock storage for EC2 in one AZBoot volumes, databases on EC2, low-latency block storage
EFSManaged NFS file system across AZsShared Linux file storage for multiple instances
FSx for Windows File ServerManaged Windows file sharesSMB, Windows workloads, Active Directory integration
FSx for LustreHigh-performance file systemHPC, analytics, ML, fast processing of large datasets
Instance storeTemporary local storageEphemeral cache/scratch data; data lost on stop/terminate depending on instance behavior

Trap: EBS volumes are AZ-scoped. If an EC2 instance needs access in another AZ, snapshots can be used to create a new volume there, but EBS is not a regional shared file system.

Storage decision path

    flowchart TD
	    A[Need storage?] --> B{Object, block, or file?}
	    B -->|Object| C[S3]
	    B -->|Block for EC2| D[EBS]
	    B -->|Shared Linux file| E[EFS]
	    B -->|Windows file share| F[FSx for Windows File Server]
	    B -->|HPC fast file processing| G[FSx for Lustre]
	    C --> H{Access pattern known?}
	    H -->|Frequent| I[S3 Standard]
	    H -->|Unknown or changing| J[S3 Intelligent-Tiering]
	    H -->|Archive| K[S3 Glacier classes]

Databases and caching

Relational database choices

ServiceBest fit
Amazon RDSManaged relational databases such as MySQL, PostgreSQL, MariaDB, Oracle, and SQL Server
Amazon AuroraAWS-designed relational database compatible with MySQL/PostgreSQL, often chosen for performance, scaling, and managed HA
RDS Multi-AZHigh availability and automatic failover
RDS read replicaRead scaling and, in some cases, cross-Region read/disaster recovery patterns
Aurora ReplicasRead scaling and failover targets within Aurora clusters
RDS ProxyConnection pooling for applications, especially Lambda-heavy relational workloads

Trap: Multi-AZ is for availability/failover, not read scaling in the usual SAA-C03 decision pattern. Read replicas are for read scaling.

NoSQL and purpose-built databases

ServiceBest fit
DynamoDBServerless key-value/document database, high-scale low-latency access
DynamoDB global tablesMulti-Region active-active access patterns
DynamoDB DAXIn-memory cache for DynamoDB read acceleration
ElastiCache for Redis/MemcachedIn-memory caching, session stores, low-latency reads
MemoryDB for RedisDurable Redis-compatible in-memory database
RedshiftData warehousing and analytics
OpenSearch ServiceSearch, log analytics, full-text queries
NeptuneGraph database
DocumentDBMongoDB-compatible document workloads
TimestreamTime series data
KeyspacesApache Cassandra-compatible workloads
QLDBLedger database with immutable transaction log

Database decision rules

RequirementLikely answer
SQL, joins, transactions, managed operationsRDS or Aurora
Need relational HA across AZsRDS Multi-AZ or Aurora
Scale reads for relational workloadRead replicas
Key-value access at massive scaleDynamoDB
Microsecond caching layerElastiCache
Data warehouse reportingRedshift
Search across logs/documentsOpenSearch Service
Graph relationshipsNeptune
Immutable verifiable ledgerQLDB

Security, identity, and encryption

IAM essentials

ConceptReview point
IAM userLong-term identity; avoid for applications when roles are possible.
IAM groupCollection of users; permissions management for users.
IAM roleAssumable identity with temporary credentials; preferred for AWS services.
IAM policyJSON permissions document.
Identity-based policyAttached to users, groups, or roles.
Resource-based policyAttached to resources such as S3 buckets, KMS keys, SQS queues, or Lambda functions.
STSProvides temporary security credentials.
Least privilegeGrant only required actions on required resources.
MFAStronger authentication, especially for privileged access.

Common trap: Applications running on EC2 should usually use an IAM role attached to the instance profile, not stored access keys.

AWS Organizations controls

FeatureUse
AWS OrganizationsCentral account management
Organizational unitsGroup accounts by function, environment, or governance boundary
Service control policiesSet maximum available permissions for accounts/OUs
Consolidated billingCentralized billing across accounts

Trap: An SCP does not grant permissions. It only limits what can be granted by identity/resource policies.

KMS and secrets

NeedService or feature
Managed encryption keysAWS KMS
Customer-managed key policies and rotation controlKMS customer managed keys
Store and rotate database credentialsAWS Secrets Manager
Store configuration parameters and simple secretsSystems Manager Parameter Store
Encrypt S3 objectsSSE-S3, SSE-KMS, or client-side encryption depending on requirements
Encrypt EBS volumesEBS encryption using KMS
Encrypt RDSRDS encryption using KMS, generally chosen at creation or via snapshot workflows

Logging and detection

ServiceUse
CloudTrailAPI activity and account governance audit trail
CloudWatchMetrics, logs, alarms, dashboards
AWS ConfigResource configuration history, compliance rules
GuardDutyThreat detection using logs and behavior analysis
Security HubCentral security findings and posture management
InspectorVulnerability management for supported workloads
MacieSensitive data discovery in S3
IAM Access AnalyzerAnalyze external access and policy findings

Trap: CloudWatch is not the same as CloudTrail. CloudWatch monitors metrics/logs; CloudTrail records API activity.

Application integration and decoupling

Messaging and event services

ServiceBest fit
SQS Standard queueDecouple producers/consumers with high throughput and at-least-once delivery
SQS FIFO queueOrdered processing and exactly-once processing behavior within FIFO design constraints
SNSPub/sub fanout to subscribers
EventBridgeEvent bus, SaaS/AWS service events, routing by event patterns
Kinesis Data StreamsReal-time streaming data ingestion and custom consumers
Kinesis Data FirehoseLoad streaming data into destinations like S3, Redshift, OpenSearch, or third-party services
Step FunctionsOrchestrate workflows and stateful business processes
Amazon MQManaged message broker for protocols/apps needing broker compatibility

SQS review points

FeatureMeaning
Visibility timeoutTime a message is hidden after a consumer receives it. Set long enough for processing.
Dead-letter queueCaptures messages that fail repeatedly.
Long pollingReduces empty responses and cost.
Delay queue/message timerPostpones message availability.
FIFO queueOrdering and deduplication use cases.

Common trap: If one message must be delivered to many subscribers, use SNS fanout, not a single SQS queue with multiple competing consumers.

Reliability and disaster recovery patterns

High-availability patterns

RequirementArchitecture pattern
Web app highly available across AZsALB across public subnets, EC2 Auto Scaling across private subnets
Managed relational DB failoverRDS Multi-AZ or Aurora
Stateless application tierStore sessions externally, use Auto Scaling
Static content high availabilityS3 with CloudFront
Queue-based workload resilienceSQS plus Auto Scaling consumers and DLQ
Global failoverRoute 53 health checks and failover routing, or appropriate multi-Region design

Disaster recovery approaches

PatternReview meaning
Backup and restoreLowest cost, slower recovery
Pilot lightMinimal critical core running, scale up during disaster
Warm standbyScaled-down full environment ready to expand
Multi-site active-activeMultiple active environments, fastest recovery, highest complexity/cost

Exam decision rule: If the question asks for the lowest cost DR option and can tolerate slower recovery, backup and restore is usually favored. If it asks for very fast recovery, warm standby or active-active may be more appropriate.

Migration, hybrid, and data transfer

NeedAWS service
Database migration with minimal downtimeAWS Database Migration Service
Convert database schema between enginesAWS Schema Conversion Tool
Transfer large datasets onlineAWS DataSync
SFTP/FTPS/FTP managed endpointsAWS Transfer Family
Offline bulk data transferAWS Snow Family
Hybrid storage integrationAWS Storage Gateway
Discover on-premises inventoryAWS Application Discovery Service
Rehost servers to AWSAWS Application Migration Service
Central backup managementAWS Backup

Storage Gateway types

TypeUse
File GatewayFile interface to S3-backed storage
Volume GatewayBlock storage with cached or stored volume patterns
Tape GatewayVirtual tape replacement for backup workflows

Monitoring, operations, and governance

ServiceHigh-yield use
CloudWatch AlarmsAlert or trigger actions based on metrics
CloudWatch LogsCentralize application/system logs
CloudWatch Logs InsightsQuery logs
X-RayTrace distributed applications
Systems ManagerPatch, run commands, manage inventory, Session Manager access
AWS BackupCentral backup policies across supported services
Trusted AdvisorRecommendations across cost, security, fault tolerance, performance, and service limits
Service QuotasView/request quota increases
Health DashboardAWS service events and account-specific health
Control TowerMulti-account landing zone governance

Trap: For secure shell access without opening inbound SSH, Systems Manager Session Manager is often a better answer than a bastion host, assuming prerequisites are met.

Cost optimization review

Cost levers

AreaReview actions
ComputeRight-size instances, use Auto Scaling, Savings Plans/Reserved Instances for steady usage, Spot for interruptible workloads
StorageChoose correct S3 storage class, lifecycle old data, delete unused EBS volumes/snapshots
DatabasesSelect appropriate engine, use read replicas only when needed, scale capacity to workload
NetworkingWatch NAT Gateway data processing, cross-AZ traffic, data transfer out, and unnecessary public paths
MonitoringSet budgets, alarms, and cost allocation tags
ArchitecturePrefer managed/serverless where it reduces idle capacity and operations

Cost tools

ToolUse
AWS BudgetsTrack spend or usage against thresholds
Cost ExplorerAnalyze historical cost and usage
Cost and Usage ReportsDetailed billing data for analysis
Compute OptimizerRightsizing recommendations for supported resources
Pricing CalculatorEstimate architecture costs before deployment

Common trap: “Cheapest” is not always “best.” If the scenario requires high availability, durability, or compliance, avoid options that save money by violating stated requirements.

High-yield service comparison tables

S3 vs EBS vs EFS

RequirementChoose
Store images, backups, logs, static assetsS3
Boot volume for EC2EBS
Block storage for database on EC2EBS
Shared POSIX file system across Linux EC2 instancesEFS
Long-term archiveS3 Glacier storage classes
Temporary scratch data tied to an instanceInstance store

ALB vs NLB vs CloudFront

RequirementChoose
Path-based or host-based HTTP routingALB
TCP/UDP, extreme performance, static IP supportNLB
Global caching and edge deliveryCloudFront
Web application firewall at edge or ALBAWS WAF with CloudFront or ALB
Fixed global entry IPs with regional endpointsGlobal Accelerator

SQS vs SNS vs EventBridge vs Kinesis

RequirementChoose
Buffer work between producers and consumersSQS
Fanout notifications to multiple subscribersSNS
Event routing from AWS/SaaS/custom appsEventBridge
Ordered high-volume streaming analyticsKinesis Data Streams
Load streaming data into S3/Redshift/OpenSearchKinesis Data Firehose
Coordinate multi-step workflowStep Functions

RDS Multi-AZ vs read replica

RequirementChoose
Automatic failover for relational DBMulti-AZ
Scale read trafficRead replica
Cross-Region read localityCross-Region read replica where supported
Improve write scalingUsually not read replicas; consider architecture/database choice
Reduce admin for connection stormsRDS Proxy

Common SAA-C03 traps

Trap 1: Ignoring “managed” and “least operational overhead”

If two answers work technically, the exam often favors the one with less administration when the scenario requests minimal operations.

Less optimalOften better
Self-managed MySQL on EC2RDS or Aurora
EC2 fleet for event functionsLambda
EC2-hosted queue/broker without needSQS, SNS, EventBridge, or Amazon MQ depending on requirement
Manual scalingAuto Scaling or serverless scaling

Trap 2: Confusing HA with scalability

Design goalMeaning
High availabilitySurvive failure and remain accessible
ScalabilityHandle increased load
ElasticityAutomatically scale up/down
DurabilityPreserve data

An Auto Scaling group may improve both availability and scalability, but an RDS read replica mostly improves read scalability, while Multi-AZ improves availability.

Trap 3: Choosing public access when private access is required

If the question asks for private connectivity to AWS services, consider:

  • VPC gateway endpoints for supported services such as S3 and DynamoDB
  • VPC interface endpoints powered by PrivateLink for many AWS services
  • Private subnets with no direct inbound internet route
  • Direct Connect or VPN for hybrid connectivity

Trap 4: Misreading “real-time”

“Real-time” can point to different services:

ScenarioLikely service
Streaming click events for custom consumersKinesis Data Streams
Deliver streaming data into S3Kinesis Data Firehose
Pub/sub application notificationSNS
Event routing between applicationsEventBridge
Queue-based background processingSQS

Trap 5: Overusing Multi-Region

Multi-Region designs can improve disaster recovery and latency but add cost and complexity. If the question only requires high availability within a Region, Multi-AZ is often enough.

Trap 6: Forgetting state

Stateless compute is easier to scale and replace. Store state in managed external services:

State typeCommon service
User sessionsElastiCache, DynamoDB, application-managed external store
Uploaded filesS3
Shared application filesEFS or FSx
Relational dataRDS or Aurora
Key-value dataDynamoDB

Fast final-review checklist

Before answering an SAA-C03 scenario question, ask:

  1. What is the primary requirement? Cost, availability, security, performance, or operational simplicity?
  2. Is the workload stateful or stateless?
  3. Does it need relational features, key-value scale, file storage, object storage, or block storage?
  4. Is traffic synchronous, queued, pub/sub, event-driven, or streaming?
  5. Is the architecture single-AZ, Multi-AZ, or Multi-Region?
  6. Does the question require private connectivity or public access?
  7. Can a managed or serverless service reduce operational overhead?
  8. Are there hidden cost drivers such as idle capacity, cross-AZ transfer, NAT processing, or overprovisioned storage?
  9. Does the proposed answer satisfy every stated constraint, not just one?
  10. Does any answer add unnecessary complexity?

Practice connection

Use this Quick Review as a final concept pass, then move into IT Mastery practice with original practice questions. The fastest way to improve for AWS Certified Solutions Architect – Associate (SAA-C03) is to test service selection under realistic constraints:

  • Start with focused topic drills on weak areas such as VPC networking, S3 storage classes, RDS vs DynamoDB, IAM/KMS, and decoupling.
  • Review detailed explanations for both correct and incorrect answers.
  • Track repeated mistakes by decision type, not just by service name.
  • Then use timed mock exams to practice reading scenario wording quickly.

Next step: choose one weak domain, complete a short question bank drill, and review every explanation until you can state why the best answer is better than the plausible distractors.

Continue in IT Mastery

Use this Quick Review as a final concept map, then move into IT Mastery for focused topic drills, mixed practice sets, timed mock exams, and detailed explanations. The practice questions are original IT Mastery practice items; they are not official AWS questions, copied live-exam content, or exam dumps.

Browse Certification Practice Tests by Exam Family