You are developing a mobile application for your company with DynamoDB as the back end and JavaScript as the front end. During the daytime, you notice that sometimes there are spikes in the application, especially in the DynamoDB write throughput. What would be the most cost-effective and scalable architecture for this application?

Answer options:

A.Enable DynamoDB Auto Scaling to meet the requirements.
B.Increase the write capacity of DynamoDB tables by 20% to meet the peak loads.
C.Create a service that pulls SQS messages and writes them to DynamoDB to handle sudden spikes in DynamoDB.D.Launch DynamoDB in Multi-AZ configuration with a global index to balance writes.

Correct Answer – A
Option A is CORRECT because with DynamoDB Auto Scaling, DynamoDB can automatically increase its write capacity for the spike and decrease the throughput after the spike.
Option B is incorrect because the extra write capacity is a waste after the spike. It is not a cost-efficient solution.
Option C is incorrect because the new SQS is not cost-efficient, and it is not needed after the spike.
Option D is incorrect because this causes extra costs and is not a cost-efficient solution.
For more information on DynamoDB auto-scaling, please refer to the below URL-
https://aws.amazon.com/blogs/aws/new-auto-scaling-for-amazon-dynamodb/
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ProvisionedThroughput.html