You are working on a decoupled application that uses Amazon SQS for storing messages before being processed by another application deployed on the Amazon EC2 instance. You are observing a surge in the number of messages being processed by this application, most of which are duplicate messages. What change needs to be done if your application takes approximately 45 secs to process each message?

Answer options:

A.Configure Amazon SQS Visibility timeout to 43200 seconds.
B.Configure Amazon SQS Visibility timeout to 0 seconds.
C.Configure Amazon SQS Visibility timeout to 60 seconds.
D.Configure Amazon SQS Visibility timeout to default to 30 seconds.

Correct Answer – C
Visibility Timeout is a period during which Amazon SQS prevents other consumers from receiving and processing the message. In the above requirement, the application takes 45 secs to process each message. So Visibility Timeout should be greater than 45 seconds. Hence, setting visibility timeout as 60 seconds is the correct option.
Option A is incorrect. Even though setting Amazon SQS Visibility timeout to 43200 seconds will work, it will add delay as it must wait for 12 hours if initial message processing fails.
Option B is incorrect since message processing takes 45 secs. Setting a visibility timeout of 0 seconds will increase duplicate messages as other consumers will start processing the same message when the first consumer is processing it.
Option D is incorrect since message processing takes 45 secs. Setting a visibility timeout of 30 seconds will increase duplicate messages as other consumers will start processing the same message when the first consumer is processing it.
For more information on visibility timeout on Amazon SQS, refer to the following URL-
https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/working-with-messages.html#processing-messages-timely-manner