SAA-C03 Question 92
Select 4A company is building a web application that experiences unpredictable spikes in traffic. The application stores user data in a relational database and uses a RESTful API to process requests. The company wants the architecture to automatically handle traffic spikes, ensure high availability, and minimize operational overhead. Which combination of AWS services should they use to design a scalable and loosely coupled architecture?
- A
Amazon RDS with Multi-AZ deployment for the database
- B
Amazon EC2 Auto Scaling for the web servers
- C
Elastic Load Balancer (ELB) to distribute incoming traffic
- D
Amazon SQS to decouple the application components
- E
Amazon EFS to store static website content
Show answer and explanation
Correct answers: A, B, C, D
Explanation
To design a scalable and loosely coupled architecture, the combination of Amazon RDS with Multi-AZ, EC2 Auto Scaling, ELB, and Amazon SQS ensures high availability, fault tolerance, and the ability to handle unpredictable traffic spikes. These services work together to minimize operational overhead, decouple components, and provide a robust solution for the web application. Amazon EFS, while useful in other scenarios, is not relevant for this specific use case.
- A. Correct.
Amazon RDS with Multi-AZ deployment ensures high availability and fault tolerance for the relational database, which is critical for handling unpredictable traffic spikes.
- B. Correct.
Amazon EC2 Auto Scaling automatically adjusts the number of EC2 instances to handle changes in traffic, ensuring scalability and minimizing operational overhead.
- C. Correct.
Elastic Load Balancer (ELB) distributes incoming traffic across multiple targets, improving fault tolerance and scaling during traffic spikes.
- D. Correct.
Amazon SQS allows asynchronous communication between application components, decoupling them and making the system more resilient and scalable.
- E. Incorrect.
Amazon EFS is primarily used for file storage and is not required for this use case. Serving static content would typically be handled by Amazon S3 and/or Amazon CloudFront.