Explanation:
To prioritize specific types of messages in an SQS-based architecture, the standard pattern is to use multiple queues. By creating a dedicated queue for high-priority messages (alarm notifications) and another for lower-priority ones (information notifications), the consumer application logic can be configured to check the high-priority queue first. This ensures critical messages are processed immediately even if there is a backlog of informational messages.
Ultimate access to all questions.
Question #29
A company has an application that collects notifications from thousands of alarm systems. The notifications include alarm notifications and information notifications. The information notifications include the system arming processes, disarming processes, and sensor status.
All notifications are kept as messages in an Amazon Simple Queue Service (Amazon SQS) queue. Amazon EC2 instances that are in an Auto Scaling group process the messages. A CloudOps engineer needs to implement a solution that prioritizes alarm notifications over information notifications.
Which solution will meet these requirements?
A
Adjust the Auto Scaling group to scale faster when a high number of messages is in the queue.
B
Use the Amazon Simple Notification Service (Amazon SNS) fanout feature with Amazon SQS to send the notifications in parallel to all the EC2 instances.
C
Add an Amazon DynamoDB stream to accelerate the message processing.
D
Create a queue for alarm notifications and a queue for information notifications. Update the application to collect messages from the alarm notifications queue first.
E
None
F
None
No comments yet.