Which solution will meet these requirements?
Use a NAT gateway to manage web traffic. Use Amazon EC2 Auto Scaling groups to receive, process, and store processed customer orders. Use an AWS Lambda function to capture and store unprocessed orders.
Use a Network Load Balancer (NLB) to manage web traffic. Use an Application Load Balancer to receive customer orders from the NLUse Amazon Redshift with a Multi-AZ deployment to store unprocessed and processed customer orders.
Use a Gateway Load Balancer (GWLB) to manage web traffic. Use Amazon Elastic Container Service (Amazon ECS) to receive and process customer orders. Use the GWLB to capture and store unprocessed orders. Use Amazon DynamoDB to store processed customer orders.
Use an Application Load Balancer to manage web traffic. Use Amazon EC2 Auto Scaling groups to receive and process customer orders. Use Amazon Simple Queue Service (Amazon SQS) to store unprocessed orders. Use Amazon RDS with a Multi-AZ deployment to store processed customer orders.
Explanations:
While this option mentions using EC2 Auto Scaling to manage web traffic and capture unprocessed orders with Lambda, it lacks a direct method for efficiently handling web traffic as a load balancer would. NAT gateways are primarily for network address translation and do not manage traffic at the application layer, making this solution less suitable for high-traffic scenarios.
This option suggests using a Network Load Balancer (NLB) to manage web traffic, which is designed for TCP traffic rather than HTTP. It also proposes using Amazon Redshift, a data warehouse service, which is not suited for transactional order processing. Thus, it does not adequately meet the requirements of processing customer orders in a resilient and scalable way.
This option proposes using a Gateway Load Balancer (GWLB) to manage web traffic, but GWLB is primarily intended for distributing traffic to security appliances rather than for general web application traffic management. Additionally, it suggests capturing unprocessed orders with the GWLB, which is not a suitable method for handling application-level processing needs.
This option uses an Application Load Balancer to effectively manage web traffic, ensuring it can scale with demand. It employs Amazon EC2 Auto Scaling to dynamically adjust processing capacity based on traffic. Amazon SQS is used for handling unprocessed orders reliably, ensuring no orders are lost during peak traffic. Finally, Amazon RDS with a Multi-AZ deployment offers a resilient solution for storing processed customer orders, providing high availability and durability.
I classify that the answer is:
Use an Application Load Balancer to manage web traffic. Use Amazon EC2 Auto Scaling groups to receive and process customer orders. Use Amazon Simple Queue Service (Amazon SQS) to store unprocessed orders. Use Amazon RDS with a Multi-AZ deployment to store processed customer orders.