Free Amazon ANS-C01 Actual Exam Questions - Question 13 Discussion
subnets in three Availability Zones behind an Application Load Balancer (ALB). Security auditors
require encryption of all connections. The company uses Amazon Route 53 for DNS and uses AWS
Certificate Manager (ACM) to automate SSL/TLS certificate provisioning. SSL/TLS connections are
terminated on the ALB.
The company tests the application with a single EC2 instance and does not observe any problems.
However, after production deployment, users report that they can log in but that they cannot use the
application. Every new web request restarts the login process.
What should a network engineer do to resolve this issue?
It’s C, app-based cookies give more control over session persistence than group-level stickiness.
Probably C, app-based cookies handle session persistence better with ALB.
It’s A. The issue looks like session persistence isn’t set on the ALB listener rule, so enabling group-level stickiness there makes sure users hit the same instance throughout their session.
A imo, since the session issue points to stickiness not being enabled properly. The problem is that the load balancer isn’t consistently sending requests to the same instance, so enabling group-level stickiness on the ALB listener rule would help keep the session intact without relying on app cookies. Option C’s cookie-based stickiness depends on the app setting cookies correctly, which might not be guaranteed. This way, the ALB itself manages session persistence for the whole group, fixing the repeated login problem more directly.
Maybe C makes the most sense here. The problem seems to be that the session isn’t sticking to the same EC2 instance, which is why every new request restarts the login. Enabling stickiness at the target group level with an application-based cookie would keep users bound to one instance. Option A talks about stickiness on the ALB listener rule, which isn’t really how session affinity works with ALBs. D and B seem off since removing the ALB or switching to a Network Load Balancer complicates things unnecessarily. Stickiness at the target group with cookies fits best for web apps needing session p
A/C? Both mention enabling stickiness, but A talks about group-level stickiness on the ALB listener rule, while C focuses on target group stickiness with an app-based cookie. Since the app probably needs consistent backend session handling, C seems more precise.
Is the application using session cookies that depend on sticky sessions? Because the issue sounds like requests aren’t consistently hitting the same instance, causing logouts.