Which combination of actions should be taken to address the latency issues?

Explanations:

Creating a new DynamoDB table with cross-Region replication enabled would not be effective for minimizing latency. Instead, using global tables is a better approach for maintaining low-latency access to the database from different regions.

This option suggests creating global resources which AWS does not support. Load balancers and auto scaling groups are region-specific. Therefore, you cannot create them as global resources; each region requires its own setup.

Creating new ALB and Auto Scaling group resources in the new Region allows for local traffic handling and better performance for users in that region. This setup minimizes latency for the new office by ensuring that requests are processed in the same geographical area.

Implementing Amazon Route 53 with health checks and latency-based routing allows the application to route user requests to the closest ALB, thereby reducing latency and improving availability. This approach ensures users are directed to the optimal resources based on their location.

Failover routing policies are not suitable for this scenario since they are designed for primary and backup resources, not for minimizing latency across multiple locations. Latency-based routing is more appropriate here.

Converting the DynamoDB table to a global table allows for automatic replication of data across regions, ensuring low-latency access to the database for users in both regions, which is essential for performance improvement.