Q: 2
A solutions architect has launched multiple Amazon EC2 instances in a placement group within a
single Availability Zone. Because of additional load on the system, the solutions architect attempts to
add new instances to the placement group. However, the solutions architect receives an insufficient
capacity error.
What should the solutions architect do to troubleshoot this issue?
Options
Discussion
Option B
C or B. Spread groups aren't the same as cluster, so A doesn't fit and merging placement groups isn't a thing (C feels off). Pretty sure AWS docs say stop/start all instances (B) can fix capacity issues, but it's downtime. Could be missing a detail here.
Nah, I don’t think it’s D. B is the right troubleshooting step since stopping and starting lets AWS move the group to hardware with enough capacity. Option A is a trick-spread placement groups work differently. Anyone see this behave otherwise?
A tbh, using a spread placement group sounds like it'd help with capacity errors since it distributes instances across hardware. Stopping/starting everything (B) feels risky for downtime. Not totally sure though, maybe missing something about how spread works in this case?
B imo. Had something like this in a mock and stopping/starting lets AWS find new hardware for the whole group, which usually solves these capacity errors. Creating a new placement group won’t help if you need them all together. Agree?
Be respectful. No spam.
