A GIS team needs EC2 instances for CPU-heavy overnight batch crunching of parcel maps. Which instance family category best fits that workload?
Select an answer to reveal the explanation.
Short Explanation
Parcel crunching that burns CPU all night wants compute-optimized EC2—think race-car engines, not giant cargo holds. Storage-optimized and memory-optimized shine for disk and RAM-heavy jobs; tiny burstable bastions are the wrong gear for serious batch GIS.
Full Explanation
AWS EC2 instance families align to workload traits: compute-optimized types emphasize high-performance processors for CPU-bound jobs such as GIS batch processing. Storage-optimized and memory-optimized families target high disk throughput and large in-memory working sets, respectively. Selecting the matching family improves performance and cost efficiency. CLF candidates should map civic batch CPU work to compute-optimized instances rather than defaulting to unrelated families.