An enterprise is migrating a legacy customer management API to AWS. The API runs on a cluster of Amazon EC2 instances in a private subnet, configured to listen on port 8080. An Application Load Balancer (ALB) is deployed in public subnets to distribute incoming traffic. The application needs to dynamically scale based on demand while maintaining high availability. Traffic to the backend instances must be securely restricted, and the load balancer must accurately determine target health. Which two configurations should the solutions architect implement to satisfy these requirements? (Select two.)
- Configure the target group to route traffic to port 8080 and set the health check port to use the traffic port.Answer
- Configure the security group of the EC2 instances to allow inbound traffic on port 8080 from the security group of the Application Load Balancer.Answer
- CConfigure the target group health check to query the default port 80 to ensure the web server is listening, while routing main traffic to port 8080.
- DCreate a Network ACL on the private subnet that allows inbound traffic on port 8080 from the security group of the Application Load Balancer.
- EConfigure an Amazon Route 53 latency-based routing policy to direct client requests directly to the private EC2 instances to handle the scaling load.
Answer
To support an application running on port 8080, the target group must route traffic to port 8080 with the health check port matching the traffic port, and the EC2 instances' security group must allow inbound traffic on port 8080 from the security group of the Application Load Balancer.
To support an application running on port 8080, the target group must route traffic to port 8080 and its health checks must target the same port (or 'traffic-port') to ensure accurate status reporting. Additionally, to secure the architecture, the EC2 instances' security group should allow inbound traffic on port 8080 specifically from the security group of the Application Load Balancer.
Step-by-Step Solution
Key Concept
Integrating Elastic Load Balancing (ELB) with backend EC2 targets requires matching application ports for routing and health checks, and establishing secure path communications via security group chaining.
Estimated Time:2m 0s