CloudGuild · Blog · Cheat sheets · Lessons · Certifications
Exam Question Walkthrough for AWS Certified Solutions Architect - Associate (SAA-C03)
Master the SAA-C03 exam with this detailed breakdown of a key question on microservices architecture.
Designing a microservices architecture can trip up many candidates. The choice of services significantly impacts scalability and resilience. Let's break it down.
The question
You are designing a microservices architecture for an application that requires high scalability and resilience. Each microservice needs to communicate with others and handle varying loads efficiently. Which AWS service combination would best support this architecture?
- A. Amazon EC2 and Elastic Load Balancing
- B. AWS Lambda and Amazon API Gateway
- C. Amazon ECS and Amazon RDS
- D. Amazon EKS and Amazon DynamoDB
Think before you scroll
Consider how each option manages scalability and resilience. Focus on serverless versus traditional infrastructure. This distinction is crucial for microservices.
The answer
The correct option is B. AWS Lambda and Amazon API Gateway. AWS Lambda allows you to run code without provisioning servers. This means it inherently supports high scalability and resilience. Amazon API Gateway efficiently manages communication between microservices, making this combination ideal for a microservices architecture.
Why the other options lose
- A. Amazon EC2 and Elastic Load Balancing: While this combination can handle high loads, it requires you to manage the EC2 instances, which adds complexity. Scalability is dependent on your ability to provision and manage infrastructure.
- C. Amazon ECS and Amazon RDS: This option involves container orchestration and a relational database. Though it can scale, it does not match the serverless model's efficiency. Managing RDS also introduces potential bottlenecks.
- D. Amazon EKS and Amazon DynamoDB: Using EKS for container orchestration with DynamoDB offers scalability. However, it still requires managing Kubernetes clusters, which adds operational overhead compared to serverless solutions.
The concept behind it
The key principle here is the serverless architecture. AWS Lambda abstracts away server management, allowing teams to focus on code. This leads to better scalability and resilience, especially in microservices, where each service can independently scale based on demand.
Exam trap to remember
Remember: for microservices requiring high scalability and resilience, serverless options like AWS Lambda are often superior to traditional infrastructure models.