Topic 1 Question 87
2 つ選択You want to migrate an on-premises 100 TB Microsoft SQL Server database to Google Cloud over a 1 Gbps network link. You have 48 hours allowed downtime to migrate this database. What should you do?
Use a change data capture (CDC) migration strategy.
Move the physical database servers from on-premises to Google Cloud.
Keep the network bandwidth at 1 Gbps, and then perform an offline data migration.
Increase the network bandwidth to 2 Gbps, and then perform an offline data migration.
Increase the network bandwidth to 10 Gbps, and then perform an offline data migration.
ユーザの投票
コメント(4)
AUse a change data capture ***** (CDC) migration strategy.
BMove the physical database servers from on-premises to Google Cloud.
CKeep the network bandwidth at 1 Gbps, and then perform an offline data migration. 1 Gbps = 12460*60/8 = 10,800 GB = 10 TB per 24 hrs So, 20 TB per 48 hrs DIncrease the network bandwidth to 2 Gbps, and then perform an offline data migration. So, 40 TB per 48 hrs EIncrease the network bandwidth to 10 ***** Gbps, and then perform an offline data migration. So, 200 TB per 48 hrs Answer: A E
👍 3pk3492022/12/24- 正解だと思う選択肢: AE
I confirm pk349 calculations
👍 2chelbsik2022/12/25 A, E. According to Google’s data transfer chart, 100 TB across a 1 Gbps link would take 12 days. I don’t think you can physically move your own equipment into a Google DC. Eliminate B. Increasing the bandwidth to 2 Gbps and doing an offline migration anyway wouldn’t help. The Google Transfer Appliance comes in 7 TB, 40 TB and 300 TB sizes. However, the turnaround time (Google ships the appliance to you, you load it with data, you ship it back, Google unloads it to a Cloud Storage bucket) is approximately 3 weeks. Eliminate C and D. That leaves A and E. A 10 Gbps link would transfer 100 TB in 30 hours. That leaves 18 hours for a CDC solution to sync the data. https://cloud.google.com/architecture/migration-to-google-cloud-transferring-your-large-datasets#online_versus_offline_transfer
👍 2dynamic_dba2023/03/14
シャッフルモード