An application runs in a single AWS Region on EC2 instances behind an ALB with Auto Scaling and uses DynamoDB. A new office on another continent suffers high latency. How should you reduce latency and improve availability for users in both Regions? (Choose three)

To reduce latency and improve availability, you need to deploy resources closer to the new office and intelligently route traffic. Creating new ALB and Auto Scaling group resources in the new Region (and configuring the new ALB to direct traffic to the new Auto Scaling group) establishes a local presence for the application. This brings the compute layer closer to the users, directly reducing network latency. Converting the DynamoDB table to a global table provides multi-Region replication for the database, ensuring low-latency data access for users in both Regions and enhancing data availability. Finally, creating Amazon Route 53 records, health checks, and latency-based routing policies allows Route 53 to automatically direct users to the closest healthy ALB, optimizing their experience. Creating a new DynamoDB table with cross-Region replication is less efficient than a global table, which is designed for multi-Region active-active use cases. Creating new ALB and Auto Scaling group global resources is incorrect because ALBs and Auto Scaling groups are regional services, not global. Using Route 53 aliases with failover routing is primarily for high availability within a single region or active-passive multi-region, not for latency-based routing across active-active regions.