Study how SAA-C03 frames cost through storage, compute, database, and network design choices rather than isolated pricing trivia.
Cost optimization on SAA-C03 is not a billing-only chapter. AWS tests whether you can spot the cheapest design that still satisfies the workload. That means understanding storage tiers, compute purchasing options, network transfer costs, and when over-design quietly becomes the most expensive mistake in the scenario.
Savings Plans: AWS commitment pricing model that discounts eligible compute usage in exchange for steady spend over time.
Spot: Discounted EC2 capacity with interruption risk when AWS reclaims unused capacity.
NAT gateway: Managed outbound path for private subnets that can become a major cost driver when endpoints would work instead.
Questions in this domain often reuse services you already know from the secure, resilient, or performance chapters. The difference is the deciding constraint. Here the best answer is the one that preserves the required outcome with the lowest justified spend or least waste.
AWS currently weights this domain at 20% of scored content.
Start with 4.1 Storage Solutions, then move to 4.2 Compute Solutions, 4.3 Database Solutions, and 4.4 Network Architectures.
| If the scenario is really about… | Go first to… |
|---|---|
| lifecycle rules, storage classes, EBS sizing, migration method, backup retention | 4.1 Storage Solutions |
| Savings Plans, Spot, Reserved Instances, right-sizing, runtime model | 4.2 Compute Solutions |
| Aurora or RDS sizing, read patterns, DynamoDB capacity mode, cache trade-offs | 4.3 Database Solutions |
| NAT spend, endpoint fit, CloudFront offload, transfer path, cross-AZ charges | 4.4 Network Architectures |
Revisit this chapter when you keep missing questions where:
This chapter lands best after you study resilience and performance first. Cost answers get easier when you already know which architectures are technically valid.