Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 376 discussion

Considering the requirements, Option B (Amazon EventBridge with AWS Lambda and S3 Lifecycle Expiration Policy) seems to be the most cost-effective and appropriate solution. It combines the scalability and flexibility of AWS Lambda for image processing with the straightforward event handling of Amazon EventBridge, and appropriately manages the image lifecycle with an S3 expiration policy. While Option C is also a strong contender, the misalignment of the lifecycle policy with the requirement makes Option B a better fit. Option A might be more suitable for complex workflows but is likely not needed for this scenario, and Option D includes unnecessary long-term archival steps.

B is for sure A no because Step Function is not in list of s3 event destinations https://docs.aws.amazon.com/AmazonS3/latest/userguide/notification-how-to-event-types-and-destinations.html C and D has option for storing data longer than 6 months which is not required

Option B is the best answer. Answer D is not, since it includes to keep files in deep archive which is not cost effective.

why store data after 6 months also there is no mention of using any preferred or required s3 storage tier. cannot simply associate cost-effect to S3-IA

The solution will receive batches of large image files, resize the files, and store the files in an Amazon S3 bucket for up to 6 months. It dosent mean delete after 6 months. Option D preserves this logic: Receives the original image and stores it in S3. Lambda resizes it and stores another copy (the resized one). You now have both files. S3 lifecycle rules manage cost: Store in Standard-IA initially, then move to Glacier Deep Archive if needed, or delete after 6 months.

it's definitely not D, there's no point in archiving the data past 6 months.

Option B (Amazon EventBridge with AWS Lambda and S3 Lifecycle Expiration Policy) seems to be the most cost-effective and appropriate solution. It combines the scalability and flexibility of AWS Lambda for image processing with the straightforward event handling of Amazon EventBridge, and appropriately manages the image lifecycle with an S3 expiration policy.

Invoking Lambda directly won't give any resiliency - so C is not a choice. Since the Event Bridge solution tries to replace original file - its rule out. Step function can't be destined from S3 - A is out. Hence the right answer is D through SQS meeting the need for re-run.

Options A and B imply replacing the original image, which will cause an execution loop. Option C doesn't allow rerunning failed jobs. Therefore, only option D meets all the requirements.

This is a very malformed question. It should be D because SQS can handle failure. But then the archiving policy is not requested. So all options are not optimal in my opinion.

Archiving and replaying events with Amazon EventBridge https://aws.amazon.com/blogs/compute/archiving-and-replaying-events-with-amazon-eventbridge/

Option D is most cost effective

need to rerun failed jobs, so D

Difficult one. Both options B and D meet the specific requirement of storing the files in an Amazon S3 bucket for up to 6 months. However, when considering the additional requirements of being reliable at enterprise scale, having the ability to rerun processing jobs in the event of failure, and being the most cost-effective solution, option D with Amazon SQS, AWS Lambda, and the S3 Lifecycle policy to transition to Glacier Deep Archive is still the better choice. No Rerun of jobs with B. Only D

"Store the images in S3 for six months" - leaves only option B. Options C & D mean keeping the images in S3 forever and that's not the more cost effective option compared to just deleting the files as the question implies is a requirement.

You’ve got to have a buffer for reruns! For those concerned about the 6 months TTL in S3 remember glacier isn’t S3.

C and D are out, for keeping data more than 6 months. A is out, due to S3 event destination does not include step function, which is anyway seldom use for one step action. Eventbridge does support retry if event fail to go off: