PAS-C01 · Question #121
A company is running its SAP workloads on premises and needs to migrate the workloads to AWS. All the workloads are running on SUSE Linux Enterprise Server and Oracle Database. The company's landscape
The correct answer is C. Use SAP Software Provisioning Manager to perform parallel export/import of the systems to. SAP Software Provisioning Manager (SWPM) with parallel export/import is the appropriate migration tool for heterogeneous migrations (different OS or database platform). Since the company is migrating from Oracle Database on SUSE Linux to AWS (potentially changing the database), t
Question
A company is running its SAP workloads on premises and needs to migrate the workloads to AWS. All the workloads are running on SUSE Linux Enterprise Server and Oracle Database. The company's landscape consists of SAP ERP Central Component (SAP ECC), SAP Business Warehouse (SAP BW), and SAP NetWeaver systems. The company has a dedicated AWS Direct Connect connection between its on-premises environment and AWS. The company needs to migrate the systems to AWS with the least possible downtime. Which migration solution will meet these requirements?
Options
- AUse SAP Software Provisioning Manager to perform an export of the systems. Copy the export to
- BUse SAP Software Provisioning Manager to perform parallel export/import of the systems to
- CUse SAP Software Provisioning Manager to perform parallel export/import of the systems to
- DUse SAP Software Provisioning Manager to perform an export of the systems. Copy the export to
How the community answered
(36 responses)- A11% (4)
- B3% (1)
- C83% (30)
- D3% (1)
Explanation
SAP Software Provisioning Manager (SWPM) with parallel export/import is the appropriate migration tool for heterogeneous migrations (different OS or database platform). Since the company is migrating from Oracle Database on SUSE Linux to AWS (potentially changing the database), the parallel export/import method splits the data export into multiple packages processed simultaneously, significantly reducing total migration time compared to sequential export. The use of the existing Direct Connect connection allows high-throughput data transfer directly to the AWS target environment without going through the public internet. Option A and D use sequential (non-parallel) export which takes longer. Option B is similar but the key differentiator for minimum downtime in this scenario is using parallel processing with the Direct Connect link to AWS directly, as described in option C.
Topics
Community Discussion
No community discussion yet for this question.