DVA-C02 · Question #531
A company has an application that processes audio files for different departments. When audio files are saved to an Amazon S3 bucket, an AWS Lambda function receives an event notification and processe
The correct answer is A. Configure the S3 bucket to send the event notifications to an Amazon Simple Notification Service. An SNS topic as the S3 event notification destination enables fan-out to multiple SQS queues, routing audio file location events to each department independently without modifying Lambda code.
Question
A company has an application that processes audio files for different departments. When audio files are saved to an Amazon S3 bucket, an AWS Lambda function receives an event notification and processes the audio input. A developer needs to update the solution so that the application can process the audio files for each department independently. The application must publish the audio file location for each department to each department's existing Amazon Simple Queue Service (Amazon SQS) queue. Which solution will meet these requirements with no changes to the Lambda function code?
Options
- AConfigure the S3 bucket to send the event notifications to an Amazon Simple Notification Service
- BUpdate the Lambda function to write the file location to a single shared SQS queue. Configure the
- CUpdate the Lambda function to send the file location to each department's SQS queue.
- DConfigure the S3 bucket to send the event notifications to each department's SQS queue.
How the community answered
(24 responses)- A54% (13)
- B25% (6)
- C8% (2)
- D13% (3)
Why each option
An SNS topic as the S3 event notification destination enables fan-out to multiple SQS queues, routing audio file location events to each department independently without modifying Lambda code.
S3 event notifications can target an SNS topic. SNS supports the fan-out pattern, where a single published message is delivered to all subscribed endpoints simultaneously. By subscribing each department's SQS queue to the SNS topic, each department independently receives the audio file location without any changes to the Lambda function that processes the audio.
Writing to a single shared SQS queue and adding filtering logic requires changes to the Lambda function code, violating the no-code-change requirement.
Updating the Lambda function to send messages to each department's individual SQS queue explicitly requires modifying the Lambda function code.
S3 event notifications support sending to multiple destinations, but you cannot configure a single S3 event to natively fan out to multiple distinct SQS queues for different departments without an intermediary like SNS.
Concept tested: S3 to SNS fan-out pattern for multi-queue event distribution
Source: https://docs.aws.amazon.com/AmazonS3/latest/userguide/NotificationHowTo.html
Community Discussion
No community discussion yet for this question.