A company is launching a global online game using Amazon EC2 instances in three Regions: us-east-1, eu-west-1, and ap-southeast-1. Leaderboards, player inventory, and event status must be available across Regions. Any Region should be able to scale to handle the combined load from all Regions, and users must be automatically routed to the Region with the lowest latency. Which design meets these requirements with the LEAST operational overhead?

The correct option uses Auto Scaling groups with NLBs for scalable compute, which is standard practice. Route 53 latency-based routing automatically directs users to the closest, lowest-latency Region, fulfilling the routing requirement. Amazon DynamoDB global tables provide a fully managed, multi-Region, active-active database solution for game metadata, ensuring high availability, low latency, and automatic replication with minimal operational overhead. Incorrect options: Option 1 uses Global Accelerator, which is good for routing, but RDS read replicas across Regions don't support the active-active, combined load requirement efficiently for writes, and Spot Fleets might be interrupted, impacting availability. Option 2 uses geoproximity routing, which is less precise than latency-based routing for lowest latency, and managing MySQL replication on EC2 instances increases operational overhead significantly. Option 4 uses EC2 Global View (a management tool, not for deployment), custom DNS logic on EC2 instances adds significant operational complexity, and Aurora Global Database is a good choice for data but the compute and routing strategy is overly complex.