A company has an application that collects notifications from thousands of alarm systems. Notifications include alarm notifications and information notifications. All notifications are stored in an Am

Question

Options

• AScale the Auto Scaling group faster when message volume increases.
• BUse Amazon SNS fanout to send messages to all EC2 instances.
• CAdd an Amazon DynamoDB stream to accelerate processing.
• DCreate separate SQS queues for alarm notifications and information notifications and process

• A
  3% (1)
• B
  14% (5)
• C
  9% (3)
• D
  74% (26)

Explanation

Explanation

Creating separate SQS queues - one for alarm notifications and one for information notifications - allows EC2 instances to poll the alarm queue first, ensuring high-priority messages are processed before informational ones. This is the standard AWS architectural pattern for message prioritization, as a single SQS queue has no native priority ordering mechanism.

Why the distractors are wrong:

• Option A simply scales processing capacity faster but does nothing to distinguish which messages get processed first - both message types would still compete equally in the same queue.
• Option B SNS fanout distributes messages to multiple endpoints simultaneously, which addresses fan-out delivery, not priority processing.
• Option C DynamoDB Streams is a change-data-capture feature for DynamoDB tables and has no relevance to SQS message prioritization.

Memory Tip

Think of it like an emergency triage system - you don't put critical patients and routine check-ups in the same waiting room line. Give each priority its own queue, and direct your workers (EC2 instances) to check the urgent queue first. Whenever you see "prioritize" + "SQS," immediately think separate queues with dedicated consumers.

No community discussion yet for this question.