Q73 — AWS SAA-C03 Ch.13

Question 73 of 100 | ← Chapter 13

Q973. An ecommerce company hosts an API that handles sales requests.The company hosts the API frontend on Amazon EC2 instances that run behind an Application Load Balancer(ALB).The company hosts the API backend on EC2 instances that perform the transactions. The backend tiers are loosely coupled by an Amazon Simple Queue Service (Amazon SQS) queue.The company anticipates a significant increase in request volume during a new product launch event. The company wants to ensure that the API can handle increased loads successfullyWhich solution will meet these requirements?

• A. Double the number of frontend and backend EC2 instances to handle the increased traffic during the product launch event. Create a dead-letter queue to retain unprocessed sales requests when the demand exceeds the system capacity.
• B. Place the frontend EC2 instances into an Auto Scaling group.Create an Auto Scaling policy to launch new instances to handle the incoming network traffic.
• C. Place the frontend EC2 instances into an Auto Scaling group. Add an Amazon ElastiCache cluster in front of the ALB to reduce the amount of traffic the API needs to handle
• D. Place the frontend and backend EC2 instances into separate Auto Scaling groups.Create a policy for the frontend Auto Scaling group to launch instances based on incoming network traffic. Create a policy for the backend Auto Scaling group to launch instances based the SQS queue backlog. ✓

Correct Answer: D. Place the frontend and backend EC2 instances into separate Auto Scaling groups.Create a policy for the frontend Auto Scaling group to launch instances based on incoming network traffic. Create a policy for the backend Auto Scaling group to launch instances based the SQS queue backlog.

Explanation

The correct answer is:D. Place the frontend and backend EC2 instances into separate Auto Scaling groups. Create a policy for the frontend Auto Scaling group to launch instances based on incoming network traffic. Create a policy for the backend Auto Scaling group to launch instances based the SQS queue backlog.Explanation:A. Double the number of frontend and backend EC2 instances to handle the increased traffic during the product launch event. Create a dead-letter queue to retain unprocessed sales requests when the demand exceeds the system capacity.- This solution is not scalable, as it requires manual intervention to add more instances. It also does not address the scalability of the backend, which is the main bottleneck.B. Place the frontend EC2 instances into an Auto Scaling group. Create an Auto Scaling policy to launch new instances to handle the incoming network traffic.- This solution only addresses the scalability of the frontend, but does not address the scalability of the backend, which is the main bottleneck.C. Place the frontend EC2 instances into an Auto Scaling group. Add an Amazon ElastiCache cluster in front of the ALB to reduce the amount of traffic the API needs to handle.- This solution may help reduce the load on the frontend, but it does not address the scalability of the backend, which is the main bottleneck.D. Place the frontend and backend EC2 instances into separate Auto Scaling groups. Create a policy for the frontend Auto Scaling group to launch instances based on incoming network traffic. Create a policy for the backend Auto Scaling group to launch instances based the SQS queue backlog.- This is the correct solution. By placing the frontend and backend instances into separate Auto Scaling groups, you can scale them independently based on their specific requirements. The frontend can scale based on incoming network traffic, while the backend can scale based on the SQS queue backlog, ensuring that the backend can handle the increased load during the product launch event.In summary, the correct solution is option D, which uses separate Auto Scaling groups for the frontend and backend instances, with scaling policies tailored to their specific requirements.