DynamoDB Scheduled Auto Scaling for Predictable Workloads

DEA-C01 By islever Editorial Last updated

Automate data processing by using AWS services.

Short answer

C Use AWS Application Auto Scaling to schedule higher provisioned capacity for peak usage times and lower capacity during off-peak times.

Question

A company stores data from an application in an Amazon DynamoDB table that operates in provisioned capacity mode. The workloads of the application have predictable throughput load on a regular schedule. Every Monday, there is an immediate increase in activity early in the morning. The application has very low usage during weekends. The company must ensure that the application performs consistently during peak usage times. Which solution will meet these requirements in the MOST cost-effective way?
  1. Increase the provisioned capacity to the maximum capacity that is currently present during peak load times.
  2. Divide the table into two tables. Provision each table with half of the provisioned capacity of the original table. Spread queries evenly across both tables.
  3. Use AWS Application Auto Scaling to schedule higher provisioned capacity for peak usage times. Schedule lower capacity during off-peak times. Correct Answer
  4. Change the capacity mode from provisioned to on-demand. Configure the table to scale up and scale down based on the load on the table.

Key Takeaways

The exam tests the distinction between reactive auto scaling and proactive scheduled scaling, highlighting that scheduled policies are optimal for known, recurring peaks like Monday mornings.

This question evaluates the cost-effective management of Amazon DynamoDB provisioned capacity using AWS Application Auto Scaling with scheduled policies to match predictable traffic patterns.

Common mistake: Many learners choose On-Demand mode (D) because it handles variable load automatically, but this is incorrect for predictable workloads where provisioned capacity is significantly cheaper.

Expert Analysis

Why the Answer Is Correct

AWS Application Auto Scaling allows you to configure target tracking or simple scaling policies based on schedules. Since the workload has a predictable pattern (Monday morning peak, low weekend usage), scheduling higher provisioned capacity during specific times ensures performance while avoiding the high costs of maintaining maximum capacity all week. This aligns perfectly with the requirement for the "MOST cost-effective way".

Why the Other Options Are Wrong

Option A is inefficient because paying for peak capacity 24/7 results in significant waste during low-usage periods. Option B adds operational complexity without guaranteeing cost savings and may lead to uneven load distribution issues. Option D (On-Demand) is designed for unpredictable traffic; for predictable workloads, the per-request cost of On-Demand is generally higher than scaled-down provisioned capacity.

Community Comment Notes

Community consensus strongly favors C. User rralucard_ noted that option C "allows the company to align their DynamoDB capacity costs with actual usage patterns." User Christina666 correctly pointed out that "On-demand mode is great for unpredictable workloads" and would likely cost more here. User sdas1 referenced documentation stating "provisioned capacity is probably best for you if you have relatively predictable application traffic," reinforcing the choice of C over D.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

Always look for keywords like 'predictable' and 'cost-effective' when choosing between Provisioned and On-Demand modes. If the pattern is regular (e.g., daily, weekly), Scheduled Auto Scaling is usually the intended answer.

Frequently Asked Questions

Why not use On-Demand mode for this scenario?

On-Demand is more expensive for predictable workloads. You pay a premium for flexibility that you don't need when traffic follows a known schedule.

Does Scheduled Auto Scaling require manual intervention?

No. Once configured, AWS Application Auto Scaling automatically adjusts the provisioned capacity up and down according to the defined schedule.

More DEA-C01 FAQ →

Community Votes

C
100%

100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 9 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 9

  1. rralucard_ 👍 5 Answered C
    Option C, using AWS Application Auto Scaling to schedule higher provisioned capacity for peak usage times and lower capacity during off-peak times, is the most cost-effective solution for the described scenario. It allows the company to align their DynamoDB capacity costs with actual usage patterns, scaling up only when needed and scaling down during low-usage periods.
  2. pypelyncar 👍 4 Answered C
    app autoscalling allows you to dynamically adjust provisioned capacity based on usage patterns. You only pay for the capacity you utilize, reducing costs compared to keeping a high, fixed capacity throughout the week
  3. Christina666 👍 3 Answered C
    D. Change the capacity mode from provisioned to on-demand... On-demand mode is great for unpredictable workloads. In your case, with predictable patterns, you'd likely pay more with on-demand than with a well-managed, scheduled, provisioned mode.
  4. FuriouZ 👍 3 Answered C
    Obviously better than B because of peak scaling
  5. damaldon 👍 2
    C. https://docs.aws.amazon.com/autoscaling/application/userguide/services-that-can-integrate-dynamodb.html
Show 4 more comments
  1. jpmadan 👍 1 Answered B
    D Excerpts from documentation: This means that provisioned capacity is probably best for you if you have relatively predictable application traffic, run applications whose traffic is consistent, and ramps up or down gradually. Whereas on-demand capacity mode is probably best when you have new tables with unknown workloads, unpredictable application traffic and also if you only want to pay exactly for what you use. The on-demand pricing model is ideal for bursty, new, or unpredictable workloads whose traffic can spike in seconds or minutes, and when under-provisioned capacity would impact the user experience. https://docs.aws.amazon.com/wellarchitected/latest/serverless-applications-lens/capacity.html
  2. sdas1 👍 1
    C https://docs.aws.amazon.com/wellarchitected/latest/serverless-applications-lens/capacity.html DynamoDB auto scaling modifies provisioned throughput settings only when the actual workload stays elevated or depressed for a sustained period of several minutes. This means that provisioned capacity is probably best for you if you have relatively predictable application traffic, run applications whose traffic is consistent, and ramps up or down gradually.
  3. Rakiko 👍 1 Answered C
    My guess is C as it stands for Cat
  4. lucas_rfsb 👍 1 Answered D
    As I understand, should be D

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Amazon Redshift Compound Sort Key Query Optimization

S-grade

Secure Redshift Spectrum Access with VPC Endpoints

S-grade

Athena Federated Query for Multi-Source Iceberg Pipelines

S-grade

Reclaiming Storage in Amazon Redshift Materialized Views

S-grade

Practice All DEA-C01 Questions

Access 100 questions with complete answers and detailed explanations.

View Full DEA-C01 Practice Test →

← Back to DEA-C01 Study Guide