Company ABC has an AWS setup and planning to use Amazon SQS for queuing messages. The design is such that two applications will receive the same message in the queue and process it. Once applications would have read the message, it should be deleted. However, when the 2nd application makes the ReceiveMessage API call, the message is not getting returned. Which of the following could be reasons? (Choose 2 options)

Answer options:

A.Application 2 is making a call before Visibility Timeout elapsed which was set by application 1 ReceiveMessage call.
B.Amazon SQS deletes the message once it has been responded via the ReceiveMessage call from Application 1.
C.Application 1 had deleted the message after it had been processed before Visibility Timeout elapsed.
D.Application 2 does not have access to the message it is trying to receive.

Answer: A, C
Option A is correct.
Immediately after a message is received, it remains in the queue. To prevent other consumers from processing the message again, Amazon SQS sets a visibility timeout, a period of time during which Amazon SQS prevents other consumers from receiving and processing the message. The default visibility timeout for a message in 30 seconds. The minimum is 0 seconds. The maximum is 12 hours.
https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-visibility-timeout.html
Option B is not correct.
https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-visibility-timeout.html
Option C is correct.
Once the message is deleted from Amazon SQS Queue, it will not be available anymore.
Option D is not correct.
Permission exists on the Queue level, not on the message level.
For more information on SQS actions, refer to documentation here.
https://docs.aws.amazon.com/IAM/latest/UserGuide/list_amazonsqs.html