Examkin

Question

Difficulty: EasyDecoupling Architectures and Event-Driven Messaging

A company is building a ride-sharing application. The application must process passenger ride-status updates, such as requested, driver assigned, and completed, asynchronously. To ensure the passenger history displays correctly, these updates must be processed in the exact sequence they occurred. The system processes approximately 150 updates per second. Which solution meets these requirements with the least operational overhead?

  1. Send the ride-status update messages to an Amazon SQS FIFO queue and process them sequentially.Answer
  2. B
    Send the ride-status update messages to an Amazon SQS Standard queue and sort them by timestamp in the consumer application.
  3. C
    Send the ride-status update messages to an Amazon SQS Standard queue and set a delivery delay on the queue.
  4. D
    Send the ride-status update messages to an Amazon SQS Standard queue and configure a single consumer instance to process them one at a time.

Answer

Send the ride-status update messages to an Amazon SQS FIFO queue and process them sequentially.
The correct option correctly identifies Amazon SQS FIFO queues as the native AWS solution to guarantee that messages are processed in the exact order they are received. Since the application processes 150 updates per second, it falls well within the default limit of 300 transactions per second for FIFO queues without batching, satisfying the request with minimal operational complexity.

Step-by-Step Solution

1
Analyze the requirements for message ordering and throughput.
The application requires strict first-in, first-out (FIFO) ordering for ride-status updates at a rate of 150 updates per second.
This determines whether a standard queue or a FIFO queue is required.
2
Evaluate the capabilities of Amazon SQS queue types.
Amazon SQS FIFO queues guarantee order preservation and support up to 300 transactions per second (TPS) without batching, which exceeds the required 150 updates per second. Amazon SQS Standard queues do not guarantee ordering.
This identifies the only queue type that natively supports the strict ordering constraint without custom sorting logic.
3
Select the solution with the least operational overhead.
Using an Amazon SQS FIFO queue natively fulfills the ordering requirement without requiring additional consumer sorting logic or complex custom applications.
This satisfies the requirement to minimize operational overhead.

Key Concept

Amazon SQS FIFO queues preserve the exact ordering of messages and are ideal for low-to-medium throughput applications requiring strict sequencing.
Estimated Time:45s
Rate this question

Topics

Decoupling Architectures and Event-Driven Messaging

More questions from this topic