Q: 2
An application that runs on AWS receives messages from an Amazon Simple Queue Service (Amazon
SQS) queue and processes the messages in batches. The
application sends the data to another SQS queue to be consumed by another legacy application. The
legacy system can take up to 5 minutes to process some transaction dat
a.
A developer wants to ensure that there are no out-of-order updates in the legacy system. The
developer cannot alter the behavior of the legacy system.
Which solution will meet these requirements?
Options
Discussion
Option A is the way to go. Setting the API Gateway integration type to MOCK lets the API return test responses without any backend, so frontend teams can keep developing. Pretty sure this is exactly what AWS recommends for this use-case. Anyone see a better method?
Seen almost this exact setup in a practice exam, so I'd go with D. You get FIFO for order and DelaySeconds to hold back processing just long enough. Not 100% if DelaySeconds alone solves all timing issues but sounds close for what the question asks. Agree or not?
Probably A . FIFO with visibility timeout is the combo that handles ordering and avoids duplicate processing for slow consumers.
Makes sense to me, A.
A , FIFO queue plus visibility timeout is what keeps the order and prevents double processing.
This kind of AWS question always trips people up, but the exam wants you to catch the visibility timeout thing. A
Why not just use a standard queue if batching is needed? FIFO feels required only for strict ordering.
Pretty sure A is what AWS expects here. FIFO keeps message order and the visibility timeout stops other consumers from grabbing the same job before the legacy app finishes. Saw similar in exam reports, but open to pushback.
Nah, I think A is right here. Standard queues (B or C) can’t guarantee order at all, and DelaySeconds in D doesn’t stop early reprocessing-visibility timeout does. Saw similar on practice, pretty sure A is less of a trap. Disagree?
A is wrong, D. FIFO with DelaySeconds should keep the order and lets you manage delivery time. I saw a similar question in some practice tests, pretty sure D fits unless I'm missing something about visibility timeout. Official guide covers this.
Be respectful. No spam.
