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

Option C Dynamo DB is a NoSQL-JSON supported

A. Configuring EMR and an Aurora DB cluster for this use case would introduce unnecessary complexity and operational overhead. EMR is typically used for processing large datasets and running big data frameworks like Apache Spark or Hadoop. B. While using S3 event notifications and SQS for decoupling is a good approach, using EC2 to process the data would introduce operational overhead in terms of managing and scaling the EC2. D. Using EventBridge and Kinesis Data Streams for this use case would introduce additional complexity and operational overhead compared to the other options. EventBridge and Kinesis are typically used for real-time streaming and processing of large volumes of data. In summary, option C is the recommended solution as it provides a serverless and scalable approach for processing uploaded files using S3 event notifications, SQS, and Lambda. It offers low operational overhead, automatic scaling, and efficient handling of varying demand. Storing the resulting JSON file in DynamoDB aligns with the requirement of saving the data for later analysis.

Ans C - as per cookieMr (1 yr, 2 mth ago) "...In summary, option C is the recommended solution as it provides a serverless and scalable approach for processing uploaded files using S3 event notifications, SQS, and Lambda. It offers low operational overhead, automatic scaling, and efficient handling of varying demand. Storing the resulting JSON file in DynamoDB aligns with the requirement of saving the data for later analysis."

Option C, fulfills the least operational overhead condition.

B where we use EC2 instances for processing would be ideal in situations where runtime is > 15 minutes. However the question mentions 'simple processing', hence we go for Lambda.

LEAST operational overhead A: EMR is massive programming effort for this B: EC2 is considerable overhead D: Nice solution but why would you use Kinesis as there is no streaming scenario here C: Simplest and all managed services so least operational overhead compared to other options

Option C is the best solution that meets the requirements with the least operational overhead: Configure Amazon S3 to send event notification to SQS queue Use Lambda function triggered by SQS to process each file Store output JSON in DynamoDB This leverages serverless components like S3, SQS, Lambda, and DynamoDB to provide automated file processing without needing to provision and manage servers. SQS queues the notifications and Lambda scales automatically to handle spikes and drops in file uploads. No EMR cluster or EC2 Fleet is needed to manage.

C: Lambdas are made for that

C is best

Option C is the best solution that meets the requirements with the least operational overhead: Configure Amazon S3 to send event notification to SQS queue Use Lambda function triggered by SQS to process each file Store output JSON in DynamoDB This leverages serverless components like S3, SQS, Lambda, and DynamoDB to provide automated file processing without needing to provision and manage servers. SQS queues the notifications and Lambda scales automatically to handle spikes and drops in file uploads. No EMR cluster or EC2 Fleet is needed to manage.

Option C is correct - Dynamo DB is a NoSQL-JSON supported

SQS + LAMDA + JSON >>>>>> Dynamo DB

The option C is right answer.

can someone explain why SQS? it's a poll-based messaging, does it guarantee reacting the event asap?

Dynamo DB is a NoSQL-JSON supported

Option C, Configuring Amazon S3 to send an event notification to an Amazon Simple Queue Service (SQS) queue and using an AWS Lambda function to read from the queue and process the data, would likely be the solution with the least operational overhead. AWS Lambda is a serverless computing service that allows you to run code without the need to provision or manage infrastructure. When a new file is uploaded to Amazon S3, it can trigger an event notification which sends a message to an SQS queue. The Lambda function can then be set up to be triggered by messages in the queue, and it can process the data and store the resulting JSON file in Amazon DynamoDB.

Option C as JSON is supported by DynamoDB. RDS or AuroraDB are not suitable for JSON data. A - Because this is not a Bigdata analytics usecase.