An application runs on Amazon EC2 instances behind an Elastic Load Balancer in an Auto Scaling group and uses an Amazon DynamoDB table. The company wants to ensure the application can be made available in another AWS Region with minimal downtime. What should a solutions architect do to meet this requirement with the LEAST downtime?

The correct option ensures minimal downtime by pre-provisioning the core infrastructure (Auto Scaling group and load balancer) in the disaster recovery (DR) Region. This "pilot light" strategy means resources are ready to scale up quickly. Configuring DynamoDB as a global table provides automatic, active-active replication across regions, eliminating the need for manual data synchronization during a failover. DNS failover, typically using Amazon Route 53, allows for rapid redirection of traffic to the DR Region's load balancer. The other options introduce delays. Using CloudFormation templates to create EC2 instances and load balancers when needed (cold standby) takes longer to provision than a pilot light setup. While CloudFormation is excellent for infrastructure as code, launching resources from scratch during a disaster increases recovery time. Relying on a CloudWatch alarm and Lambda function for DNS updates adds complexity and potential latency compared to direct DNS failover configuration.