Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam SAP-C02 Topic 11 Question 39 Discussion

Actual exam question for Amazon's SAP-C02 exam
Question #: 39
Topic #: 11
[All SAP-C02 Questions]

A delivery company is running a serverless solution in tneAWS 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?

Show Suggested Answer Hide Answer
Suggested Answer: C

Set Up EventBridge Event Bus:

Step 1: Open the Amazon EventBridge console and create a custom event bus. This bus will be used to handle user deletion events.

Step 2: Name the event bus appropriately (e.g., user-deletion-bus).

Post Events on User Deletion:

Step 1: Modify the central user service to post an event to the custom EventBridge event bus whenever a user is deleted.

Step 2: Ensure the event includes relevant details such as the user ID and any other necessary metadata.

Create EventBridge Rules for Microservices:

Step 1: For each microservice that needs to delete user data, create a new rule in EventBridge that triggers on the user deletion event.

Step 2: Define the event pattern to match the user deletion event. This pattern should include the event details posted by the central user service.

Invoke Microservice Logic:

Step 1: Configure the EventBridge rule to invoke a target, such as an AWS Lambda function, which contains the logic to delete the user data from the microservice's data store.

Step 2: Each microservice should have its Lambda function or equivalent logic to handle the deletion of user data upon receiving the event.

Using Amazon EventBridge ensures a scalable, reliable, and decoupled approach to handle the deletion of user data across multiple microservices. This setup allows each microservice to independently process user deletion events without direct dependencies on other services.

Reference

AWS EventBridge Documentation

DynamoDB Streams and AWS Lambda Triggers

Implementing the Transactional Outbox Pattern with EventBridge Pipes (AWS Documentation) (Amazon Web Services, Inc.) (Amazon Web Services, Inc.) (AWS Documentation) (AWS Cloud Community).


Contribute your Thoughts:

Abel
2 months ago
I'm with Amber on this one - the DynamoDB Streams approach (A) seems the most bulletproof for this use case.
upvoted 0 times
...
Eleonore
2 months ago
Haha, option D with the SQS queue? Sounds like a recipe for some epic race conditions and eventual consistency issues!
upvoted 0 times
...
Isabella
2 months ago
I'd go with option B and use DynamoDB event notifications and Amazon SNS. Seems simpler than the Lambda function in option A.
upvoted 0 times
Leoma
26 days ago
Definitely, it ensures that all copies of the sensitive data are deleted immediately when a user request is made.
upvoted 0 times
...
Arleen
1 months ago
Yeah, having each microservice subscribe to the SNS topic for user deletion events makes sense.
upvoted 0 times
...
Dyan
2 months ago
I agree, it does seem simpler than setting up a Lambda trigger like in option A.
upvoted 0 times
...
Ariel
2 months ago
Yeah, option B definitely seems like the most efficient solution for deleting user information across all microservices.
upvoted 0 times
...
Fidelia
2 months ago
Option B sounds like a good choice. Using DynamoDB event notifications and Amazon SNS seems efficient.
upvoted 0 times
...
Mozell
2 months ago
I agree, option B seems straightforward and effective for ensuring all microservices delete user data immediately.
upvoted 0 times
...
Glen
2 months ago
Option B sounds like the best choice. Using DynamoDB event notifications and Amazon SNS seems efficient.
upvoted 0 times
...
...
Tasia
3 months ago
I see your point, Nan. Option C does seem like a more efficient solution for deleting user data across all microservices.
upvoted 0 times
...
Ezekiel
3 months ago
Option C with EventBridge looks interesting, but I'm not sure if it provides the same level of guarantee as the DynamoDB Streams approach.
upvoted 0 times
Rhea
2 months ago
Let's go with Option A then, to make sure all microservices delete user data immediately.
upvoted 0 times
...
Carman
2 months ago
I agree, Option A seems like a safer bet for ensuring immediate data deletion.
upvoted 0 times
...
Aleshia
2 months ago
I think Option A with DynamoDB Streams might provide a more reliable solution.
upvoted 0 times
...
Carlee
2 months ago
Option C with EventBridge is a good choice for this scenario.
upvoted 0 times
...
...
Nan
3 months ago
I disagree, I believe option C is better as it uses Amazon EventBridge to invoke logic in each microservice.
upvoted 0 times
...
Johnna
3 months ago
I think option A could work because it uses DynamoDB Streams to trigger events for user deletion.
upvoted 0 times
...
Amber
3 months ago
The DynamoDB Streams and Lambda solution (A) seems like the most robust and reliable way to ensure immediate data deletion across all microservices.
upvoted 0 times
Selene
3 months ago
Yes, option A provides a seamless way to ensure all microservices delete user data simultaneously.
upvoted 0 times
...
Natalie
3 months ago
I agree, option A with DynamoDB Streams and Lambda seems like the best choice for immediate data deletion.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77