Q20 — AWS SAP-C02 Ch.1

Question 20 of 75 | ← Chapter 1

Q95. A company is hosting a monolithic REST-based API for a mobile app on five Amazon EC2 instances in public subnets of a VPC. Mobile clients connect to the API by using a domain name that is hosted on Amazon Route 53. The company has created a Route 53 multivalue answer routing policy with the IP addresses of all the EC2 instances. Recently, the app has been overwhelmed by large and sudden increases to traffic. The app has not been able to keep up with the traffic. A solutions architect needs to implement a solution so that the app can handle the new and varying load. Which solution will meet these requirements with the LEAST operational overhead?

• A. Separate the API into individual AWS Lambda functions. Configure an Amazon API Gateway RESTAPI with Lambda integration for the backend. Update the Route 53 record to point to the API Gateway API. ✓
• B. Containerize the API logic. Create an Amazon Elastic Kubernetes Service (Amazon EKS) cluster. Run the containers in the cluster by using Amazon EC2. Create a Kubernetes ingress. Update the Route 53 record to point to the Kubernetes ingress.
• C. Create an Auto Scaling group. Place all the EC2 instances in the Auto Scaling group. Configure the Auto Scaling group to perform scaling actions that are based on CPU utilization. Create an AWS Lambda function that reacts to Auto Scaling group changes and updates the Route 53 record.
• D. Create an Application Load Balancer (ALB) in front of the API. Move the EC2instances to private subnets in the VPC.Add the EC2 instances as targets for the ALB. Update the Route 53 record to point to the ALB.

Correct Answer: A. Separate the API into individual AWS Lambda functions. Configure an Amazon API Gateway RESTAPI with Lambda integration for the backend. Update the Route 53 record to point to the API Gateway API.

Explanation

To handle the new and varying load on the monolithic REST-based API with the least operational overhead, the following solution can be implemented: A. Separate the API into individual AWS Lambda functions. Configure an Amazon API Gateway REST API with Lambda integration for the backend. Update the Route 53 record to point to the API Gateway API. By separating the monolithic API into individual AWS Lambda functions, the application can benefit from the scalability and automatic scaling capabilities of Lambda. Each Lambda function can handle a specific endpoint or functionality of the API, allowing for better resource allocation and efficient scaling. Configuring an Amazon API Gateway REST API with Lambda integration allows the API Gateway to act as a front-end for the Lambda functions, handling the incoming requests and routing them to the appropriate Lambda function. Updating the Route 53 record to point to the API Gateway API ensures that client traffic is directed to the API Gateway, which then forwards the requests to the Lambda functions. This solution minimizes operational overhead by leveraging the serverless capabilities of Lambda and the API Gateway, eliminating the need to manage and scale EC2 instances manually. Therefore, the solution with the least operational overhead is to separate the API into individual AWS Lambda functions, configure an Amazon API Gateway REST API with Lambda integration, and update the Route 53 record to point to the API Gateway.