Which combination of steps should the solutions architect take to meet these requirements?
(Choose three.)
Create an AWS CloudFormation template for the current infrastructure design. Use parameters for important system values, including Region. Use the CloudFormation template to create the new infrastructure in the second Region.
Use the AWS Management Console to document the existing infrastructure design in the first Region and to create the new infrastructure in the second Region.
Update the Route 53 hosted zone record for the application to use weighted routing. Send 50% of the traffic to the ALB in each Region.
Update the Route 53 hosted zone record for the application to use latency-based routing. Send traffic to the ALB in each Region.
Update the configuration of the existing DynamoDB table by enabling DynamoDB Streams. Add the second Region to create a global table.
Create a new DynamoDB table. Enable DynamoDB Streams for the new table. Add the second Region to create a global table. Copy the data from the existing DynamoDB table to the new table as a one-time operation.
Explanations:
Creating an AWS CloudFormation template allows for the automation of infrastructure deployment. By using parameters, the template can be reused to replicate the existing infrastructure in the second Region with minimal administrative overhead. This is efficient for managing environments and supports disaster recovery planning.
While documenting the existing infrastructure is useful, using the AWS Management Console to manually recreate the infrastructure in the second Region increases administrative overhead and the potential for errors. This approach does not support automation or efficient replication of the environment.
Weighted routing in Route 53 would distribute traffic based on specified weights but does not consider latency or performance, which is crucial for a disaster recovery setup. It’s not an optimal solution for ensuring improved access times to users across Regions.
Latency-based routing in Route 53 directs users to the Region that provides the lowest latency, optimizing access times. This setup is essential for a multi-Region application, especially for users in different geographic locations. It enhances performance and supports disaster recovery by allowing traffic to be rerouted efficiently.
Enabling DynamoDB Streams and creating a global table allows for automatic replication of data across Regions. This ensures that the data is continuously synchronized, which is critical for disaster recovery and maintaining consistent access to data in both Regions.
While creating a new DynamoDB table and enabling Streams could work, it involves more manual steps, such as copying data as a one-time operation. This is less efficient than using global tables, which automatically handle replication and synchronization, thus increasing administrative overhead.
It seems to me that the answer is:
Create an AWS CloudFormation template for the current infrastructure design. Use parameters for important system values, including Region. Use the CloudFormation template to create the new infrastructure in the second Region.