A company is designing a fleet management system that receives diagnostic alerts from vehicles. When an alert is received, it must be sent to two separate applications: a real-time notification service and a maintenance scheduling service. The system must decouple the alert reception from the processing services and handle traffic spikes without losing messages. Strict ordering of the alerts is not required.
Which combination of AWS services should a solutions architect choose to meet these requirements? (Select TWO.)
- Amazon Simple Notification Service (Amazon SNS) to fan out the alerts to multiple destination queues.Answer
- Amazon Simple Queue Service (Amazon SQS) standard queues to buffer the alerts for each processing service.Answer
- CAmazon SQS FIFO queues to guarantee that all alerts are processed in the exact order they are received.
- DAmazon Route 53 with latency-based routing to distribute the alerts directly to the processing instances.
Answer
Amazon Simple Notification Service (Amazon SNS) to fan out the alerts to multiple destination queues, and Amazon Simple Queue Service (Amazon SQS) standard queues to buffer the alerts for each processing service.
To send the same event to multiple downstream systems and decouple them, the solutions architect should use the SNS-to-SQS fan-out pattern. Amazon SNS publishes the event once, and standard Amazon SQS queues subscribed to the SNS topic receive a copy of the message. This decouples the services, buffers the messages to handle traffic spikes, and avoids the unnecessary complexity of FIFO queues since ordering is not required.
Step-by-Step Solution
Key Concept
The combination of Amazon SNS and Amazon SQS (fan-out pattern) allows messages to be sent to multiple destination queues, enabling decoupled, scale-resilient parallel processing without strict ordering requirements.