Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 18 discussion

To design a solution that uses durable, stateless components to process images automatically, a solutions architect could consider the following actions: Option A involves creating an SQS queue and configuring the S3 bucket to send a notification to the queue when an image is uploaded. This allows the application to decouple the image upload process from the image processing process and ensures that the image processing process is triggered automatically when a new image is uploaded. Option B involves configuring the Lambda function to use the SQS queue as the invocation source. When the SQS message is successfully processed, the message is deleted from the queue. This ensures that the Lambda function is invoked only once per image and that the image is not processed multiple times.

It looks like A-B

Use S3 → SQS → Lambda with stateless processing logic for a durable, scalable, and serverless image processing pipeline.

AB: S3-SQS-Lambda

High level flow: Web (1) -> Internet (2) -> Uploaded image bucket (3) -> Compressed image bucket (4) Let's break this down. Image uploading (1)(2)(3): If the image's size is big, multi upload is a MUST. If you want to accelerate the process, you can also use Acceleration Transfer with additional fee. Image compressing (3)(4): SQS Simple Queue can directly integrate with S3 events. For every image uploaded, S3 event will create a message in SQS queue. After that, Lambda can be invoked to compress the image and then upload the image to destination bucket.

Keywords: - Store the image in an Amazon S3 bucket, process and compress the image with an AWS Lambda function. - Durable, stateless components to process the images automatically A,B: Correct - SQS has message retention function(store message) default 4 days(can increate update 14 days) so that you can re-run lambda if there are any errors when processing the images. C: Incorrect - Lambda function just run the request then stop, the max tmeout is 15 mins. So we cannot store data in the ram of Lambda function. D: Incorrect - we can trigger Lambda dirrectly from SQS no need EC2 instance in this case E: Incorrect - It kinds of manually step -> the owner has to read email then process it :))

Explanation: Option A: By creating an Amazon SQS queue and configuring the S3 bucket to send a notification to the SQS queue when an image is uploaded, the system establishes a durable and scalable way to handle incoming image processing tasks. Option B: Configuring the Lambda function to use the SQS queue as the invocation source allows it to retrieve messages from the queue and process them in a stateless manner. After successfully processing the image, the Lambda function can delete the message from the queue to avoid duplicate processing.

A. Create an Amazon Simple Queue Service (Amazon SQS) queue. Configure the S3 bucket to send a notification to the SQS queue when an image is uploaded to the S3 bucket. B. Configure the Lambda function to use the Amazon Simple Queue Service (Amazon SQS) queue as the invocation source. When the SQS message is successfully processed, delete the message in the queue. Explanation: A (SQS Queue): Using SQS to decouple the S3 bucket from the processing components provides durability and scalability. When an image is uploaded, a notification is sent to the SQS queue. B (Lambda with SQS Trigger): Configuring the Lambda function to use the SQS queue as the invocation source allows for stateless and scalable image processing. Lambda can be triggered by messages in the SQS queue, and upon successful processing, the message can be deleted, ensuring that each message (image) is processed once. This combination ensures a durable, stateless, and scalable architecture for processing images automatically in response to user uploads.

Option A is a correct because it allows for decoupling between the image upload process and image processing. By configuring S3 to send a notification to SQS, image upload event is recorded and can be processed independently by microservice. Option B is also a correct because it ensures that Lambda is triggered by messages in SQS. Lambda can retrieve image information from SQS, process and compress image, and store compressed image in a different S3. Once processing is successful, Lambda can delete processed message from SQS, indicating that image has been processed. Option C is not recommended because it introduces a stateful approach by using a text file to keep track of processed images. Option D is not optimal solution as it introduces unnecessary complexity by involving an EC2 to monitor SQS and maintain a text file. Option E is not directly related to requirement of processing images automatically. Although EventBridge and SNS can be useful for event notifications and further processing, they don't provide the same level of durability and scalability as SQS.

Ans A,B - as per Buruguduystunstugudunstuy's response: stateless, robust

whenever we talk about microservices we should mention SQS, so A and B are the right answers

A/B make the most sense and in practice this works, I've done it.

Answer- A,B

I can not understand why it is not as simple like s3-1 event destination to notify the lambda function to process and upload to s3-2

Option AB MET THE REQUIREMENT

D and E are distractions. C seems a valid solution. However, as you have to select two, A and B are the only two that work in conjunction with each other.

A and B are optimal solutions