PAS-C01 · Question #114
A global retail company has SAP Fiori embedded with SAP S/4HANA Finance application servers that run in a private subnet in a dedicated SAP VPC on AWS. The database tier runs on SAP HANA, which reside
The correct answer is D. Install an SAP Web Dispatcher in the public subnet.. SAP Web Dispatcher is the SAP-native reverse proxy component designed specifically to handle HTTP/HTTPS traffic routing, URL redirecting, filtering, and rewriting for SAP web applications. To receive inbound traffic from the public internet, the Web Dispatcher must reside in a pu
Question
A global retail company has SAP Fiori embedded with SAP S/4HANA Finance application servers that run in a private subnet in a dedicated SAP VPC on AWS. The database tier runs on SAP HANA, which resides in the same private subnet. The company has deployed a Network Load Balancer (NLB) in a public subnet. The company has configured the NLB to send user traffic from outside the AWS network to the SAP application servers directly. An SAP solutions architect needs to expose the user interface (UI) layer's web services for remote access through a public internet web application. The application will handle cross- domain requests such as URL redirecting, filtering, and rewriting. The whole architecture will be distributed across multiple Availability Zones with hot standby for SAP HANA database components and SAP application components. The existing NLB will work as is. During failover, the NLB will redirect user traffic to the secondary Availability Zone after SAP is installed and running. How can the SAP solutions architect securely implement a connection between the UI layer's web services and the SAP application?
Options
- AUse the NLB and Amazon Route 53 to send the encrypted traffic from the internet directly to the
- BInstall an SAP Web Dispatcher with no public IP address in the same private subnet as the SAP
- CInstall a third-party tool that can consume web services and the objects that contain business logic.
- DInstall an SAP Web Dispatcher in the public subnet.
How the community answered
(24 responses)- A4% (1)
- B4% (1)
- C13% (3)
- D79% (19)
Explanation
SAP Web Dispatcher is the SAP-native reverse proxy component designed specifically to handle HTTP/HTTPS traffic routing, URL redirecting, filtering, and rewriting for SAP web applications. To receive inbound traffic from the public internet, the Web Dispatcher must reside in a public subnet with a public IP address (or behind a load balancer in a public subnet). Option A is incorrect because an NLB routes TCP traffic directly to the backend application servers without providing the application-layer (Layer 7) capabilities like URL rewriting and cross-domain request handling that the question requires. Option B is wrong because a Web Dispatcher in a private subnet with no public IP cannot be reached directly from the internet. Option C introduces unnecessary complexity with a third-party tool when SAP Web Dispatcher is the purpose-built, supported solution. Placing the SAP Web Dispatcher in the public subnet allows it to front the application servers in the private subnet, provides the required web service and cross-domain capabilities, and supports multi-AZ deployment for high availability.
Topics
Community Discussion
No community discussion yet for this question.