How to Cache Dynamic RDS Data for Low-Latency Reads?

DVA-C02 By islever Editorial Last updated

Short answer

D Create an Amazon ElastiCache for Redis cluster. Update the application code to use a write-through caching strategy and read the data from Redis.

Question

A company has a social media application that receives large amounts of traffic. User posts and interactions are continuously updated in an Amazon RDS database. The data changes frequently, and the data types can be complex. The application must serve read requests with minimal latency. The application's current architecture struggles to deliver these rapid data updates efficiently. The company needs a solution to improve the application's performance. Which solution will meet these requirements?
  1. Use Amazon DynamoDB Accelerator (DAX) in front of the RDS database to provide a caching layer for the high volume of rapidly changing data.
  2. Set up Amazon S3 Transfer Acceleration on the RDS database to enhance the speed of data transfer from the databases to the application.
  3. Add an Amazon CloudFront distribution in front of the RDS database to provide a caching layer for the high volume of rapidly changing data.
  4. Create an Amazon ElastiCache for Redis cluster. Update the application code to use a write-through caching strategy and read the data from Redis. Correct Answer

Key Takeaways

Tests cache technology selection for dynamic workloads, where candidates frequently misapply static CDN or NoSQL accelerators to relational databases.

This question evaluates optimal caching architectures for high-traffic, frequently updated relational databases. The community consensus strongly recommends Amazon ElastiCache for Redis paired with a write-through strategy to ensure low latency and data consistency.

Common mistake: Option C (CloudFront) is commonly selected due to its popularity, but it cannot efficiently cache highly dynamic database queries or complex RDS responses because it relies on fixed TTLs and edge-origin caching models unsuited for real-time data.

Expert Analysis

Why the Answer Is Correct

Amazon ElastiCache for Redis excels at delivering sub-millisecond read latency and natively supports complex data structures like hashes, lists, and sets, directly matching the application's needs. Implementing a write-through caching strategy guarantees that every update is persisted to both the cache and RDS simultaneously, eliminating cache inconsistency issues. This architecture effectively offloads read traffic from the primary database while maintaining strong data freshness.

Why the Other Options Are Wrong

DAX (Option A) is exclusively engineered for DynamoDB and lacks native integration with relational databases like RDS, making it architecturally invalid. CloudFront (Option C) caches HTTP responses at edge locations and struggles with highly dynamic, personalized, or frequently updated database content due to strict TTL constraints and lack of query-level optimization. S3 Transfer Acceleration (Option B) only speeds up object uploads and downloads via the CloudFront network and plays no role in accelerating database operations.

Community Comment Notes

Candidates overwhelmingly agree on Redis as the correct choice, with several highlighting the exam heuristic "complex data equals Redis" as a reliable decision-making shortcut. Multiple comments correctly point out that CloudFront is strictly designed for static web assets, reinforcing why Option C fails for database workloads. One highly upvoted response references the official AWS whitepaper on database caching patterns, which validates the write-through approach for consistency-critical scenarios.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

Match workload traits to caching services: choose Redis for complex, high-frequency dynamic data and Memcached for simple session states. Always verify service compatibility with your underlying data store before selecting an accelerator option.

Community Votes

D
100%

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

Discussion 10 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 10

  1. SerialiDr 👍 3 Answered D
    This option is the most suitable for the described scenario. Amazon ElastiCache for Redis can act as a high-performance, in-memory data store and cache, which is ideal for applications that require fast access to data. Implementing a write-through caching strategy ensures that data is written to the cache and the primary data store (RDS) simultaneously, keeping the cache up to date. Reading data from the cache can significantly reduce latency and the load on the RDS database, making it an optimal solution for applications with high read demand.
  2. be1dca8 👍 2
    D Cloud Front is generally used to distribute static content such as images, stylesheets, and scripts. CloudFront is not typically used for caching database queries or dynamic data directly from databases like RDS.
  3. ANDRES715 👍 1
    R. Utilice Amazon DynamoDB Accelerator (DAX) frente a la base de datos RDS para proporcionar una capa de almacenamiento en caché para el gran volumen de datos que cambian rápidamente. Al utilizar Amazon DynamoDB Accelerator (DAX) frente a la base de datos RDS, se puede proporcionar una capa de almacenamiento en caché para el gran volumen de datos que cambian rápidamente. DAX mejora el rendimiento de las consultas de lectura al almacenar en caché los resultados de las consultas más frecuentes, lo que reduce la latencia y mejora la capacidad de respuesta de la aplicación. Es importante tener en cuenta que DynamoDB Accelerator (DAX) es una opción eficiente para mejorar el rendimiento de aplicaciones que requieren un acceso rápido a datos que cambian con frecuencia, como en el caso de una aplicación de redes sociales.
  4. be1dca8 👍 1
    D is generally used to distribute static content such as images, stylesheets, and scripts. CloudFront is not typically used for caching database queries or dynamic data directly from databases like RDS.
  5. KarBiswa 👍 1 Answered D
    https://docs.aws.amazon.com/whitepapers/latest/database-caching-strategies-using-redis/caching-patterns.html
Show 5 more comments
  1. 65703c1 👍 2 Answered D
    D is the correct answer.
  2. Abdullah22 👍 2 Answered D
    going with cash D
  3. CrescentShared 👍 1 Answered D
    hesitate between C and D.
  4. Abdullah22 👍 1
    cash , complex = redis
  5. monishvster 👍 1 Answered D
    Should be D

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.

How to Log Every Lambda Invocation to an SQS Queue?

S-grade

How to Test Updated Lambda Functions with a Subset of Users Using API Gateway?

S-grade

How to automate S3 object tagging after delayed third-party content audit?

S-grade

How to automatically rotate encryption keys for API keys in serverless apps with no development effort?

S-grade

Practice All DVA-C02 Questions

Access 100 questions with complete answers and detailed explanations.

View Full DVA-C02 Practice Test →

← Back to DVA-C02 Study Guide