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 replication of the existing infrastructure in a new Region with minimal administrative overhead. Parameters can be used for configuration values, making it easier to deploy consistently across different environments.
While documenting the existing infrastructure is useful, using the AWS Management Console to manually recreate the infrastructure in the second Region introduces more administrative overhead and is prone to human error. Automating the process with CloudFormation is a better approach.
Weighted routing in Route 53 would distribute traffic based on specified weights, which is not ideal for disaster recovery scenarios where one Region may be unavailable. This method does not account for latency or user proximity, potentially leading to suboptimal performance.
Latency-based routing in Route 53 directs user traffic to the Region that provides the lowest latency, improving access times for users. This setup is beneficial for a multi-Region application, enhancing both performance and availability.
Enabling DynamoDB Streams and creating a global table allows for data replication across Regions, which is essential for maintaining consistent data availability in a disaster recovery setup. This enables near real-time data synchronization between Regions.
Creating a new DynamoDB table and enabling Streams does not replicate the existing table’s data automatically. This method requires additional steps to copy data, which adds complexity and administrative overhead. A global table approach is more efficient.
It appears 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.