Which combination of actions should a SysOps administrator take to resolve the logout problem?
(Choose two.)
Change to the least outstanding requests algorithm on the ALB target group.
Configure cookie forwarding in the CloudFront distribution’s cache behavior settings.
Configure the duration-based cookie to be named AWSALB.
Configure the ALB to use the expiration cookie header.
Change the ALB to use application-based cookies.
Explanations:
Changing to the least outstanding requests algorithm does not directly address the issue of forced logouts. The logout problem is likely related to session management rather than load balancing algorithm.
Configuring cookie forwarding in the CloudFront distribution allows the application cookies to be forwarded to the backend instances. This ensures that session information is preserved across multiple requests and prevents forced logouts.
Renaming the duration-based cookie to AWSALB does not resolve the logout issue. The name of the cookie is not the primary factor in maintaining session persistence; it is the configuration of session management that matters.
Configuring the ALB to use the expiration cookie header is not necessary for resolving the logout problem. The existing configuration of sticky sessions should already manage session persistence without this adjustment.
Changing the ALB to use application-based cookies can help manage sessions more effectively, especially if the application is generating its own cookies. This approach provides better control over session management and prevents unintended logouts.
I gauge that the answer is:
Configure cookie forwarding in the CloudFront distribution’s cache behavior settings.