AWS Certified Developer - Associate
Get started today
Ultimate access to all questions.
A widely used mobile application is designed to retrieve data from an AWS DynamoDB table, which has been configured with read-capacity units (RCUs) evenly distributed across four partitions. However, one particular partition is experiencing significantly higher traffic compared to the other partitions, leading to hot partition problems.
Which technology can you implement to decrease the read traffic on your AWS DynamoDB table with minimal effort?
A widely used mobile application is designed to retrieve data from an AWS DynamoDB table, which has been configured with read-capacity units (RCUs) evenly distributed across four partitions. However, one particular partition is experiencing significantly higher traffic compared to the other partitions, leading to hot partition problems.
Which technology can you implement to decrease the read traffic on your AWS DynamoDB table with minimal effort?
Explanation:
DynamoDB DAX
Amazon DynamoDB Accelerator (DAX) is a fully managed, highly available, in-memory cache for DynamoDB that delivers up to a 10x performance improvement: from milliseconds to microseconds: even at millions of requests per second.
Incorrect options:
DynamoDB Streams - A stream record contains information about a data modification to a single item in a DynamoDB table. This is not the correct option for the given use-case.
ElastiCache - ElastiCache can cache the results from anything but you will need to modify your code to check the cache before querying the main query store. As the given use-case mandates minimal effort, so this option is not correct.
More partitions - This option has been added as a distractor as DynamoDB handles that for you automatically.