PAS-C01 · Question #100
A company is planning to lift and shift its on-premises SAP Business Suite on SAP HANA workload to AWS. The production database is 15 TB in size. The downtime for production migration is limited to a
The correct answer is D. Use an AWS Direct Connect connection during migration.. Migrating a 15 TB SAP HANA database via system replication requires sustained high bandwidth and a stable, low-latency network connection - AWS Direct Connect is the right choice for this phase because it provides dedicated bandwidth (avoiding internet congestion) that can suppor
Question
A company is planning to lift and shift its on-premises SAP Business Suite on SAP HANA workload to AWS. The production database is 15 TB in size. The downtime for production migration is limited to a few hours. The company will use SAP HANA system replication to migrate the SAP HANA database. After migration to AWS, the company's remote workforce and business partners need to connect to this SAP Business Suite on SAP HANA instance with an internet connection and an OpenVPN- compatible client in a secure way. Which connectivity solution will meet these requirements?
Options
- AUse a direct internet connection with a single public subnet and an internet gateway during and
- BUse an AWS Site-to-Site VPN connection during migration.
- CUse an AWS Direct Connect connection during migration.
- DUse an AWS Direct Connect connection during migration.
How the community answered
(23 responses)- A9% (2)
- B4% (1)
- C4% (1)
- D83% (19)
Explanation
Migrating a 15 TB SAP HANA database via system replication requires sustained high bandwidth and a stable, low-latency network connection - AWS Direct Connect is the right choice for this phase because it provides dedicated bandwidth (avoiding internet congestion) that can support the initial data load and ongoing log shipping within the limited downtime window. After migration, the requirement is secure access for remote workers and business partners using an OpenVPN-compatible client. AWS Client VPN is built on the OpenVPN protocol, making it directly compatible. Option D combines Direct Connect for the migration phase with AWS Client VPN for ongoing user access. A public subnet with an internet gateway (A) is insecure. Site-to-Site VPN (B) is for network-to-network connectivity, not individual client access, and has lower bandwidth limits than Direct Connect for a 15 TB transfer.
Topics
Community Discussion
No community discussion yet for this question.