AWS Certified SAP on AWS – Specialty (PAS-C01) — Question 122

A company is running SAP ERP Central Component (SAP ECC) on SAP HANA on premises. The current landscape runs on four application servers that use an SAP HANA database. The company is migrating this environment to the AWS Cloud. The cloud environment must minimize downtime during business operations and must not allow inbound access from the internet.

Which solution will meet these requirements?

Answer options

• A. Design a Multi-AZ solution. In each Availability Zone, create a private subnet where Amazon EC2 instances that host the SAP HANA database and the application servers will reside. Use EC2 instances that are the same size to host the primary database and the secondary database. Use SAP HANA system replication in synchronous replication mode.
• B. Design a Single-AZ solution. Create a private subnet where a single SAP HANA database and application servers will run on Amazon EC2 instances.
• C. Design a Multi-AZ solution. In each Availability Zone, create a private subnet where Amazon EC2 instances that host the SAP HANA database and the application servers will reside. Shut down the EC2 instance that runs the secondary database node. Turn on this EC2 instance only when the primary database node or the primary database node's underlying EC2 instance is unavailable.
• D. Design a Single-AZ solution. Create two public subnets where Amazon EC2 instances that host the SAP HANA database and the application servers will reside as two separate instances. Use EC2 instances that are the same size to host the primary database and the secondary database. Use SAP HANA system replication in synchronous replication mode.

Correct answer: A

Explanation

Option A is correct because it establishes a Multi-AZ solution, ensuring high availability and minimizing downtime while keeping the architecture private and secure from internet access. Option B does not provide redundancy, which is essential for minimizing downtime. Option C is incorrect because it only activates the secondary database on failure, which does not align with minimizing downtime. Option D fails to meet the requirement of private subnets and introduces unnecessary public access.