An online learning platform stores quiz questions and metadata in an Amazon DynamoDB table. During exams, a surge in user traffic causes high read latency and ProvisionedThroughputExceededException errors when the application retrieves quiz details. The developer wants to introduce Amazon DynamoDB Accelerator (DAX) to optimize query performance with minimal latency and minimal application rewrite. The application currently retrieves quiz details using strongly consistent reads and executes frequent Scan operations to populate list views. Which combination of actions should the developer take to resolve the latency and throttling issues? (Select two.)
- Modify the application's read requests to use eventually consistent reads so that the DynamoDB Accelerator (DAX) client can serve them from the item cache.Answer
- Replace the Scan operations with Query operations to allow DAX to store and serve the retrieved quiz details from the query cache.Answer
- CDeploy an Amazon ElastiCache for Memcached cluster to act as an API-compatible write-through cache for the DynamoDB table.
- DKeep using strongly consistent reads for quiz metadata retrieval to ensure DAX caches the most up-to-date data.
- EUse Scan operations with DAX, relying on DAX to automatically index the results into the item cache for subsequent single-item lookups.
Answer
The correct actions are to modify the read requests to use eventually consistent reads and to replace Scan operations with Query operations.
To resolve the read throttling and latency issues, the developer must configure the read requests to use eventually consistent reads, because DynamoDB Accelerator (DAX) only caches eventually consistent reads; strongly consistent reads are passed directly through to DynamoDB and do not benefit from caching. Additionally, replacing Scan operations with Query operations ensures that the retrieved data is cached in the DAX query cache, which dramatically improves performance compared to executing expensive Scan operations.
Step-by-Step Solution
Key Concept
DAX Caching Behavior and Query Optimization
Estimated Time:2m 0s