Home › AWS Solutions Architect Associate › cloudcomputing › resilientarchitectures › Which combination best implements a write-heavy …
Which combination best implements a write-heavy event ingestion pipeline that needs to fan-out the same event to multiple downstream consumers (e.g., a database, an analytics pipeline, and a notification system)?
AAmazon SNS for fan-out → multiple SQS queues (one per consumer) → consumers
BAmazon S3 Glacier Deep Archive as the event bus
CAmazon Route 53 latency-based routing as the event router
DSingle SQS queue read by all three consumers simultaneously
Answer & Solution
Correct answer: A. Amazon SNS for fan-out → multiple SQS queues (one per consumer) → consumers
SNS publishes once → fan-outs to subscribed SQS queues (one per consumer) so each consumer gets its own copy and processes independently. A single SQS queue with many readers competes for messages (one read wins). Glacier and Route 53 aren't event buses.
Related questions
A stateless web tier sits behind an ALB across 3 AZs. The team wants to remove ANY single Step Functions on AWS is best characterised as:Which AWS pattern lets an HTTP API handle 10× traffic spikes WITHOUT provisioning EC2 capaA workload requires recovery from a complete AWS Region failure with an RPO measured in miWhich database read-scaling primitive lets an Amazon RDS or Aurora cluster offload read-onWhen designing a multi-tier web app on AWS, which AWS Load Balancer type best fits an HTTPWhich AWS storage type is shared, mountable as a network file system (NFS), and ideal for A workload that needs to process bursty incoming events with retries and dead-letter handl