A company wants to implement SAP HANA on AWS with the Multi-AZ deployment option by using AWS Launch Wizard for SAP. The solution will use SUSE Linux Enterprise High Availability Extension for the hig

Question

Options

• ABefore starting the Launch Wizard deployment, create the underlying Amazon Elastic Block Store
• BUse a value for the PaceMakerTag parameter that is not used by any other Amazon EC2
• CEnsure that the virtual hostname for the SAP HANA database that is used for the SUSE Linux
• DEnsure that the VirtuallPAddress parameter is outside the VPC CIDR and is not being used in the
• EBefore starting the Launch Wizard deployment, set up the SUSE Linux Enterprise High Availability

• A
  10% (2)
• B
  70% (14)
• C
  15% (3)
• E
  5% (1)

Explanation

For a SUSE Linux Enterprise High Availability Extension deployment using AWS Launch Wizard for SAP in Multi-AZ mode, two specific inputs must be correctly configured. Answer B: The PaceMakerTag parameter must be a unique EC2 resource tag value not used by any other instance in the account. Pacemaker uses this tag to identify cluster nodes via AWS APIs; if the tag is shared, Pacemaker may incorrectly target or fail to target the right instances during failover. Answer D: The VirtualIPAddress (overlay IP) must be an IP address that falls outside the VPC CIDR range and is not already in use. This is because the overlay IP is implemented as an entry in the VPC route table pointing to the active node's ENI; for this routing to work correctly, the IP must not conflict with VPC-internal addressing. Answer A is incorrect-Launch Wizard creates EBS volumes automatically. Answer C is incorrect-the virtual hostname requirements for SUSE HA relate to DNS and should resolve to the overlay IP, not a specific value format enforced by Launch Wizard. Answer E is incorrect-Launch Wizard sets up the HA extension as part of the automated deployment.

No community discussion yet for this question.