SAA-C03 Question 473
Single answerA startup is developing a new analytics platform for processing user behavior data. They expect high read and write throughput during peak times but anticipate that traffic will vary significantly throughout the day. The company wants to minimize costs while ensuring the database automatically scales to handle these workload variations. What is the most cost-optimized database solution for their needs?
- A
Use Amazon RDS with a Multi-AZ deployment and provisioned IOPS storage.
- B
Use Amazon DynamoDB with on-demand capacity mode.
- C
Use Amazon Aurora Serverless v2 with auto-scaling configured.
- D
Use Amazon ElastiCache for Redis with fixed-node clusters.
Show answer and explanation
Correct answer: B
Explanation
Amazon DynamoDB with on-demand capacity mode is ideal for applications with unpredictable or highly variable workloads. It automatically scales to meet demand and charges only for the read and write capacity actually consumed, making it the most cost-optimized solution for the given scenario.
- A. Incorrect.
Amazon RDS with a Multi-AZ deployment and provisioned IOPS storage is better suited for predictable workloads that require high availability and consistent performance. However, it is not as cost-optimized for variable workloads due to the fixed resources and high storage costs.
- B. Correct.
Amazon DynamoDB with on-demand capacity mode is the best choice for variable workloads because it automatically scales up or down based on traffic and eliminates the need for capacity planning. This ensures cost efficiency during periods of low traffic.
- C. Incorrect.
Amazon Aurora Serverless v2 is a good option for variable workloads, but it is typically more expensive than DynamoDB for high-throughput applications and may introduce latency for scaling operations.
- D. Incorrect.
Amazon ElastiCache for Redis is designed for low-latency caching rather than as a primary database. While it is cost-effective for caching, it is not a suitable choice for handling variable throughput in a primary database scenario.