Key points

• A topic can publish one message to multiple supported subscriber types.
• For durable independent consumers, subscribe a separate SQS queue for each consumer path.
• Filter policies can reduce irrelevant deliveries, but consumers still need idempotency and failure handling.

Best-known use cases

• Fan out an event to multiple application domains.
• Send push notifications through supported endpoints.

What candidates often confuse it with

• SNS pushes to subscribers; SQS retains work for pull-based consumers.
• SNS fan-out is simpler; EventBridge provides richer event-bus routing and integrations.

Key takeaway

Choose SNS for push fan-out; add SQS queues when every consumer needs its own durable backlog.

Related services

• Amazon SQS
• Amazon EventBridge
• AWS Lambda

Relevant exam tasks

• D2.1

Learn more

• Amazon SNS