County IT runs overnight batch GIS rendering and daytime in-memory analytics on citizen datasets. How should EC2 instance families be chosen for performance?
Select an answer to reveal the explanation.
Short Explanation
Match the engine to the race: compute-optimized for heavy GIS number-crunching, memory-optimized when the whole dataset wants to live in RAM.
Full Explanation
Instance family selection should follow workload characteristics. Compute-optimized families suit CPU-bound batch GIS; memory-optimized families suit in-memory analytics. One-size burstable fleets, HDD storage-optimized for RAM-bound work, or unnecessary GPUs misalign cost and performance. Purpose-matched families meet Task 2.5 performance design.