A SysOps administrator has created an Amazon EC2 instance using an AWS CloudFormation template in the us-east-1 Region. The administrator finds that this template has failed to create an EC2…

Question

Options

• AResource tags defined in the CloudFormation template are specific to the us-east-1 Region.
• BThe Amazon Machine Image (AMI) ID referenced in the CloudFormation template could not be
• CThe cfn-init script did not run during resource provisioning in the us-west-2 Region.
• DThe IAM user was not created in the specified Region.

• A
  5% (1)
• B
  89% (17)
• D
  5% (1)

Explanation

AMI IDs are region-specific, meaning an AMI ID valid in us-east-1 (e.g., ami-0abcd1234) does not exist in us-west-2 - CloudFormation will fail during stack creation because it cannot locate the referenced image. This is a common real-world pitfall when reusing templates across regions without updating AMI mappings (often solved using CloudFormation Mappings with per-region AMI IDs).

Why the distractors are wrong:

• A - Resource tags are not region-specific; the same tag key/value pairs work in any region.
• C - cfn-init failures would typically result in a different error (stack rollback after the instance launches), not a failure to create the instance at all - and this isn't the primary cause of cross-region failures.
• D - IAM is a global service; IAM users are not region-scoped and are available across all regions automatically.

Memory tip: Think "AMI = Address specific to My region." Whenever you copy a CloudFormation template to a new region, AMI IDs are the first thing to update - use Mappings or AWS::SSM::Parameter lookups to make templates region-agnostic.

No community discussion yet for this question.