What must the company do to migrate to an SQS FIFO queue?
Create a new SQS FIFO queue. Turn on content-based deduplication on the new FIFO queue. Update the application to include a message group ID in the messages.
Create a new SQS FIFO queue. Update the application to include the DelaySeconds parameter in the messages.
Modify the queue type from SQS standard to SQS FIFO. Turn off content-based deduplication on the queue. Update the application to include a message group ID in the messages.
Modify the queue type from SQS standard to SQS FIFO. Update the application to send messages with identical message bodies and to include the DelaySeconds parameter in the messages.
Explanations:
To migrate to an SQS FIFO queue, the company must create a new FIFO queue, enable content-based deduplication, and update the application to include a message group ID, which is required for FIFO queues.
The DelaySeconds parameter is not a requirement when migrating to a FIFO queue. The correct action is to include a message group ID and enable content-based deduplication.
It is not possible to modify an existing SQS standard queue to a FIFO queue. A new FIFO queue must be created. The message group ID is required, but content-based deduplication should be enabled, not turned off.
Modifying the queue type from standard to FIFO is not possible. Additionally, the DelaySeconds parameter is unnecessary for FIFO migration. The correct solution involves content-based deduplication and a message group ID.
I assess that the answer is:
Create a new SQS FIFO queue. Turn on content-based deduplication on the new FIFO queue. Update the application to include a message group ID in the messages.