A company wants to migrate its SAP ERP landscape to AWS. The company will use a highly available distributed deployment for the new architecture. Clients will access SAP systems from a local data cent

Question

Options

• AFor the ASCS instance, configure an overlay IP address that is within the production VPC CIDR
• BFor the ASCS instance, configure an overlay IP address that is outside the production VPC CIDR
• CFor the ASCS instance, configure an overlay IP address that is within the production VPC CIDR
• DFor the ASCS instance, configure an overlay IP address that is outside the production VPC CIDR
• EFor the ASCS instance, configure an overlay IP address that is outside the production VPC CIDR

• A
  23% (8)
• B
  60% (21)
• C
  11% (4)
• E
  6% (2)

Explanation

For SAP high-availability clusters on AWS, the overlay IP address used for the ASCS (ABAP Central Services) instance must be outside the production VPC CIDR range. This is a fundamental AWS networking requirement for the cluster failover mechanism: when a failover occurs, the Pacemaker resource agent updates the VPC route table to redirect traffic for the overlay IP to the current active node. If the overlay IP were within the VPC CIDR, AWS's native routing would interfere with this process and prevent correct failover routing. Options B and D both specify an overlay IP outside the VPC CIDR, satisfying this requirement, while differing in another configuration detail (not fully visible in the truncated options). Options A, C, and E specify overlay IPs within the VPC CIDR, which would cause the same type of clustering failure described in Question 2.

No community discussion yet for this question.