Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
AWS Certified Solutions Architect - Associate · AWS
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
To prevent duplicate processing of SQS messages, ensure that the visibility timeout is long enough to cover entire processing duration. Use the ChangeMessageVisibility API to adjust it dynamically if needed.
I chose D as well, I understand the rationale behind it.But I think it is named incorrectly. should this not be "InvisibilityTimeout" instead of "VisibilityTimeout"? If the message becomes visible again after a timeout, because SQS assumes it failed processing - then it remains invisible and after timeout it becomes visible again... So thats wheremy point of contention is.
Explicação: Causa provável do problema: O problema ocorre porque o tempo de visibilidade (visibility timeout) configurado na fila do Amazon SQS é muito curto. Quando uma instância EC2 lê uma mensagem da fila e começa a processá-la, se o processamento não for concluído antes que o tempo de visibilidade expire, a mensagem volta para a fila e pode ser processada novamente por outra instância. Isso leva a registros duplicados na tabela RDS.