New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Amazon PAS-C01 Exam - Topic 4 Question 38 Discussion

Actual exam question for Amazon's PAS-C01 exam
Question #: 38
Topic #: 4
[All PAS-C01 Questions]

A company is running an SAP on Oracle system on IBM Power architecture in an on-premises data center. The company wants to migrate the SAP system to AWS. The Oracle database is 15 TB n size The company has set up a 100 Gbps AWS Direct Connect connection to AWS from the on-premises data center.

Which solution should the company use to migrate the SAP system MOST quickly?

Show Suggested Answer Hide Answer
Suggested Answer: B

Snowball Edge allows for offline data transfer, which is suitable for cases where there is slow and inconsistent internet connectivity. The data can be transferred to the Snowball Edge device, shipped to the AWS region, and then imported into the new SAP HANA system in the VPC. This is a suitable option for migrating large amounts of data from a remote location to AWS.

https://docs.aws.amazon.com/sap/latest/sap-hana/migrating-hana-tools.html#migrating-hana-snowball


by Ryan at Jul 05, 2024, 05:00 AM

Limited Time Offer

25%

Off

Get Premium PAS-C01 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Eloisa
3 months ago
D? Really? Sounds like a lot of extra steps.
upvoted 0 times
...
Alecia
3 months ago
C sounds complicated, not sure about that one.
upvoted 0 times
...
Carey
3 months ago
Surprised they didn't mention using AWS Database Migration Service!
upvoted 0 times
...
Ahmed
4 months ago
I think B is better for minimizing downtime.
upvoted 0 times
...
Sophia
4 months ago
Option A seems the fastest, right?
upvoted 0 times
...
Edelmira
4 months ago
I have a vague recollection of AWS SMS from my studies. Option D seems interesting, but I'm not confident about using snapshots for such a large system.
upvoted 0 times
...
Valentine
4 months ago
I practiced a similar question where we had to consider network bandwidth. I think option A might be faster since it involves exporting and importing directly during the migration window.
upvoted 0 times
...
Gennie
4 months ago
I'm not entirely sure, but I feel like option C could be effective too. The Cross Platform Transportable Tablespace sounds familiar, but I worry about the complexity involved.
upvoted 0 times
...
Billi
5 months ago
I remember that for large databases like 15 TB, minimizing downtime is crucial. I think option B might be the best approach since it uses Oracle Data Guard for replication.
upvoted 0 times
...
Madalyn
5 months ago
This is a lot to take in, but I think I'd go with option A. Doing the full system export and import seems the most straightforward, even if it takes a bit longer. The heterogeneous system copy process is something I'm familiar with, so I feel confident I could execute that well.
upvoted 0 times
...
Madalyn
5 months ago
I'm leaning towards option D with the AWS SMS snapshots. That seems like the most automated approach, and the ability to quickly spin up a new SAP system from the latest snapshot could make the cutover really fast. I'll need to research AWS SMS a bit more, but that's my initial thought.
upvoted 0 times
...
Katina
5 months ago
Option C with the XTTS conversion seems promising. Doing the conversion in stages before the migration window could help speed things up. The incremental backups and conversions sound like a good way to keep the data up-to-date.
upvoted 0 times
...
Caitlin
5 months ago
I'm a bit confused by all the different steps in these options. I'll need to carefully read through each one to understand the differences and decide which one seems most efficient. The 100 Gbps Direct Connect connection is a big advantage, so that's something to consider.
upvoted 0 times
...
Jody
5 months ago
This looks like a pretty complex migration scenario, but I think option B might be the quickest approach. Replicating the database changes in real-time using Oracle Data Guard could help minimize downtime.
upvoted 0 times
...
Na
5 months ago
This looks like a straightforward question about the purpose of a specific line of code. I'll need to carefully read through the options and think about what that line of code is likely doing.
upvoted 0 times
...
Tiera
5 months ago
Hmm, I remember learning about IPv6 addressing, but I can't recall the exact number of bits used for the interface identifier. I'll have to think this through carefully.
upvoted 0 times
...
Gladys
5 months ago
Hmm, I'm a bit unsure on this one. I'll have to think it through carefully to make sure I don't mix up the different penetration testing stages.
upvoted 0 times
...
Bok
5 months ago
Accessing the internet? No way, that can't be it. I think it's gotta be changing settings in the Display Properties dialog box.
upvoted 0 times
...
Paris
9 months ago
I hope they have a good backup plan, because if they mess this up, they'll be in the doghouse faster than you can say 'SAP on AWS'.
upvoted 0 times
...
Georgeanna
9 months ago
This is like choosing between my favorite ice cream flavors. I'll have one of each, please!
upvoted 0 times
Nieves
8 months ago
D) Before the migration window launch an appropriately sized Amazon EC2 instance on AWS to receive the migrated SAP database. Create an AWS Server Migration Service (AWS SMS) job to take regular snapshots of the on-premises Oracle hosts. Use AWS SMS to copy the snapshot as an AMI to AWS through the Direct Connect connection. Create a new SAP on Oracle system by using the migrated AMI. During the migration window take a final incremental SMS snapshot and copy the snapshot to AWS. Restart the SAP system by using the new up-to-date AMI. Switch over to the SAP system on AWS
upvoted 0 times
...
Sylvie
8 months ago
C) Before the migration window build a new installation of the SAP system on AWS by using SAP Software Provisioning Manager. Create a staging Oracle database on premises to perform Cross Platform Transportable Tablespace (XTTS) conversion on the Oracle database. Take a backup of the converted staging database. Copy the converted backup to AWS through the Direct Connect connection import the Oracle database backup to the SAP system on AWS. Take regularly scheduled incremental backups and XTTS conversions of the staging database. Transfer these backups and conversions to the AWS target database. During the migration window, perform a final incremental Oracle backup. Convert the final Oracle backup by using XTTS. Replay the logs in the target Oracle database hosted on AWS. Switch over to the SAP system on AWS
upvoted 0 times
...
Kristal
9 months ago
B) Before the migration window build a new installation of the SAP system on AWS by using SAP Software Provisioning Manager. Back up the Oracle database by using native Oracle tools. Copy the backup of the Oracle database to AWS through the Direct Connect connection. Import the Oracle database to the SAP system on AWS. Configure Oracle Data Guard to begin replication on-premises database log changes from the SAP system to the new AWS system. During the migration window use Oracle to replicate any remaining changes to the Oracle database hosted on AWS. Switch over to the SAP system on AWS
upvoted 0 times
...
Dong
9 months ago
A) Before the migration window build a new installation of the SAP system on AWS by using SAP Software Provisioning Manager. During the migration window export a copy of the SAP system and database by using the heterogeneous system copy process and R3load. Copy the output of the SAP system files to AWS through the Direct Connect connection import the SAP system to the new SAP installation on AWS. Switch over to the SAP system on AWS
upvoted 0 times
...
...
Brinda
10 months ago
Wait, we have a 100 Gbps Direct Connect connection? I'm going with Option D - the AWS SMS solution seems the quickest and least disruptive.
upvoted 0 times
Margurite
9 months ago
Definitely, the 100 Gbps Direct Connect connection will make the migration process smoother with Option D.
upvoted 0 times
...
Sherly
10 months ago
I agree, using AWS SMS to migrate the SAP system seems like the least disruptive option.
upvoted 0 times
...
Catarina
10 months ago
Option D sounds like the best choice. The AWS SMS solution seems efficient.
upvoted 0 times
...
...
Eura
10 months ago
I'm not sure about the XTTS conversion process. Doesn't that require some downtime? Option B with Oracle Data Guard replication might be safer.
upvoted 0 times
...
Donette
10 months ago
Option C seems like the way to go. The XTTS conversion and incremental backups should ensure a smooth migration without any data loss.
upvoted 0 times
Francoise
10 months ago
Yes, the XTTS conversion and incremental backups definitely seem like they would help ensure a successful migration without any data loss.
upvoted 0 times
...
Nichelle
10 months ago
I agree, option C seems like the most thorough approach for migrating the SAP system to AWS.
upvoted 0 times
...
...
Golda
10 months ago
But option C involves XTTS conversions for faster migration, which could be beneficial.
upvoted 0 times
...
Corinne
10 months ago
I disagree, I believe option B is more efficient with Oracle Data Guard for replication.
upvoted 0 times
...
Golda
11 months ago
I think option A is the best solution for quick migration.
upvoted 0 times
...

Save Cancel