A global online gaming company is launching a new massively multiplayer online (MMO) game. The game backend needs to store player profiles, game state, and leaderboard data. This data must support millions of concurrent users, provide extremely low-latency access (single-digit milliseconds), and scale globally across multiple AWS regions for high availability and disaster recovery. Data consistency for critical game state is crucial. Which AWS database solution is the most appropriate for this scenario?

Why the other options are wrong

• B. ElastiCache for Redis provides in-memory caching for extremely low latency, but it's a caching layer, not a primary persistent database solution for game state and profiles that require strong consistency and global multi-master writes.
• C. Aurora Global Database provides fast cross-region replication for disaster recovery and read scaling, but its write latency for multi-master global writes is typically higher than DynamoDB's single-digit millisecond guarantee for this specific use case.
• D. RDS with read replicas offers read scaling and disaster recovery but does not provide the global multi-master write capabilities with single-digit millisecond latency needed for a globally distributed MMO game backend.