Study SAP-C02 Cost Optimization Strategy for New Solutions: key concepts, common traps, and exam decision cues.
Cost optimization in a new design is about avoiding unnecessary cost from the beginning. SAP-C02 expects you to notice when charges will come from data transfer, oversized compute, the wrong storage class, or an overbuilt architecture.
| Need | Strongest first fit | Why |
|---|---|---|
| reduce steady-state compute cost | rightsize and match purchase model | compute often dominates spend |
| lower storage cost over time | lifecycle policy and proper storage class | storage economics depend on access pattern |
| reduce needless network charges | minimize NAT, cross-AZ, TGW, and public-transfer overhead where possible | transfer cost is a common hidden trap |
| cut ops-heavy platform cost | use managed or serverless services when they fit | operations cost is part of total cost |
| handle interruptions for cheaper capacity | Spot Instances | low-cost compute for tolerant workloads |
| Trap | Better rule |
|---|---|
| optimizing only instance price | storage and transfer patterns can be just as important |
| choosing commitment purchases before usage is stable | Savings Plans and RIs fit predictable workloads better |
| keeping every object in the hottest storage tier | storage class should match access frequency |
| ignoring managed-service savings in operations | total cost includes people and platform effort, not just raw AWS price |
Cost-design questions usually reward matching spending controls to the usage pattern. If data cools after an initial period, think lifecycle policies and colder storage classes. If network architecture choices move lots of traffic, check transfer and processing charges. If compute is stable, think commitment-based pricing. SAP-C02 often hides cost signals inside ordinary architecture decisions.