DVA-C02 · Question #232
A developer has built a market application that stores pricing data in Amazon DynamoDB with Amazon ElastiCache in front. The prices of items in the market change frequently. Sellers have begun complai
The correct answer is A. The cache is not being invalidated when the price of the item is changed.. In a caching setup using Amazon ElastiCache in front of Amazon DynamoDB, if the cache is not being invalidated or updated when data in DynamoDB is changed, it can result in stale data being served from the cache, leading to the observed behavior. To resolve this issue, you should
Question
A developer has built a market application that stores pricing data in Amazon DynamoDB with Amazon ElastiCache in front. The prices of items in the market change frequently. Sellers have begun complaining that, after they update the price of an item, the price does not actually change in the product listing. What could be causing this issue?
Options
- AThe cache is not being invalidated when the price of the item is changed.
- BThe price of the item is being retrieved using a write-through ElastiCache cluster.
- CThe DynamoDB table was provisioned with insufficient read capacity.
- DThe DynamoDB table was provisioned with insufficient write capacity.
How the community answered
(18 responses)- A72% (13)
- B17% (3)
- C11% (2)
Explanation
In a caching setup using Amazon ElastiCache in front of Amazon DynamoDB, if the cache is not being invalidated or updated when data in DynamoDB is changed, it can result in stale data being served from the cache, leading to the observed behavior. To resolve this issue, you should implement a mechanism to invalidate or update the cache whenever the price of an item is changed in DynamoDB to ensure that the most up-to-date data is retrieved from the cache or DynamoDB.
Community Discussion
No community discussion yet for this question.