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.
Option C seems right to me. Enabling TTL and letting Lambda just set the expiration attribute keeps things simple, AWS deletes the data automatically after one month. Not 100% sure if there's a weird edge case about delayed deletion, but this should be lowest overhead. Someone let me know if I'm missing anything.
Had something like this in a mock and pretty sure C is the way to go. Using DynamoDB TTL with a Lambda function just to set the expiration date keeps things mostly serverless, and AWS handles the deletion afterward. No need for custom stream handling or extra services. Only possible caveat is TTL isn't instant, but "within one month" seems fine for most use cases. Anyone see a risk with this approach?
Its C since enabling TTL in DynamoDB plus a Lambda to set the expiration is low effort and AWS manages most of the process. Official AWS docs and practice exams mention TTL for these scenarios. Pretty sure this fits, anyone disagree?
C or B? TTL isn't perfectly precise, so if exact month cutoff is mandatory, maybe B fits better.
Be respectful. No spam.
