A handful of critical license servers must not run on the same underlying hardware. They may be placed in more than one Availability Zone. Which placement group matches that requirement?
Select an answer to reveal the explanation.
Short Explanation
You would not hang both spare keys on the same nail. A spread placement group puts each of these few critical servers on distinct hardware, including across Availability Zones, so one host does not take the set with it. A cluster group packs them together, and skipping a placement group does not promise each server its own hardware.
Full Explanation
A spread placement group places each instance on distinct hardware. That is the constraint for this handful of license servers: they must not share a host, and they are allowed to sit in more than one Availability Zone, which a spread group can do. A cluster placement group packs instances close together on the same underlying hardware inside one zone. That is the opposite of keeping the license servers apart, and it cannot span zones. A partition placement group is built for a large distributed fleet, divided into partitions so the loss of one partition is not the loss of the whole group. It is not the tool for a few servers that each need their own hardware. Launching with no placement group gives no promise that the instances land on different hosts. The scheduler can still place them together. Caveat: a spread group accepts only a small number of instances in each Availability Zone, which fits a handful of license servers and not a large fleet. Operational check: after launch, confirm each license server is in that spread placement group and in the Availability Zone you chose.