SAP-C02 Continuous Improvement for Existing Solutions Practice Question

Exhibit

Refer to the exhibit.

{
  "AWSTemplateFormatVersion": "2010-09-09",
  "Resources": {
    "EC2Instance": {
      "Type": "AWS::EC2::Instance",
      "Properties": {
        "ImageId": "ami-0abcdef1234567890",
        "InstanceType": "t2.micro"
      }
    },
    "MyQueue": {
      "Type": "AWS::SQS::Queue",
      "Properties": {
        "QueueName": "my-queue"
      }
    }
  }
}

A CloudFormation stack is created using the template above. The stack creation fails with the error: 'The following resource(s) failed to create: [EC2Instance]'. Logs show: 'AMI 'ami-0abcdef1234567890' does not exist.' What is the most likely cause?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The AMI ID is not available in the region where the stack is being deployed.

The error 'AMI does not exist' indicates that the hardcoded AMI ID in the CloudFormation template is not available in the region where the stack is being deployed. AMI IDs are region-specific, so using a hardcoded ID from another region causes the failure. Option B is incorrect because the SQS queue name collision would result in a different error. Option C is incorrect because AMI IDs are alphanumeric by design. Option D is incorrect because the error specifically mentions the AMI, not the instance type.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
The AMI ID is not available in the region where the stack is being deployed.
Why this is correct
AMI IDs are region-specific; hardcoding can cause cross-region failures.
✗
The SQS queue name 'my-queue' is already in use.
Why it's wrong here
The error is about EC2Instance, not SQS.
✗
The AMI ID is invalid because it contains letters.
Why it's wrong here
AMI IDs contain letters and are valid.
✗
The instance type t2.micro is not supported in the region.
Why it's wrong here
t2.micro is widely supported.

Go deeper

SAP-C02 Continuous Improvement for Existing Solutions Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question