A SysOps administrator exported a CloudFormation template of existing infrastructure in us-west-2 and tried to use that same template to create a stack in eu-west-1. The stack failed partway through, returned an error, and rolled back. Which two reasons could explain this failure? (Choose two.)

When deploying CloudFormation templates across regions, you must ensure that all referenced resources and services are available in the target region. AMIs are region-specific, so an AMI ID valid in us-west-2 will likely not exist in eu-west-1, causing stack creation to fail. Similarly, not all AWS services are available in every region. If the template attempts to provision a resource from a service not offered in eu-west-1, the stack creation will fail. The other options are less likely or incorrect. IAM users are global resources, so referencing one wouldn't typically cause a regional deployment failure. Insufficient IAM permissions would likely cause a failure at the very beginning, not "partway through." CloudFormation templates are primarily used to create new resources, not just update existing ones.