A distributed big-data cluster of many EC2 instances runs a replicated storage layer where each rack-equivalent group should fail independently of the others, so a single hardware fault must not take down more than one group at once. The team wants AWS to spread the instances across distinct underlying hardware in controllable failure isolation groups. Which EC2 placement group strategy fits this requirement?
- AA cluster placement group, packing the instances close together in one Availability Zone for the lowest inter-node network latency.
- BA spread placement group, placing each individual instance on distinct hardware up to the small per-zone instance limit.
- CA partition placement group, dividing the instances into partitions that each sit on a separate rack of underlying hardware. Correct
- DNo placement group, relying on launching the instances across several Availability Zones to provide the hardware isolation.
Why A is wrong: A cluster group optimises latency by packing instances onto nearby hardware, which concentrates rather than isolates failures and works against the requirement.
Why B is wrong: A spread group isolates a handful of critical instances but is capped at seven per Availability Zone, so it cannot host a large distributed cluster.
Why C is correct: A partition placement group splits instances into partitions on distinct racks, so a hardware fault is contained to one partition, matching the replicated storage isolation need.
Why D is wrong: Spreading across zones helps availability but gives no control over rack-level partition isolation, leaving the replicated layout unaligned with hardware fault domains.