An SAP technical architect is working on a high availability setup of an SAP application that is running on an SAP HANA database in the AWS Cloud. Primary and secondary SAP HANA databases are…

Question

Options

• ADetermine whether the SAP HANA instances have an assigned public IP address.
• BChange the VPC CIDR range to 10.0.0.0/8 to accommodate the overlay IP address assignment.
• CUse a different overlay IP address that is outside the VPC CIDR range for the SAP HANA cluster.
• DConfigure SAP HANA system replication after the cluster setup is complete.

• A
  20% (12)
• B
  5% (3)
• C
  66% (40)
• D
  10% (6)

Explanation

In AWS high-availability clustering for SAP (using Pacemaker/SUSE HA Extension), overlay IP addresses work by injecting a host route into the VPC routing tables via a custom resource agent script. For this mechanism to function correctly, the overlay IP address MUST fall outside the VPC CIDR range. The VPC CIDR is 10.0.0.0/16, which covers addresses 10.0.0.0 through 10.0.255.255. The SAP HANA cluster overlay IP of 10.0.9.9 falls within this range, which causes a conflict - AWS will try to route it through normal VPC routing rather than allowing the cluster agent to control it. The ASCS/ERS overlay IP of 10.9.9.9 is correctly outside the VPC CIDR. Option A (public IP) is irrelevant to clustering. Option B is unnecessary and disruptive. Option D is incorrect because system replication is already configured - the cluster mechanism is the problem, not replication.

No community discussion yet for this question.