A developer is creating a service that uses an Amazon S3 bucket for image uploads. The service will use an AWS Lambda function to create a thumbnail of each image. Each time an image is uploaded, the

By configuring the S3 bucket to publish object-created events to an SNS topic, and then subscribing both a Lambda function and an email endpoint (via SNS email subscription) to that topic, a single upload event fans out to both processing paths concurrently. This is the standard AWS fan-out pattern using SNS, requiring no polling and no additional coordination code.

The answer choices B and C/D involving SQS would serialize processing or require polling, and a single SQS queue cannot natively deliver the same message to both Lambda and an email endpoint simultaneously.

SQS is a point-to-point queue; a single message can only be consumed once by one consumer, making it unsuitable for delivering the same event to multiple independent processors without additional fan-out infrastructure.

Sending S3 events directly to SQS and then to a second service adds unnecessary complexity and does not natively support email delivery without additional services.