
Ultimate access to all questions.
A space exploration company collects telemetry data from various satellites. This data, in the form of small packets, is received via Amazon API Gateway and immediately queued in an Amazon Simple Queue Service (SQS) standard queue. A specialized application monitors this queue and is responsible for converting the incoming data into a standardized format. However, due to the inherent inconsistencies in the satellite data, the application sometimes fails to process certain messages, causing them to remain in the SQS queue. The DevOps engineer is tasked with creating a solution that not only preserves these unprocessed messages but also ensures they are accessible for review and potential reprocessing by the scientific team. What should be the approach to address this issue?
A
Set up AWS Lambda to periodically check the SQS queue for valid messages. For those that fail validation, copy the data to an Amazon S3 bucket for review by the scientists. Implement a Lambda function to update the SQS queue with corrected data once it has been reviewed and amended by the scientists.
B
Change the SQS standard queue to an SQS FIFO queue. Use AWS Lambda to poll the queue every 10 minutes via an Amazon EventBridge schedule. Identify and move messages older than 5 minutes based on their SentTimestamp to the application's designated output location, then remove them from the queue.
C
Establish an SQS dead-letter queue and adjust the main queue with a redrive policy that sets Maximum Receives to 1 and targets the new dead-letter queue's ARN. Guide the scientists to utilize the dead-letter queue for reviewing and later reprocessing the untransformed data.
D
Modify API Gateway to direct messages to distinct SQS virtual queues, each named after a satellite. Update the application to route unprocessable data to a new virtual queue, and instruct the scientists to access this queue for reviewing and reprocessing the data.