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?…

Question

Options

• 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.
• DIncrease the network bandwidth to 2 Gbps, and then perform an offline data migration.
• EIncrease the network bandwidth to 10 Gbps, and then perform an offline data migration.

• A
  82% (18)
• B
  5% (1)
• C
  5% (1)
• D
  9% (2)

Explanation

A pure offline migration of 100 TB at 1 Gbps would take approximately 222 hours (100 TB × 1,024 GB/TB × 8 bits/byte ÷ 1,000,000,000 bits/sec ≈ 819,200 seconds), far exceeding the 48-hour window. At 10 Gbps, the same transfer takes approximately 22 hours, which fits comfortably within 48 hours - making Option E (increase bandwidth to 10 Gbps + offline migration) viable. Option A (Change Data Capture / CDC) is also correct because using CDC allows the bulk of the data to be migrated while the source system remains online, with only the incremental changes replayed during a short cutover window, minimizing downtime regardless of network speed. Options C and D fail the math test: 1 Gbps takes ~222 hours and 2 Gbps takes ~111 hours - both exceed 48 hours. Option B (moving physical servers) is impractical and not a cloud migration strategy.

No community discussion yet for this question.