A complicated data analysis software in JAVA has used a standard SQS queue to decouple users` requests and the backend processing. The visibility timeout for the queue is set as 60 seconds. In most cases, the process of messages can finish within 1 minute successfully. However, it may take about 100 seconds for the backend to get the job done for certain new requests. These requests are tagged with a specific JSON header by the frontend already. You want to ensure that these new requests are processed properly in the backend. How should you improve the queue configurations in the best way?

Answer options:

A.In the AWS SQS console, simply change the default visibility timeout from 1 minute to 2 minutes.
B.Use AWS SDK to adjust the visibility timeout to 2 minutes for messages that contain the specific JSON header.
C.Change the queue type from standard to FIFO with the default visibility timeout configured as 2 minutes.
D.Create a new SQS queue as the dead letter queue. Route these specific requests to the dead letter queue so that the normal backend process is not influenced.

Correct Answer – B
For the new requests, the default visibility timeout of 60 seconds for the queue would be insufficient. The messages’ visibility should be extended by specifying a new timeout value using the ChangeMessageVisibility action through the AWS SDK.
Option A is incorrect: Because this change in the AWS console is a global change for all messages in the queue. However, in this case, only specific messages need to extend the timer.
Option B is correct: Refer to https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-configure-visibility-timeout-queue.html on how to configure Visibility Timeout for an Amazon SQS queue. Using the method, those messages with particular JSON headers can get a revised timer.
Option C is incorrect: Because the FIFO queue type does not help with the visibility timeout issue for the new messages.
Option D is incorrect: Although the dead letter queue can help isolate the new messages, it cannot fix the problem on the visibility timeout issue. Besides, the timer needs to be enlarged only for these new messages.