A company deployed a multiplayer mobile game that requires live location tracking of players using latitude and longitude. The data store must support rapid updates and retrieval of locations. The game stores location data in an Amazon RDS for PostgreSQL DB instance with read replicas, but during peak usage the database cannot maintain required read/write performance. The user base is rapidly increasing. What should a solutions architect do to improve data-tier performance?

The correct answer is to deploy an Amazon ElastiCache for Redis cluster. ElastiCache for Redis is an in-memory data store that provides extremely low-latency reads and writes, making it ideal for caching frequently accessed data like player locations. By caching location data in Redis, the application can offload a significant amount of read traffic from the RDS PostgreSQL instance, improving overall performance and scalability. The game application would need to be modified to interact with the Redis cache before querying the database. Taking a snapshot and enabling Multi-AZ does not directly address performance bottlenecks; Multi-AZ is for high availability, not performance scaling. Migrating to Amazon OpenSearch Service is not suitable as OpenSearch is primarily for search and analytics, not a high-performance key-value store for rapid location updates. Deploying DAX is for Amazon DynamoDB, not RDS for PostgreSQL.