Answer – B
Option A is incorrect because to benefit from the enhanced networking, all the instances should be in the same Placement Group. Launching the new ones in a new Placement Group will not work in this case.
Option B is CORRECT because the most likely reason for the "Capacity Error" is that the underlying hardware may not have the capacity to launch any additional instances on it. If the instances are stopped and restarted, AWS may move the instances to a hardware that has the capacity for all the requested instances.
Option C is incorrect because there is no such limit on the number of instances in a Placement Group (however, you can not exceed your EC2 instance limit allocated to your account per region).
Option D is incorrect because the capacity error is not related to the instance size and ensures that the instances are of the same size will not resolve the capacity error.
More information on Cluster Placement Group
If you receive a capacity error when launching an instance in a placement group that already has running instances, stop and start all of the instances in the placement group, and try the launch again. Restarting the instances may migrate them to hardware that has the capacity for all the requested instances.
Cluster Placement Groups
A cluster placement group is a logical grouping of instances within a single Availability Zone. A placement group can span peered VPCs in the same region.
Cluster placement groups are recommended for applications that benefit from low network latency, high network throughput, or both. The majority of the network traffic is between the instances in the group. To provide the lowest latency and the highest packet-per-second network performance for your placement group, choose an instance type supporting enhanced networking. For more information, see Enhanced Networking.
We recommend that you launch the number of instances you need in the placement group in a single launch request and use the same instance type for all instances in the placement group. If you try to add more instances to the placement group later or try to launch more than one instance type in the placement group, you increase your chances of getting an insufficient capacity error.
If you stop an instance in a placement group and then start it again, it still runs in the placement group. However, the start fails if there isn`t enough capacity for the instance.
If you receive a capacity error when launching an instance in a placement group that already has running instances, stop and start all of the instances in the placement group and try the launch again. Restarting the instances may migrate them to hardware that has capacity for all the requested instances.
For more information on this, please refer to the below URL
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html
Note:
In this scenario, we are discussing the insufficient capacity error happening within a placement group.
As per AWS docs,
"If you receive a capacity error when launching an instance in a placement group that already has running instances, stop and start all of the instances in the placement group, and try the launch again. Restarting the instances may migrate them to hardware that has capacity for all the requested instances."
In our scenario, we already have 9 EC2 instances running on a placement group. When we tried to add 2 more to the group, we have encountered this error. So if we stop and restart all the instances, it will help resolve this issue as the restarting instances will migrate to a new hardware that will have the capacity for all the instances.
For more information, please refer to:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html