Which actions should the SysOps administrator take to resolve this error?
(Choose two.)
Create a separate AWS CloudFormation template for the EC2 instance.
Modify the AWS CloudFormation template to not specify an Availability Zone for the EC2 instance.
Modify the AWS CloudFormation template to use a different EC2 instance type.
Use a different Amazon Machine Image (AMI) for the EC2 instance.
Use the AWS CLI’s validate-template command before creating a stack from the template.
Explanations:
The InsufficientInstanceCapacity error often occurs because the requested instance type is unavailable in the specified Availability Zone. By not specifying an Availability Zone, CloudFormation will allow EC2 to launch in any available zone where capacity is sufficient.
If the EC2 instance type specified in the template is unavailable due to insufficient capacity, switching to a different instance type with different resource requirements may help resolve the issue.
Creating a separate CloudFormation template for the EC2 instance is unnecessary. The issue is related to resource availability, which can be resolved by adjusting the instance type or Availability Zone, not by splitting the template.
Using a different Amazon Machine Image (AMI) is unlikely to resolve an InsufficientInstanceCapacity error, which is related to capacity limitations of the instance type or Availability Zone, not the AMI itself.
Thevalidate-templatecommand checks for syntactical correctness and schema validity of the template. It doesn’t address runtime capacity issues like InsufficientInstanceCapacity errors, which are related to resource availability.
I compute that the answer is:
Modify the AWS CloudFormation template to not specify an Availability Zone for the EC2 instance.
I think the answer is:
Modify the AWS CloudFormation template to not specify an Availability Zone for the EC2 instance.