Caching RDS Read Records Without Schema Changes
An application is experiencing performance issues based on increased demand. This increased demand is on read-only historical records pulled from an Amazon RDS-hosted database with custom views and queries. A developer must improve performance without changing the database structure. Which approach will improve performance and MINIMIZE management overhead?
Community Insight
The question tests choosing a fully managed read cache for RDS while respecting both constraints—no database structure change and minimal operational overhead—so the trap is picking a self-managed or schema-migrating option.
When read-only historical records from an Amazon RDS database with custom views and queries slow down under load, the fastest fix that leaves the schema untouched is a managed caching layer. Amazon ElastiCache (Redis OSS) fronts those queries, absorbing read traffic while keeping management overhead near zero.
Option C (Memcached on Amazon EC2) is the most common wrong pick: it does cache reads, but you must provision, patch, monitor, and handle failover yourself, which directly violates the 'MINIMIZE management overhead' requirement.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Amazon ElastiCache (Redis OSS) is a fully managed service, so AWS handles provisioning, patching, backups, and node replacement while the developer only issues cache reads and writes. Because it sits in front of the existing RDS instance, the custom views and queries stay exactly as they are, satisfying the 'without changing the database structure' constraint. Read-only historical records are an ideal caching pattern: they are queried repeatedly and change rarely, so cache hit rates stay high and offloaded RDS reads relieve the performance bottleneck. AlmeroSenior's comment captures both halves of this: Redis is "Fully manged, and does not require DB structure to be changed, like moving to Dynamo would."Why the Other Options Are Wrong
Option A requires moving all data to Amazon DynamoDB and repointing the application, which rewrites the data model, abandons the custom SQL views and queries, and represents a substantial migration effort rather than a quick optimization. Option C would work functionally, but running Memcached on Amazon EC2 means you own the operating system, the Memcached OSS software, capacity planning, and single-point-of-failure risks—exactly the management overhead the question tells you to minimize, as AlmeroSenior noted that hosting on EC2 "is by nature a single point of failure." Option D is technically incoherent: DynamoDB Accelerator is an in-memory write-through cache for DynamoDB tables and cannot be deployed 'on Amazon RDS,' which is a relational engine. PashoQ's remark that "Managing OSS app does not fit least management" points the same direction as the correct choice—self-managed OSS caching on EC2 contradicts the least-overhead constraint.Community Comment Notes
The community is split, with AlmeroSenior selecting B and both PashoQ and 0bdf3af selecting C, yet the written reasoning is inconsistent: PashoQ's own text argues that managing an OSS application "does not fit least management," which argues against the C option that commenter selected. 0bdf3af simply asserts "memcache fits" without addressing the explicit management-overhead clause in the question stem. Reading the comments on their merits rather than their vote counts, the reasoning in favor of a fully managed ElastiCache layer is the only one that satisfies both stated constraints simultaneously.Official Reference
Exam Strategy
Read the qualifier in the stem first—here both 'without changing the database structure' and 'MINIMIZE management overhead' must be satisfied simultaneously, so any option that migrates data or requires self-managing servers on EC2 is eliminated before you compare caching speeds.
Frequently Asked Questions
Why is Memcached on Amazon EC2 wrong when it also caches reads?
Because it forces you to manage the EC2 instance, the Memcached software, patching, and failover yourself, violating the 'MINIMIZE management overhead' requirement that ElastiCache satisfies as a managed service.
Can DynamoDB Accelerator (DAX) improve caching for an Amazon RDS database?
No. DAX is an in-memory cache designed exclusively for Amazon DynamoDB tables and cannot be deployed against an RDS instance or its custom views and queries.
Related Analysis
Practice All DVA-C02 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DVA-C02 Practice Test →