Examice

Exam SAP-C01 All QuestionsBrowse all questions from this exam

Question 960

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 erupted 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?

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.

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.

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.

Create an Application Load Balancer (ALB) in front of the API. Move the EC2 instances 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: D

The best solution for a company hosting a monolithic REST-based API overwhelmed by large and sudden increases in traffic is to create an Application Load Balancer (ALB) in front of the API. Moving the EC2 instances to private subnets and adding them as targets for the ALB ensures efficient distribution of incoming requests. The ALB can handle varying loads and scales automatically, providing both high availability and scalability. This approach requires minimal operational overhead compared to other options, such as refactoring the application to use AWS Lambda functions or containerizing the application for an Amazon EKS cluster.

Discussion

Vash2303Option: A

less operational overhead is the key

Kende

C is the one.

EastmanKan

A will have less operational overhead, though the effort converting the application to Lambda will be big.

WhyIronManOption: D

D The option A is: High Operational Overhead: This approach requires significant refactoring of the monolithic application into microservices, which can be complex and time-consuming. Suitability: While serverless architecture offers benefits, the effort involved in breaking down the monolithic API may not justify the overhead for the immediate need to handle traffic spikes.

WhyIronMan

for those who choose A, what if the API is not supported by lambdas or api gateways

dev112233xxOption: D

A doesn't make sense to refactor all the code to Lambda and API Gateway.. If I propose such a solution to my CEO I will be thrown out of the nearest window Lol ALB which spread the traffic to the EC2 instances instead of Route 53 Multi value

Heer

OPTION D has 'Create an Application Load Balancer (ALB) in front of the API.' API has to be in front of ALB .So this option is ruled out Option A looks to be more with less operational overhead . So seems like the pick should be A

masetromain

I think it's A or D. A seems be great but I am not sure why "Separate the API into individual AWS Lambda functions" D is possible: https://aws.amazon.com/fr/premiumsupport/knowledge-center/api-gateway-application-load-balancers/

Kende

A: Rewriting everything is too much overhead. D: It does not scale.