Design Cost-Optimized Architectures

A steady, always-on production fleet is more expensive than necessary. Which TWO actions reduce its cost without hurting the workload? (Select TWO.)

• ACommit to a Savings Plan or Reserved Instances for the steady baseline.
• BRight-size the instances to match their actual utilization.
• CMove the production fleet entirely to interruptible Spot Instances.
• DIncrease every instance to a larger size to reduce their count.
• ERun the fleet on Dedicated Hosts to lower the hourly rate.

Committing to a Savings Plan or RIs discounts the steady baseline, and right-sizing removes over-provisioning — both cut cost safely. Moving production to Spot risks interruptions, upsizing can raise cost, and Dedicated Hosts are more expensive.

A finance team asks for the biggest monthly savings on an over-provisioned, always-on environment. Which THREE actions together reduce cost the most? (Select THREE.)

• ARight-size or terminate underutilized EC2 instances.
• BApply Savings Plans or Reserved Instances to the steady baseline usage.
• CMove infrequently accessed data to lower-cost S3 storage classes.
• DUpsize every instance to the largest type to reduce their count.
• EKeep all idle non-production resources running to stay ready.
• FStore all data in S3 Standard regardless of how often it is accessed.

Right-sizing or terminating waste, committing to Savings Plans/RIs for the steady baseline, and tiering cold data to cheaper storage classes together yield the largest savings. Upsizing everything, leaving idle resources running, and keeping all data in Standard all increase cost.