Q: 18
A developer is working on an ecommerce application that stores data in an Amazon RDS for MySQL
cluster The developer needs to implement a caching layer for the application to retrieve information
about the most viewed products.
Which solution will meet these requirements?
Options
Discussion
B . ElastiCache (Redis) is meant for a caching layer, especially for read-heavy data like most viewed products. D just adds a standby for failover, doesn't cache anything. The DynamoDB DAX option is a trap since it's not for MySQL/RDS. Pretty sure B fits the scenario best.
B or C? Had something like this in a mock, stuck between those two.
C vs B? Always see AWS pushing DAX in practice tests for these caching layers, even though it's really for DynamoDB not MySQL. Wouldn't rule C work here too?
Seen similar on official practice, pretty sure it's B here.
I’d say B since ElastiCache Redis is built exactly for this use case, not DAX and not a standby replica.
B or D? D feels right if they want high availability, but I think it's a common trap here.
D imo. Provisioned concurrency is made for this, since it keeps Lambda environments pre-warmed so you avoid unpredictable cold start delays. Pretty sure that's the only way to guarantee setup happens before invocation-saw this asked in some exam reports too.
Be respectful. No spam.
