SAP-C02 Question 654
Single answerA company is building a real-time image processing application where images are uploaded by users and need to be processed within seconds. The application must dynamically scale based on demand, maintain low operational overhead, and minimize costs. Which serverless compute architecture would best meet these requirements?
- A
Use AWS Lambda to trigger image processing upon file upload to an S3 bucket, and store the results in Amazon DynamoDB.
- B
Deploy the application on an Amazon EC2 Auto Scaling group configured to scale based on CPU utilization.
- C
Use AWS Fargate to run containers for processing images, triggered by an Amazon SQS queue.
- D
Set up an AWS Elastic Beanstalk environment with an application that processes images upon request.
Show answer and explanation
Correct answer: A
Explanation
AWS Lambda is the most appropriate serverless compute option for an event-driven architecture. It integrates natively with Amazon S3 to enable automatic triggers upon file uploads, scales automatically based on demand, and minimizes both operational overhead and costs. The other options introduce unnecessary complexity or do not fully adhere to the serverless paradigm.
- A. Correct.
This is the correct option. AWS Lambda is a serverless compute option that is event-driven and can scale automatically to process images in near real-time. By integrating with Amazon S3, the solution can trigger Lambda functions upon file uploads. It minimizes operational overhead and costs as Lambda charges only for the compute time used.
- B. Incorrect.
Incorrect. While EC2 Auto Scaling can scale based on demand, it is not a serverless solution. It requires managing instances, AMIs, and scaling policies, which increases operational overhead compared to AWS Lambda.
- C. Incorrect.
Incorrect. AWS Fargate is a serverless compute option for containers, but it is less suited for near real-time processing triggered by S3 events. Using SQS as a trigger adds latency and complexity in this scenario.
- D. Incorrect.
Incorrect. AWS Elastic Beanstalk simplifies application deployment but still requires managing resources like EC2 instances and load balancers, making it less suitable for a fully serverless and low-overhead solution.