Q66 — AWS SAA-C03 Ch.13

Question 66 of 100 | ← Chapter 13

Q966. A solutions architect is creating an event-driven architecture for a new application. The solutions architect creates an Amazon Simple Notification Service (Amazon SNS) topic and subscribes an AWS Lambda function to the SNS topic.The solutions architect uses Amazon CloudWatch to validate that the system functions as expected.The solutions architect publishes a message to the SNS topic to test the functionality. The solutions architect views the output in Amazon CloudWatch and notices that the Lambda function is invoked multiple times.What is the is the most likely reason the Lambda function was invoked multiple times?

Correct Answer: C. The SNS redrive policy is configured to deliver the message multiple times.

Explanation

The correct answer is C. The SNS redrive policy is configured to deliver the message multiple times.Here's why:A. The Lambda function is subscribed to the SNS topic multiple times:This is not the most likely reason, as the solutions architect would typically notice if the Lambda function was subscribed multiple times to the same SNS topic.B. The SNS delivery policy is configured to deliver the message multiple times:The SNS delivery policy determines how SNS attempts to deliver messages to its subscribers. It does not cause the message to be delivered multiple times unless there is a specific configuration to do so.C. The SNS redrive policy is configured to deliver the message multiple times:The SNS redrive policy is the most likely reason for the Lambda function being invoked multiple times. The redrive policy determines what happens when a message delivery fails. If the redrive policy is configured to move failed messages to a dead-letter queue and then redeliver them, it could result in the Lambda function being invoked multiple times for the same message.D. The Lambda function's application logic caused an error that results in retry attempts by the Lambda function:This is not the most likely reason, as the issue is likely with the SNS service configuration rather than the Lambda function itself.In summary, the most likely reason the Lambda function was invoked multiple times is that the SNS redrive policy was configured to redeliver failed messages, leading to multiple invocations of the subscribed Lambda function.