DEA-C01 · Question #305
A company regularly loads data into an Amazon DynamoDB table. The company must retain the data in DynamoDB for 1 year. After 1 year, the company must archive the data for 5 years. After 5 years, the…
The correct answer is D. Enable Amazon DynamoDB Streams. Configure a TTL rule to delete items from the DynamoDB. DynamoDB TTL provides a fully managed way to remove items after 1 year with minimal operational work. DynamoDB Streams can capture the item changes so a Lambda function can archive the expiring data to Amazon S3 before it is removed from the table. Using S3 Glacier Deep Archive…
Question
A company regularly loads data into an Amazon DynamoDB table. The company must retain the data in DynamoDB for 1 year. After 1 year, the company must archive the data for 5 years. After 5 years, the company must delete the data. Which solution will meet these requirements in the MOST operationally efficient way?
Options
- AInclude a timestamp with the data that is loaded into DynamoDB. Create an AWS Lambda
- BEnable Amazon DynamoDB Streams. Configure a TTL rule to delete items from the DynamoDB
- CInclude a timestamp with the data that is loaded into DynamoDB. Use an AWS Lambda function
- DEnable Amazon DynamoDB Streams. Configure a TTL rule to delete items from the DynamoDB
How the community answered
(41 responses)- A7% (3)
- B2% (1)
- C15% (6)
- D76% (31)
Explanation
DynamoDB TTL provides a fully managed way to remove items after 1 year with minimal operational work. DynamoDB Streams can capture the item changes so a Lambda function can archive the expiring data to Amazon S3 before it is removed from the table. Using S3 Glacier Deep Archive minimizes archive storage cost for long retention, and an S3 Lifecycle policy can automatically delete the archived objects after 5 years, avoiding custom deletion logic.
Topics
Community Discussion
No community discussion yet for this question.