PAS-C01 · Question #104
A global retail company is running its SAP landscape on AWS. Recently, the company made changes to its SAP Web Dispatcher architecture. The company added an additional SAP Web Dispatcher for high avai
The correct answer is B. Maintain persistence by using session cookies. Enable session stickiness (session affinity) on the. SAP applications are stateful: once a user logs in through one SAP Web Dispatcher, all subsequent requests for that session must reach the same application server instance to maintain session context. When an ALB distributes requests across two Web Dispatchers without session aff
Question
A global retail company is running its SAP landscape on AWS. Recently, the company made changes to its SAP Web Dispatcher architecture. The company added an additional SAP Web Dispatcher for high availability with an Application Load Balancer (ALB) to balance the load between the two SAP Web Dispatchers. When users try to access SAP through the ALB, the system is reachable. However, the SAP backend system is showing an error message. An investigation reveals that the issue is related to SAP session handling and distribution of requests. The company confirmed that the system was working as expected with one SAP Web Dispatcher. The company replicated the configuration of that SAP Web Dispatcher to the new SAP Web Dispatcher. How can the company resolve the error?
Options
- AMaintain persistence by using session cookies. Enable session stickiness (session affinity) on the
- BMaintain persistence by using session cookies. Enable session stickiness (session affinity) on the
- CTurn on host-based routing on the ALB to route traffic between the SAP Web Dispatchers.
- DTurn on URL-based routing on the ALB to route traffic to the application based on URL.
How the community answered
(34 responses)- A15% (5)
- B74% (25)
- C9% (3)
- D3% (1)
Explanation
SAP applications are stateful: once a user logs in through one SAP Web Dispatcher, all subsequent requests for that session must reach the same application server instance to maintain session context. When an ALB distributes requests across two Web Dispatchers without session affinity, a user's subsequent requests can be sent to the other Web Dispatcher, which has no knowledge of the established session, causing errors. The fix is to enable sticky sessions (session affinity) on the ALB target group so that all requests from a given client are consistently routed to the same Web Dispatcher. Option B correctly enables stickiness at the target group level, which is the proper AWS configuration point. Option A likely enables stickiness at the wrong scope or with an incorrect configuration. Host-based (C) or URL-based (D) routing does not address session persistence.
Topics
Community Discussion
No community discussion yet for this question.