Real-time Gaming Leaderboard with ElastiCache Persistence

SAA-C03 By islever Editorial Last updated

Short answer

C Deploy an Amazon ElastiCache for Redis cluster with AOF persistence to provide fast, persistent access to player rankings.

Question

A video game company is deploying a new gaming application to its global users. The company requires a solution that will provide near real-time reviews and rankings of the players. A solutions architect must design a solution to provide fast access to the data. The solution must also ensure the data persists on disks in the event that the company restarts the application. Which solution will meet these requirements with the LEAST operational overhead?
  1. Configure an Amazon CloudFront distribution with an Amazon S3 bucket as the origin. Store the player data in the S3 bucket.
  2. Create Amazon EC2 instances in multiple AWS Regions. Store the player data on the EC2 instances. Configure Amazon Route 53 with geolocation records to direct users to the closest EC2 instance.
  3. Deploy an Amazon ElastiCache for Redis duster. Store the player data in the ElastiCache cluster. Correct Answer
  4. Deploy an Amazon ElastiCache for Memcached duster. Store the player data in the ElastiCache cluster.

Key Takeaways

The core trap is confusing volatile caching with persistent storage; Redis must be configured with AOF or RDB snapshots to meet the 'persists on disks' requirement unlike Memcached.

This question evaluates the selection of an in-memory data store for low-latency gaming leaderboards that requires disk persistence. The correct solution leverages Amazon ElastiCache for Redis to balance speed and durability.

Common mistake: Candidates often choose Memcached (D) because it is simpler, but it lacks built-in persistence features, causing data loss on restarts which violates the scenario constraints.

Expert Analysis

Why the Answer Is Correct

Amazon ElastiCache for Redis (Option C) is the optimal choice because it provides sub-millisecond latency suitable for near real-time rankings while supporting data persistence via Append-Only File (AOF) or RDB snapshots. This ensures that player review data survives application or node restarts, satisfying the durability requirement without the operational overhead of managing EC2 instances or complex S3/CloudFront setups.

Why the Other Options Are Wrong

Option A (S3/CloudFront) introduces significant latency due to object storage semantics and caching invalidation challenges, failing the 'near real-time' test. Option B (EC2) incurs high operational overhead for patching, scaling, and managing database software manually. Option D (Memcached) is a pure in-memory cache with no persistence mechanism, meaning all data would be lost upon restart, directly contradicting the prompt's requirements.

Community Comment Notes

Community consensus strongly supports Redis due to its specific persistence capabilities. As user officedepotadmin noted, "Redis supports data persistence by snapshotting data to disk... ensuring that the data is not lost." Another commenter emphasized using AOF specifically: "To be more exact, you should use Amazon ElastiCache for Redis with AOF (Append-Only File) persistence." Users also highlighted Redis features like Sorted Sets which are ideal for leaderboard logic.

Official Reference

Exam Strategy

Always check for persistence requirements when comparing ElastiCache engines. If the question demands data survival after restarts, choose Redis over Memcached. If it demands absolute lowest latency with no persistence needs, Memcached might be considered, but Redis is generally preferred for modern stateful apps.

Frequently Asked Questions

Why not use DynamoDB for this?

While DynamoDB persists data, ElastiCache Redis offers lower latency for frequent read/write updates typical in real-time leaderboards.

Does Memcached have any persistence?

No, Memcached is purely in-memory. Any restart results in total data loss, making it unsuitable for this requirement.

More SAA-C03 FAQ →

Community Votes

C
100%

100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

  1. officedepotadmin 👍 4 Answered C
    Amazon ElastiCache for Redis provides in-memory caching which ensures low latency and high throughput, perfect for near real-time access to player reviews and rankings. Redis supports data persistence by snapshotting data to disk (RDB snapshots) and appending changes to a log (AOF), ensuring that the data is not lost even if the application restarts.
  2. Bwhizzy 👍 2 Answered C
    REDIS • Multi AZ with Auto-Failover • Read Replicas to scale reads and have high availability • Data Durability using AOF persistence • Backup and restore features • Supports Sets and Sorted Sets
  3. LeonSauveterre 👍 1 Answered C
    To be more exact, you should use Amazon ElastiCache for Redis with AOF (Append-Only File) persistence. BTW, all the "duster"s in the options should be "cluster"s.
  4. Salilgen 👍 1 Answered C
    https://aws.amazon.com/blogs/database/building-a-real-time-gaming-leaderboard-with-amazon-elasticache-for-redis/

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Practice All SAA-C03 Questions

Access 120 questions with complete answers and detailed explanations.

View Full SAA-C03 Practice Test →

← Back to SAA-C03 Study Guide