A company needs to implement high availability for its SAP S/4HANA system on AWS. The company will use a SUSE Linux Enterprise Server clustering solution in private subnets across two Availability…

Question

Options

• AImplement the SAP cluster solution by using a secondary private IP address. Reassign the
• BImplement the SAP cluster solution by using an Elastic IP address. Mask the failure of an instance
• CImplement the SAP cluster solution by using a public IP address. Use this public IP address for
• DImplement the SAP cluster solution by using an overlay IP address that is outside the CIDR block

• A
  16% (6)
• B
  8% (3)
• C
  5% (2)
• D
  71% (27)

Explanation

When clustering SAP across multiple Availability Zones in private subnets, the standard AWS approach is to use an overlay IP address-an IP address that falls outside the VPC CIDR block. A route table entry points this overlay IP at the active cluster node's Elastic Network Interface. When a failover occurs, the cluster software updates the route table entry to redirect the overlay IP to the new active node. This is the AWS-recommended pattern for SAP HA clustering across AZs. Option A (secondary private IP reassignment) is limited to within a single subnet/AZ and does not span AZs reliably. Option B (Elastic IP) is a public IP and does not work in private subnets. Option C (public IP) contradicts the private subnet requirement and is a security concern.

No community discussion yet for this question.