AWS Certified Solutions Architect – Professional (SAP-C02) — Question 473
A company is migrating infrastructure for its massive multiplayer game to AWS. The game’s application features a leaderboard where players can see rankings in real time. The leaderboard requires microsecond reads and single-digit-millisecond write latencies. The datasets are single-digit terabytes in size and must be available to accept writes in less than a minute if a primary node failure occurs.
The company needs a solution in which data can persist for further analytical processing through a data pipeline.
Which solution will meet these requirements with the LEAST operational overhead?
Answer options
- A. Create an Amazon ElastiCache tor Redis cluster with cluster mode enabled, Configure the application to interact with the primary node.
- B. Create an Amazon ROS database with a read replica. Configure the application to point writes to the writer endpoint. Configure the application to point reads to the reader endpoint.
- C. Create an Amazon MemoryDB for Redis cluster in Muit-AZ mode Configure the application to interact with the primary node.
- D. Create multiple Redis nodes on Amazon EC2 instances that are spread across multiple Availability Zones. Configure backups to Amazon S3.
Correct answer: C
Explanation
Amazon MemoryDB for Redis is a fully managed, Redis-compatible, durable in-memory database that delivers microsecond reads and single-digit millisecond writes, with Multi-AZ failover taking less than a minute. Amazon ElastiCache for Redis (Option A) is not designed as a primary, durable database for data persistence out-of-the-box, and Amazon RDS (Option B) cannot support microsecond read latencies. Managing Redis on Amazon EC2 (Option D) would meet the performance needs but incurs high operational overhead compared to the fully managed MemoryDB service.