Explanation:
Amazon SQS does not natively support prioritizing messages within a single queue. To implement a priority-based message processing system, the standard architectural pattern is to use multiple queues: one for high-priority messages (alarm notifications) and another for low-priority messages (information notifications). The message processing application is then configured to poll the high-priority queue first, falling back to the low-priority queue only when the high-priority queue is empty.
Ultimate access to all questions.
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 SysOps administrator 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 C2 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.
No comments yet.