1.5 Determine cost optimization and visibility strategies.
1.An analytics platform uses a large fleet of EC2 Spot Instances for batch processing. The jobs are tolerant to interruptions, but frequent terminations are causing unacceptable delays. The team wants to improve the resilience of the Spot fleet while still maximizing cost savings. Which two strategies should they implement in their EC2 Fleet or Auto Scaling Group configuration?(Select 2)
- A.Select only the newest-generation instance types, as they have the lowest interruption frequency.
- B.Enable Capacity Rebalancing to allow EC2 to proactively launch a replacement Spot Instance before an existing one receives a two-minute interruption notice.
- C.Set a very high Spot max price, well above the On-Demand price, to guarantee that instances will not be interrupted.
- D.Diversify the fleet across multiple instance types and families that meet the job's minimum vCPU and memory requirements.
- E.Confine the Spot fleet to a single Availability Zone to minimize inter-AZ data transfer costs.
Show answer & explanation
Correct answers: B, D — Enable Capacity Rebalancing to allow EC2 to proactively launch a replacement Spot Instance before an existing one receives a two-minute interruption notice.; Diversify the fleet across multiple instance types and families that meet the job's minimum vCPU and memory requirements.
- A. Incorrect. While newer-generation instance types might have lower interruption frequencies due to larger capacity pools, this is not a guaranteed rule. More importantly, limiting the fleet to a single instance type (or even generation) is an anti-pattern that reduces diversity and makes the entire fleet vulnerable to interruptions in that specific capacity pool.
- B. Correct. Capacity Rebalancing is a key feature for improving Spot Instance resilience. It allows Amazon EC2 to proactively launch a replacement Spot Instance when an existing instance receives a rebalance recommendation, which indicates it is at an elevated risk of interruption. This helps maintain the desired fleet capacity and reduces delays by replacing instances before they are terminated.
- C. Incorrect. Spot Instance interruptions are primarily driven by AWS needing the capacity back for On-Demand or Reserved Instance usage, not by the price exceeding your maximum bid. Setting a high max price does not prevent these capacity-based interruptions. The default max price is the On-Demand price, which is sufficient in most cases.
- D. Correct. Diversification is a fundamental best practice for using Spot Instances effectively. By configuring the fleet to use multiple instance types, families, and generations that meet the application's minimum requirements (e.g., vCPU, memory), you tap into different Spot capacity pools. This strategy significantly reduces the impact of an interruption in any single pool, thereby increasing the overall availability and resilience of the application.
- E. Incorrect. Confining the fleet to a single Availability Zone concentrates risk and reduces resilience. A best practice is to diversify across multiple Availability Zones. This allows the fleet to pull capacity from different, isolated locations, making it much less likely that a capacity shortage in one AZ will impact the entire fleet.