Exam AWS Certified DevOps Engineer - Professional DOP-C02 topic 1 question 139 discussion

The two solutions that will meet the requirement of preventing the loss of notification messages in the future are: D. Subscribe an Amazon Simple Queue Service (Amazon SQS) queue to the SNS topic. Configure the Lambda function to process messages from the SQS queue. This solution will ensure that notification messages are delivered to the SQS queue even if the Lambda function is unavailable or the RDS DB instance is down. The Lambda function can then process the messages from the SQS queue at its own pace. C. Configure an Amazon Simple Queue Service (Amazon SQS) dead-letter queue for the SNS topic. This solution will ensure that notification messages that cannot be delivered to the RDS DB instance are not lost. Instead, they will be moved to a dead-letter queue. The DevOps engineer can then manually process the messages from the dead-letter queue.

C:D , D is a best practice for this scenario, C because you can send failed SNS o SQS Dead letter queue, https://docs.aws.amazon.com/sns/latest/dg/sns-dead-letter-queues.html

Correct answer https://www.youtube.com/watch?v=rYFAdRCibyc

BD C. Dead-letter queues can only be added to SNS subscriptions, not to topics.

AD. C is wrong, "Configuring an Amazon SNS dead-letter queue for a subscription" not for SNS topic A is correct, with Dynamodb, admin can no longer "accidentally shut down the DB instance." A fixes the root cause. With D an SQS is there, no need for DLQ for SNS. If lambda process data from SQS, what is SNS DLQ help here?

C and D are correct: <. While the database was down the company lost several of the SNS notification messages that were delivered during that time> means dead-letter queue in SQS and output SNS to SQS to store dead-letter queue

B & D are correct