A company is developing a real-time multiplayer game that uses UDP between clients and servers in an Auto Scaling group. The game server platform must scale for spikes in demand, and developers want to store gamer scores and other non-relational data in a database that scales without intervention. Which solution should a solutions architect recommend?

The correct solution uses a Network Load Balancer (NLB) for traffic distribution and Amazon DynamoDB on-demand for data storage. NLBs are ideal for real-time multiplayer games because they operate at Layer 4, support UDP traffic, and can handle millions of requests per second with ultra-low latency. DynamoDB on-demand provides a fully managed, serverless NoSQL database that automatically scales to meet fluctuating demand for gamer scores and other non-relational data, eliminating the need for manual intervention. Using Amazon Route 53 for traffic distribution is incorrect because it is a DNS service, not a load balancer for active game traffic. Amazon Aurora Serverless is a relational database and might not be the best fit for non-relational game data requiring extreme scalability without intervention. Amazon Aurora Global Database is also relational and designed for global distribution, not the primary scaling need here. An Application Load Balancer (ALB) is incorrect because it operates at Layer 7 and does not natively support UDP traffic, which is specified for the game. DynamoDB global tables are for multi-region replication, not the core scaling requirement for a single region's fluctuating demand.