A company hosts a secure financial transaction processing service on Amazon EC2 instances managed by an Auto Scaling group (ASG). The instances are registered with a target group for an Application Load Balancer (ALB). The application listens on port 8443. However, due to security compliance, the application health check endpoint runs on a separate administrative service on port 8080 on the same instances. The target group is configured with the port set to 8443, and the health check port is set to the default 'traffic-port'. The EC2 instances are in private subnets, while the ALB is in public subnets. Custom Network ACLs (NACLs) are applied to both subnets. The security groups are configured to allow port 8443 and port 8080 inbound from the ALB security group, and outbound security groups are configured to allow all traffic. After deployment, the ALB marks all targets as unhealthy, and the ASG begins continuously terminating and replacing the instances. Which combination of actions will resolve this issue? (Select two.)
- Modify the target group's health check configuration to explicitly set the health check port to 8080.Cevap
- Add an outbound rule to the private subnet's Network ACL allowing traffic to the public subnets on ephemeral ports (1024-65535).Cevap
- CChange the target group port configuration to 8080 and keep the health check port set to the default traffic-port.
- DModify the security group of the EC2 instances to allow outbound traffic to the ALB security group on ephemeral ports (1024-65535).
- EConfigure a Route 53 latency routing policy with target health evaluation enabled pointing directly to the private IP addresses of the EC2 instances.