A delivery company is running a serverless solution in the AWS Cloud. The solution manages user data, delivery information, and past purchase details. The solution consists of several microservices. The central user service stores sensitive data in an Amazon DynamoDB table. Several of the other microservices store a copy of parts of the sensitive data in different storage services. The company needs the ability to delete user information upon request. As soon as the central user service deletes a user, every other microservice must also delete its copy of the data immediately. Which solution will meet these requirements?
Select one answer.
Marked answer: C
Community Discussion
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Chose A1
Originally, I chose B but later I realized that DynamoDB stream IS DynamoDB event noti mechanism and A is the go-to solution when working with DynamoDB events
Chose B1
" Create an EventBridge rule for each microservice to match the user deletion event pattern and invoke logic in the microservice to delete the user from the DynamoDB table." -> but we need to delete user data not delete user from DynamoDB.
Chose C1
For immediate, multi-subscriber deletion across microservices, use EventBridge. Post a user.deleted event to a custom bus and create one rule per microservice to trigger its own delete logic. SQS is competing-consumer (not fan-out), and DynamoDB doesn’t have direct “event notifications to SNS.” EventBridge gives clean, serverless fan-out with filtering.
