Exam AWS Certified SAP on AWS - Specialty PAS-C01 topic 1 question 2 discussion

B: "The company confirmed that the system was working as expected with one SAP Web Dispatcher." , so Web Dispatcher settings aren't the problem.

I think B

Must be B, the setting on webdispatcher affects how requests are distributed among the application servers - if the issue wasn't existing before, it must be connected to the multiple dispatchers setup. We must to make sure that once the user is connected to given dispatcher, it will remain so. B is the best answer then.

Option A seems to be correct. Maintaining persistence through session cookies and enabling session stickiness on the SAP Web Dispatchers seems like a reasonable approach to ensure that user sessions are consistently directed to the same backend server. The parameter wdisp/HTTP/esid_support set to True should help in achieving this.

Correct B.

Voting B

B. the ALB is splitting the traffic, so stickiness needs to be set in the ALB, setting it in the dispatcher seems pointless of the ALB is still splitting the traffic between different dispatchers...

A. The error message being displayed is related to SAP session handling and distribution of requests. By using session cookies, the company can maintain persistence of the user’s session across requests. By enabling session stickiness on the SAP Web Dispatchers by setting the wdisp/HTTP/esid_support parameter to True, the company can ensure that requests from the same user are always routed to the same SAP Web Dispatcher. This would resolve the error message that the company is seeing and ensure that the backend system is working as expected with the new SAP Web Dispatcher configuration.

A is correct. To resolve the error related to SAP session handling and distribution of requests when using an Application Load Balancer (ALB) to balance the load between two SAP Web Dispatchers, the company should maintain session stickiness (session affinity) by using session cookies. This will ensure that each user's session is directed to the same SAP Web Dispatcher that the initial request was directed to. Option A is the correct solution. The wdisp/HTTP/esid_support parameter is used to enable session stickiness on the SAP Web Dispatchers. By setting it to True, session information is maintained by the SAP Web Dispatcher in a session cookie. This cookie is then used to direct subsequent requests from the same user to the same SAP Web Dispatcher. Option B is incorrect because enabling session stickiness on the ALB would not be enough to ensure that session information is maintained when requests are directed to different SAP Web Dispatchers. Option C is incorrect because host-based routing would not address the issue of maintaining session information. Option D is incorrect because URL-based routing is not designed to maintain session information.

I think A. The issue is related to session stickness. Enabling wdisp/HTTP/esid_support you can maintain persistence of users session across requests.

A. https://help.sap.com/doc/saphelp_nw74/7.4.16/en-us/48/957c9194cc73eae10000000a42189b/content.htm?no_cache=true

I think its A, as the issue is in coming from SAP side?

I am also voting for B. There is a connection between ALB and the dispatchers, but user sessions won't be handle correctly, therefore causing an error.