An enterprise application uses a proprietary TCP-based protocol to process transactions. The application runs on Amazon EC2 instances within private subnets, managed by an Auto Scaling group (ASG) behind a Network Load Balancer (NLB). The application daemon listens on TCP port 7001 for transaction traffic, while a separate monitoring service on the same instances listens on TCP port 7005 to report health status. Currently, the NLB target group is configured to use the TCP protocol, with the health check port set to 'traffic-port'. The target group health checks are failing, causing the NLB to mark all instances as unhealthy and prevent transaction routing. The Security Group assigned to the EC2 instances permits inbound TCP traffic on ports 7001 and 7005 from the VPC CIDR. The subnets use a custom Network Access Control List (NACL) that permits inbound TCP traffic on ports 7001 and 7005 from the VPC CIDR, but contains no outbound rules other than the default deny rule. Which combination of actions should a Solutions Architect take to resolve the health check failure and allow transactions to flow? (Select two.)
- Update the target group configuration to specify port 7005 as the health check port instead of using the traffic port.Cevap
- Add an outbound rule to the subnet's Network ACL allowing TCP traffic to the ephemeral port range (1024–65535) to handle return traffic.Cevap
- CAdd an outbound rule to the EC2 instances' security group allowing TCP traffic to the ephemeral port range (1024–65535) to the VPC CIDR.
- DChange the target group protocol to HTTP and set the health check path to /health on port 7005.
- EConfigure a Route 53 latency routing policy to route traffic directly to the private IP addresses of the EC2 instances in the Auto Scaling group.