Flood-modeling jobs are tightly coupled HPC-style tasks where inter-node latency dominates runtime. What placement strategy should the architect use?
Select an answer to reveal the explanation.
Short Explanation
When model nodes must gossip quickly, seat them close together in a cluster placement group—distance is the enemy of tightly coupled flood jobs.
Full Explanation
Cluster placement groups pack instances into low-latency network proximity for tightly coupled HPC-style workloads. Spreading across Regions or continents increases latency; skipping placement strategy leaves performance to chance. When inter-node latency matters, cluster placement groups are the Task 2.5 pattern.