KindleYou is a location-based social search mobile app that allows users to like or dislike other users, and allows users to chat if both parties liked each other in the app. It has more than 1 billion customers across the world.
They use DynamoDB to support the mobile application and S3 to host the images and other documents shared between users.
DynamoDB has a table with 60 partitions and is being heavily accessed by users. The queries run by users do not fully use the per-partition’s throughput. In less than 3 minutes, a heavy load of queries flow in and this happens occasionally. Sometimes there are many background tasks that are running in background. How does DynamoDB handle the workload?

Answer options:

A.using Burst Capacity effectively
B.using Adaptive Capacity
C.Design Partition Keys to distribute workload evenly
D.Using Write Sharding to Distribute Workloads Evenly

Answer: A
Option A is correct - DynamoDB provides some flexibility in your per-partition throughput provisioning by providing burst capacity. DynamoDB reserves a portion of that unused capacity for later bursts of throughput to handle usage spikes.
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-partition-key-design.html#bp-partition-key-partitions-adaptive
Option B is incorrect -Adaptive Capacity enables your application to continue reading and writing to hot partitions without being throttled, provided that traffic does not exceed your table’s total provisioned capacity or the partition maximum capacity
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-partition-key-design.html#bp-partition-key-partitions-adaptive