AWS Lambda for Serverless Microservices in SAA-C03

SAA-C03 By islever Editorial Last updated

Short answer

D Use an AWS Lambda function that runs custom developed code.

Question

A company wants to rearchitect a large-scale web application to a serverless microservices architecture. The application uses Amazon EC2 instances and is written in Python. The company selected one component of the web application to test as a microservice. The component supports hundreds of requests each second. The company wants to create and test the microservice on an AWS solution that supports Python. The solution must also scale automatically and require minimal infrastructure and minimal operational support. Which solution will meet these requirements?
  1. Use a Spot Fleet with auto scaling of EC2 instances that run the most recent Amazon Linux operating system.
  2. Use an AWS Elastic Beanstalk web server environment that has high availability configured.
  3. Use Amazon Elastic Kubernetes Service (Amazon EKS). Launch Auto Scaling groups of self-managed EC2 instances.
  4. Use an AWS Lambda function that runs custom developed code. Correct Answer

Key Takeaways

The core trap is confusing 'microservices' with container-based orchestration (EKS/ECS), while the correct answer leverages Function-as-a-Service (FaaS) for true serverless benefits.

This question tests the design of serverless microservices using AWS Lambda to meet requirements for Python support, automatic scaling, and minimal operational overhead.

Common mistake: Many learners choose EKS or Elastic Beanstalk because they associate 'microservices' strictly with containers, overlooking that Lambda is a valid serverless microservice architecture.

Expert Analysis

Why the Answer Is Correct

Option D is the only solution that fully satisfies the 'serverless', 'minimal infrastructure', and 'minimal operational support' constraints. AWS Lambda automatically handles capacity provisioning, patching, and scaling, allowing developers to deploy Python code without managing any underlying servers.

Why the Other Options Are Wrong

Options A (EC2 Spot Fleet) and C (EKS with self-managed EC2) require significant infrastructure management, including OS updates, security patching, and cluster maintenance, violating the 'minimal operational support' requirement. Option B (Elastic Beanstalk) abstracts some management but still requires managing the underlying instances and load balancers, making it less 'serverless' than Lambda.

Community Comment Notes

While the majority voted for D, some commenters argued for C, stating "C is the correct answer" based on the belief that microservices must be containerized. However, this ignores the specific constraint regarding minimal operational support and the explicit request for a serverless approach. As one user noted, Lambda provides the necessary scalability and serverless nature that EKS does not offer out-of-the-box.

Exam Strategy

When you see 'serverless', 'minimal operational overhead', or 'automatic scaling' combined with 'code deployment', immediately consider AWS Lambda before containers. Remember that microservices can be implemented as functions, not just containers.

Frequently Asked Questions

Is Lambda considered a microservice?

Yes, AWS Lambda allows you to deploy individual functions as independent services, fitting the microservices pattern without container overhead.

Why not use Elastic Beanstalk?

Elastic Beanstalk manages EC2 instances behind the scenes, requiring more operational effort than Lambda's fully managed serverless environment.

More SAA-C03 FAQ →

Community Votes

D
100%

100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 8 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 8

  1. Andy_09 👍 11
    Lambda looks like a better option
  2. Typewriter101 👍 8 Answered D
    Lambda serverless, scalable, minimal infrastructure, handling hundreds of requests per second
  3. sandordini 👍 5 Answered D
    A: auto-scaling of EC2 instances - Lot of overhead + Infra B: The company selected one component of the web application to test as a microservice. The component supports hundreds of requests each second. > lastic Beanstalk is a bad choice if you need worker processes. The whole point of a worker process is to perform a task in the background without slowing down your main web app. But Elastic Beanstalk doesn't support this option in a scalable way. Also, they want to test just 1 selected microservice and I think it's a bit of overkill to do it using Elastic Beanstalk. Happy to be challenged though! C: self-managed EC2 instances > infra + operational overhead D: Lambda supports Python, microservice should be quicker than 15 mins, worst case scenario the test will fail.. (that's the purpose tests are conducted for anyway..) I'd go for D
  4. Umuntu 👍 3
    C is the correct answer. The best way to deploy microservice is to use container-based service such as EKS or ECS. So C is great
  5. alawada 👍 1 Answered C
    C is the correct answer. The best way to deploy microservice is to use container-based service
Show 3 more comments
  1. rubiteb 👍 1
    Best answer is C. The application is a large-scale we app as mentioned in the question.
  2. Andy_09 👍 1
    EBS for minimal infra maintenance
  3. gsgdga 👍 1 Answered C
    microservice => EKS, ECS

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Practice All SAA-C03 Questions

Access 120 questions with complete answers and detailed explanations.

View Full SAA-C03 Practice Test →

← Back to SAA-C03 Study Guide