A company hosts a latency-sensitive API on Amazon EC2 instances managed by an Auto Scaling group (ASG) behind an Application Load Balancer (ALB). The API processes user transactions on TCP port 8443. A separate monitoring agent on each instance listens on TCP port 9999 to report service health metrics. The ALB's target group is configured to perform health checks on port 9999. The subnet's stateless Network Access Control List (NACL) allows inbound TCP traffic on port 8443 from all sources and allows all outbound traffic.
To meet security compliance, a security engineer modifies the subnet NACL's outbound rule to only allow outbound TCP traffic to port 8443. Immediately after this change, the ALB marks all instances in the target group as unhealthy. Furthermore, Route 53, which is configured with latency-based routing policies to distribute traffic between this Region and another active Region, continues to send client requests to the unhealthy ALB.
Which combination of actions will restore the target health status and ensure Route 53 diverts traffic away from this Region during a failure? (Select two.)
- Modify the subnet Network ACLs to allow inbound TCP traffic on port 9999 and outbound TCP traffic to ephemeral ports (1024-65535).Cevap
- Configure 'Evaluate Target Health' to Yes on the Route 53 alias records that point to the Application Load Balancer.Cevap
- CChange the target group health check port to use the default traffic port (8443) and modify the subnet Network ACLs to allow inbound TCP traffic on port 8443.
- DAdd an outbound rule to the EC2 instances' security group allowing TCP traffic on port 9999, and configure the target group health check to use the default traffic port.
- EReplace the Route 53 latency-based routing policies with failover routing policies, as latency routing does not support health checking or automatic failover.