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

A company needs to migrate its critical SAP workloads from an on-premises data center to AWS. The company has a few source production databases that are 10 TB or more in size. The company wants to minimize the downtime for this migration.
As part of the proof of concept, the company used a low-speed, high-latency connection between its data center and AWS. During the actual migration, the company wants to maintain a consistent connection that delivers high bandwidth and low latency. The company also wants to add a layer of connectivity resiliency. The backup connectivity does not need to be as fast as the primary connectivity.
An SAP solutions architect needs to determine the optimal network configuration for data transfer. The solution must transfer the data with minimum latency.
Which configuration will meet these requirements?

Answer options

• A. Set up one AWS Direct Connect connection for connectivity between the on-premises data center and AWS. Add an AWS Site-to-Site VPN connection as a backup to the Direct Connect connection.
• B. Set up an AWS Direct Connect gateway with multiple Direct Connect connections that use a link aggregation group (LAG) between the on-premises data center and AWS.
• C. Set up Amazon Elastic File System (Amazon EFS) file system storage between the on-premises data center and AWS. Configure a cron job to copy the data into this EFS mount. Access the data in the EFS file system from the target environment.
• D. Set up two redundant AWS Site-to-Site VPN connections for connectivity between the on-premises data center and AWS.

Correct answer: A

Explanation

Option A is the best solution as it provides a dedicated AWS Direct Connect link for high bandwidth and low latency, along with a backup AWS Site-to-Site VPN for added resiliency. Option B, while potentially offering high throughput, does not specifically address the need for a backup connection. Option C does not meet the requirement for low latency during migration since it relies on cron jobs for data transfer. Option D offers redundancy but lacks the high performance required for critical SAP workloads.