Exam AWS Certified Solutions Architect - Professional topic 1 question 458 discussion

Correct answer is C.

Correct answer is A. With FIFO you avoid the problem of duplicate processing in the queue.

FIFO supports higher limits now https://aws.amazon.com/about-aws/whats-new/2023/08/amazon-sqs-increased-throughput-quota-fifo-high-throughput-mode/

several thousand per second so C

C: FIFO queues help you avoid sending duplicates to a queue. If you retry the SendMessage action within the 5-minute deduplication interval, Amazon SQS doesn't introduce any duplicates into the queue.

there is a difference between FIFO and a standard queue of SQS -- https://jayendrapatil.com/aws-sqs-standard-vs-fifo-queue/ so the answer should be "A"

Could be A, but we do not know how long the total process could take (maybe more than 15 min) and the SQS FiFo is not for this use case, the keyword here is "Idempotency" which means you have to build your application making sure you do not process the same message twice. so the correct option is C

A is the correct answer - FIFO Queues High Throughput: By default, FIFO queues support up to 300 messages per second (300 send, receive, or delete operations per second). When you batch 10 messages per operation (maximum), FIFO queues can support up to 3,000 messages per second. If you require higher throughput, you can enable high throughput mode for FIFO on the Amazon SQS console, which will support up to 30,000 messages per second with batching, or up to 3,000 messages per second without batching. Exactly-Once Processing: A message is delivered once and remains available until a consumer processes and deletes it. Duplicates aren't introduced into the queue. First-In-First-Out Delivery: The order in which messages are sent and received is strictly preserved (i.e. First-In-First-Out).

Based on all comments

How about This? https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queues-exactly-once-processing.html

Keyword: Process twice SQS prevents duplicate processes Answer: C

Answer is C. Key concepts: 1. Hight availability 2. Thousands of requests/s 3. Duplication in processes EC2 ASG & SQS solve all of that.

Correct answer is C C addresses the issues highlighted in the question. One of queueing message going down, and losing orders, and the last one is duplicate processor certain orders. Amazon SQS address the issue of messaging Implement idempotency in the application resolves the issue of processing duplicate order - aka At-least-once delivery (Design your applications to be idempotent (they should not be affected adversely when processing the same message more than once). https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/standard-queues.html#standard-queues-at-least-once-delivery

Why D: Can hadle more than 300 messages w/o loosing them. Will treat idempotency problem. It’s AWS sudgested topology. Why NOT A: “Put the ordering and inventory applications into their own AWS Lambda” … Lambda doesn’t support hosting application, API Gateway is required for that and it’s not mentioned. A is wrong. --SQS FIFO queues can only support 300 send, receive, or delete operations per second. and the question satats many thousand orders /second Why NOT C: no one mentioned about "idempotency" term from C - this one requires a control database to check the value for duplicates. I do not see this in C.

All answering C , focused on the high number of orders, but there is an issue with duplication, standard queues cannot handle this. Only FIFO can handle this part, so unless there is an answer to this, the answer is A

Decoupling systems and growing demand. Definitely SQS and EC2 ASG.

Answer C A is wrong. --SQS FIFO Que can handle only 300 messages per second and the question satats many thousand orders /second