An SAP basis architect is configuring high availability for a critical SAP system on AWS. The SAP basis architect is using an overlay IP address to route traffic to the subnets across multiple Availab

Question

Options

• AEdit the route in the route table of the VPC that includes the EC2 instance that runs SAP
• BEdit the inbound and outbound rules in the security group of the EC2 instance that runs SAP
• CEdit the network ACL of the subnet that includes the EC2 instance that runs SAP HANA. Allow
• DEdit the route in the route table of the VPC that includes the EC2 instance that runs SAP HANA.

• A
  4% (1)
• B
  7% (2)
• C
  14% (4)
• D
  75% (21)

Explanation

In AWS, an overlay IP (virtual IP) used for SAP HANA high availability is a secondary IP address that is not directly assigned to any ENI. To route traffic to the active SAP HANA node, the VPC route table must contain a route that points the overlay IP address to the specific Elastic Network Interface (ENI) of the active EC2 instance. When a failover occurs, a cluster automation script updates this route table entry to point to the new active node's ENI. Security group rules (B) control allowed traffic but do not route traffic. Network ACLs (C) are stateless filters, not routing tools. The distinction between option A and D lies in pointing the route to the ENI specifically, which is the correct mechanism for overlay IP routing in AWS.

No community discussion yet for this question.