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: encryption that burns CPU likes compute-optimized C, while in-memory analytics likes roomy R. One family for everything—or forcing burstable credits / storage-optimized boxes—misses the performance target.
Full Explanation
EC2 instance families align to resource bottlenecks: compute-optimized (C) families favor CPU-intensive work such as encryption pipelines, while memory-optimized (R) families favor large in-memory analytics datasets. Selecting by bottleneck is a core Task 3.2 skill. Using a single mismatched family or burstable credits as a universal default undermines predictable high performance.