A developer supports an application that accesses data in an Amazon DynamoDB table. One of the item attributes is expirationDate in the timestamp format. The application uses this attribute to find…

Question

Options

• AEnable TTL on the expirationDate attribute in the table. Create a DynamoDB stream. Create an
• BCreate two AWS Lambda functions: one to delete the items and one to process the items. Create
• CCreate two AWS Lambda functions: one to delete the items and one to process the items. Create
• DEnable TTL on the expirationDate attribute in the table. Specify an Amazon Simple Queue

• A
  81% (17)
• B
  10% (2)
• C
  5% (1)
• D
  5% (1)

Explanation

Option A is correct because enabling DynamoDB TTL on the expirationDate attribute handles item deletion automatically with zero code - DynamoDB compares the timestamp to the current time and deletes expired items natively. Pairing this with a DynamoDB Stream allows a single Lambda function to capture the TTL-deletion events and archive the items, fulfilling all requirements with minimal code.

Options B and C are wrong because they require two Lambda functions - one to handle deletion and one to process/archive - meaning the developer must write custom deletion logic that TTL already provides for free. Options B and C essentially replicate work DynamoDB can do natively.

Option D is wrong because routing through SQS adds an unnecessary layer: you'd need code to populate the queue and consume it, which is more code than a direct Stream-to-Lambda pipeline.

Memory tip: Think of TTL as DynamoDB's built-in "self-destruct timer" - whenever you see expiration + least code, TTL is almost always the answer. DynamoDB Streams are the natural companion when you need to react to those deletions (e.g., archive before they disappear).

No community discussion yet for this question.