How does DynamoDB TTL prevent throttling during data cleanup?

DVA-C02 By islever Editorial Last updated

Short answer

A Configure a TTL attribute for the leaderboard data.

Question

A company built an online event platform. For each event, the company organizes quizzes and generates leaderboards that are based on the quiz scores. The company stores the leaderboard data in Amazon DynamoDB and retains the data for 30 days after an event is complete. The company then uses a scheduled job to delete the old leaderboard data. The DynamoDB table is configured with a fixed write capacity. During the months when many events occur, the DynamoDB write API requests are throttled when the scheduled delete job runs. A developer must create a long-term solution that deletes the old leaderboard data and optimizes write throughput. Which solution meets these requirements?
  1. Configure a TTL attribute for the leaderboard data. Correct Answer
  2. Use DynamoDB Streams to schedule and delete the leaderboard data.
  3. Use AWS Step Functions to schedule and delete the leaderboard data.
  4. Set a higher write capacity when the scheduled delete job runs.

Key Takeaways

This question tests knowledge of DynamoDB’s native expiration mechanism versus manual deletion workflows, highlighting the common trap of triggering write capacity throttling through scheduled batch deletes.

DynamoDB Time-To-Live (TTL) automatically expires and deletes items without consuming provisioned write capacity units. Exam candidates and the community universally recognize TTL as the most efficient, serverless approach for managing time-bound datasets like event leaderboards.

Common mistake: Option D is frequently selected by test-takers attempting to scale resources during peak periods, but it ignores the architectural benefit of offloading deletions and unnecessarily inflates operational costs.

Expert Analysis

Why the Answer Is Correct

Configuring a TTL attribute allows DynamoDB to asynchronously expire and delete items after the specified timestamp passes. These background deletions do not consume your table’s Write Capacity Units (WCU), completely eliminating the throttling issue caused by the scheduled cleanup job. This provides a fully managed, cost-effective, and scalable long-term solution that aligns perfectly with the requirement to optimize write throughput.

Why the Other Options Are Wrong

DynamoDB Streams (Option B) capture data modification events but cannot independently schedule or trigger periodic deletions. AWS Step Functions (Option C) can orchestrate workflows, but executing bulk delete operations would still consume WCU and potentially cause the same throttling problem. Increasing write capacity temporarily (Option D) addresses the symptom rather than the root cause, leading to unnecessary costs and failing to meet the optimization requirement.

Community Comment Notes

The voting distribution shows 100% agreement on Option A, reflecting strong community confidence. Multiple contributors explicitly note that “A | Always consider TTL when trying to ditch from DynamoDB,” reinforcing its status as a go-to pattern for data expiration. Additional comments simply confirm TTL as the correct mechanism, demonstrating that this is a well-established best practice among AWS developers.

Official Reference

https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/TTL.html

This link opens the official vendor documentation in a new tab.

Exam Strategy

For any DynamoDB scenario involving automatic expiration, archival, or cleanup of time-sensitive data, prioritize TTL over custom Lambda jobs or cron-based scripts. Reserve manual deletion or capacity scaling only for non-expiring data or emergency overrides.

Community Votes

A
100%

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

Discussion 5 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 5

  1. tgv 👍 7 Answered A
    Always consider TTL when trying to ditch from DynamoDB.
  2. 65703c1 👍 2 Answered A
    A is the correct answer.
  3. KarBiswa 👍 2 Answered A
    It should be TTL enabled
  4. vkovilam 👍 2 Answered A
    Time To Live
  5. CrescentShared 👍 2 Answered A
    A is right

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.

Submitted for moderation before publishing. Keep it helpful and respectful.

How to Log Every Lambda Invocation to an SQS Queue?

S-grade

How to Test Updated Lambda Functions with a Subset of Users Using API Gateway?

S-grade

How to automate S3 object tagging after delayed third-party content audit?

S-grade

How to automatically rotate encryption keys for API keys in serverless apps with no development effort?

S-grade

Practice All DVA-C02 Questions

Access 100 questions with complete answers and detailed explanations.

View Full DVA-C02 Practice Test →

← Back to DVA-C02 Study Guide