SAA-C03 Question 94
Select 3A company is building a web application that serves users across multiple geographic regions. The application consists of a frontend hosted on Amazon S3 and an API backend that processes requests using Amazon API Gateway and AWS Lambda. The company expects significant traffic growth and wants to design the architecture to be scalable, fault-tolerant, and loosely coupled. What additional components should you include in the architecture to meet these requirements?
- A
Use Amazon CloudFront to distribute content globally and reduce latency.
- B
Implement Amazon RDS in a Multi-AZ configuration to handle API requests.
- C
Add an Amazon SQS queue between API Gateway and AWS Lambda to decouple the services.
- D
Deploy the application in multiple AWS Regions and use Route 53 for DNS-based routing.
- E
Use Elastic Load Balancing (ELB) to distribute traffic directly to the Amazon S3 bucket.
Show answer and explanation
Correct answers: A, C, D
Explanation
To create a scalable and loosely coupled architecture, using Amazon CloudFront reduces latency for static content, while Amazon SQS decouples services to handle traffic spikes more effectively. Deploying the application across multiple AWS Regions with Route 53 ensures fault tolerance and low-latency DNS routing for global users. These elements work together to meet the company's requirements for scalability, fault tolerance, and loose coupling.
- A. Correct.
Correct. Amazon CloudFront helps distribute static and dynamic content globally, reducing latency and improving performance for users across multiple regions.
- B. Incorrect.
Incorrect. Amazon RDS is not suitable for API request handling in this architecture. AWS Lambda and Amazon API Gateway already handle backend processing in this scenario.
- C. Correct.
Correct. Adding an Amazon SQS queue between API Gateway and AWS Lambda decouples the services, allowing the architecture to handle traffic spikes more effectively.
- D. Correct.
Correct. Deploying the application in multiple AWS Regions improves fault tolerance and reduces latency for users in different geographic regions when paired with Route 53 for DNS-based routing.
- E. Incorrect.
Incorrect. Elastic Load Balancing cannot distribute traffic directly to an Amazon S3 bucket. S3 is not designed to work directly with ELB.