An enterprise is migrating a stateful legacy web application to AWS. The application runs on Amazon EC2 instances managed by an Auto Scaling group (ASG) behind an Application Load Balancer (ALB). The application listens on custom port 8080. During testing under load, users experience session loss and are forced to log in repeatedly when the application scales. Additionally, during scale-in events, users whose requests are currently being processed experience immediate connection drops and HTTP 502/504 errors. The network and security teams require strict control over VPC boundaries using both security groups and Network ACLs (NACLs).
Which two actions should a solutions architect take to resolve the session issues and prevent request failures during scale-in? (Select two.)
- Enable sticky sessions (session affinity) on the Application Load Balancer target group using duration-based cookies.Cevap
- Configure a deregistration delay (connection draining) on the Application Load Balancer target group.Cevap
- CChange the target group's health check port to the default HTTP port 80 to prevent health check traffic from saturating the application on port 8080.
- DConfigure stateless Network ACLs on the instance subnets to allow inbound traffic on port 8080, relying on the stateful nature of security groups to permit outbound ephemeral port responses automatically.
- EImplement an Amazon Route 53 latency routing policy pointing directly to the EC2 instances' public IP addresses to bypass the ALB and enforce session persistence.