A county security office runs CPU-bound encryption jobs and a separate in-memory analytics workload. Which instance-family guidance is appropriate?
Select an answer to reveal the explanation.
Short Explanation
Pick the chassis for the bottleneck: CPU-bound encryption likes compute-optimized instances, while in-memory analytics likes memory-optimized instances. One family for everything—or forcing burstable credits or storage-optimized boxes—misses the performance target.
Full Explanation
EC2 families align to bottlenecks: compute-optimized instances favor CPU-intensive encryption pipelines, while memory-optimized instances favor large in-memory analytics datasets. Selecting by bottleneck is a core Task 3.2 skill. Using memory-optimized instances for both is wrong because RAM does not always beat CPU for encryption. Using burstable instances exclusively is wrong because shared credit pools undermine predictable high performance. Using storage-optimized instances as a default is wrong because these jobs are not storage-bottlenecked.