Q: 7
A company is creating a mobile financial app that gives users the ability to sign up and store personal
information. The app uses an Amazon DynamoDB table to store user details and preferences.
The app generates a credit score report by using the data that is stored in DynamoDB. The app sends
credit score reports to users once every month.
The company needs to provide users with an option to remove their data and preferences. The app
must delete customer data within one month of receiving a request to delete the data.
Which solution will meet these requirements with the LEAST operational overhead?
Options
Discussion
Option C TTL on DynamoDB fits best for auto deletion, keeps it simple and low maintenance.
C . EventBridge and Config look tempting but just add extra steps for no reason here.
C/B? TTL's delayed deletion can miss strict deadlines so if "within one month" must be exact B could fit.
C here. TTL is the built-in way to handle this with almost zero ops overhead. B is a trap, adds unnecessary complexity by using streams and manual deletes. Pretty sure C matches the AWS best practice. Anyone see a reason not to use TTL?
C imo. TTL in DynamoDB is built for scheduled deletion like this, and using Lambda just to set the TTL keeps things fully managed with minimal overhead. B looks tempting, but adding streams and extra functions means more moving parts than needed. If you need to guarantee strict timing or complex workflows, maybe B, but here C fits best. Disagree?
That might break if DynamoDB TTL doesn't trigger exactly on the 30-day mark, so B.
Why can't D just use DynamoDB TTL directly instead of adding AWS Config in the mix?
Maybe D here. AWS Config could help catch the TTL expiry and then run Lambda, so feels like less manual setup than some other approaches. Not 100% on the operational overhead part though, happy to hear if I'm off.
This comes up a lot, and C is the best fit. Just enabling TTL and using a Lambda to set the expiration attribute lets DynamoDB handle deletion automatically, no extra moving parts. Pretty sure nothing else is as low effort. Disagree?
Not sure about C, I'd pick D since AWS Config can watch for TTL and trigger Lambda. Option D.
Be respectful. No spam.
