A gaming company must rehost its gaming platform on AWS. The platform requires high-performance compute, and the leaderboard updates frequently. Currently an Ubuntu compute-optimized instance runs a Node.js front end. Game state is stored in an on-premises Redis instance. The migration should optimize application performance in AWS. Which solution meets these requirements?

The correct solution uses c5.large EC2 On-Demand Instances because c5 instances are compute-optimized, aligning with the "high-performance compute" requirement for the Node.js front end. On-Demand instances provide consistent availability, crucial for a gaming platform, unlike Spot Instances which can be interrupted. An Application Load Balancer (ALB) distributes traffic efficiently. Amazon ElastiCache for Redis is the ideal choice for the leaderboard because Redis is an in-memory data store known for its extremely low latency and high throughput, perfect for frequently updated leaderboards. Incorrect options: Using m5.large instances is less optimal as m5 instances are general-purpose, not specifically compute-optimized. Spot Instances are unsuitable due to potential interruptions. Amazon OpenSearch Service is a search and analytics engine, not designed for low-latency, high-frequency key-value operations like a leaderboard. DynamoDB is a NoSQL database, but ElastiCache for Redis offers superior performance for real-time leaderboards due to its in-memory nature.