An application ingests messages from thousands of alarm systems. Messages comprise high-priority alarm alerts and lower-priority informational messages (arming/disarming, sensor states). All messages are stored in a single Amazon SQS queue and processed by EC2 workers in an Auto Scaling group. The administrator must ensure alarm alerts are processed before informational messages. Which design meets this requirement?

Creating two SQS queues, one for high-priority alarm alerts and another for lower-priority informational messages, allows for prioritized processing. The application can be designed to always consume from the alarm queue first, ensuring critical alerts are handled promptly. This directly addresses the requirement for processing alarm alerts before informational messages. Tuning the Auto Scaling group for faster scaling doesn't guarantee prioritization; it only increases overall processing capacity. Using Amazon SNS fanout with SQS broadcasts all messages in parallel, but doesn't differentiate or prioritize message types. Introducing an Amazon DynamoDB stream is irrelevant to SQS message prioritization; DynamoDB streams capture item-level modifications in a DynamoDB table, not SQS messages.