Cover the storage, compute, database, network, and ingestion choices that drive performance decisions on the current SAA-C03 exam guide.
Performance on SAA-C03 is broader than “make it faster.” AWS now breaks this domain into five task groups because performance can come from storage shape, database design, edge placement, scaling policy, and ingestion architecture as much as from raw compute.
IOPS: Input/output operations per second, one of the main storage-performance signals in AWS volume and database scenarios.
EBS / EFS / FSx: Elastic Block Store, Elastic File System, and the FSx managed file-system families, which solve different storage-performance patterns.
ALB / NLB: Application Load Balancer versus Network Load Balancer, which usually means Layer 7 routing versus Layer 4 traffic handling.
Expect questions that ask which layer is the real bottleneck. Candidates lose points when they jump to bigger instances before checking storage class, caching, access patterns, endpoint placement, or the ingestion path feeding the workload.
AWS currently weights this domain at 24% of scored content.
Start with 3.1 Storage Solutions, then 3.2 Compute Solutions, 3.3 Database Solutions, 3.4 Network Architectures, and 3.5 Data Ingestion & Transformation.
| If the scenario is really about… | Go first to… |
|---|---|
| storage type, IOPS, throughput, EBS/EFS/FSx/S3 fit | 3.1 Storage Solutions |
| EC2 versus Lambda versus containers, scaling signal, runtime fit | 3.2 Compute Solutions |
| Aurora, RDS, DynamoDB, ElastiCache, read scaling, hot partitions | 3.3 Database Solutions |
| ALB versus NLB, CloudFront, Global Accelerator, Direct Connect, PrivateLink | 3.4 Network Architectures |
| transfer services, stream ingestion, Glue, Athena, transformation path | 3.5 Data Ingestion & Transformation |
Before you pick a service, ask in this order:
Revisit this chapter when:
This is a high-noise chapter, so keep the glossary and resources nearby while you study it.