An automotive telematics enterprise needs to migrate its platform to Google Cloud within a… — Google Cloud Professional Cloud Architect

An automotive telematics enterprise needs to migrate its platform to Google Cloud within a strict 10-day maintenance window. The existing environment consists of $800\text{ TB}$ of historical vehicle sensor log archives stored on an on-premises NAS and a $1.5\text{ TB}$ operational MySQL database. The enterprise has a dedicated $200\text{ Mbps}$ network uplink allocated for migration traffic. The solution must ensure minimal downtime for the live transaction database while completing the bulk historical data transfer within the 10-day constraint. Which migration strategy should the cloud architect recommend?

Order a Google Cloud Transfer Appliance to migrate the $800\text{ TB}$ historical sensor logs, and use Database Migration Service (DMS) with continuous replication for the $1.5\text{ TB}$ MySQL database.Answer
B
Use Storage Transfer Service over the $200\text{ Mbps}$ connection to transfer the $800\text{ TB}$ historical sensor logs, and use Database Migration Service (DMS) with continuous replication for the $1.5\text{ TB}$ MySQL database.
C
Provision an HA VPN tunnel to increase network throughput for transferring the $800\text{ TB}$ sensor logs via Storage Transfer Service, and export database dump files to Cloud Storage via Transfer Appliance.
D
Migrate the $1.5\text{ TB}$ MySQL database to Cloud Spanner using Database Migration Service, and stream the $800\text{ TB}$ sensor logs over the network using Storage Transfer Service.

Answer

Order a Google Cloud Transfer Appliance to migrate the

800\text{ TB}

historical sensor logs, and use Database Migration Service (DMS) with continuous replication for the

1.5\text{ TB}

MySQL database.

The optimal strategy pairs Transfer Appliance for the

800\text{ TB}

unstructured file archives with Database Migration Service (DMS) utilizing continuous CDC replication for the

1.5\text{ TB}

MySQL database. Transferring

800\text{ TB}

over a

200\text{ Mbps}

link requires approximately 370 days, making physical appliance shipping mandatory to achieve the 10-day deadline. Conversely, the

1.5\text{ TB}

database initial load requires approximately 16.6 hours over

200\text{ Mbps}

, allowing DMS to establish an online baseline and stream ongoing updates for a near-zero downtime cutover.

Step-by-Step Solution

Calculate data transfer time for the unstructured historical dataset over the available network uplink.

800\text{ TB} = 6.4 \times 10^{15}\text{ bits}

. At

200\text{ Mbps}

(

2 \times 10^8\text{ bps}

), transfer duration is

\frac{6.4 \times 10^{15}}{2 \times 10^8} = 32,000,000\text{ seconds} \approx 370\text{ days}

. Online network transfer is impossible within 10 days.

Large dataset scale (

800\text{ TB}

) under constrained bandwidth (

200\text{ Mbps}

) mandates an offline physical transfer appliance.

Evaluate network transfer feasibility for the

1.5\text{ TB}

relational database.

1.5\text{ TB} = 1.2 \times 10^{13}\text{ bits}

. At

200\text{ Mbps}

, initial bulk copy takes

\frac{1.2 \times 10^{13}}{2 \times 10^8} = 60,000\text{ seconds} \approx 16.6\text{ hours}

, which fits comfortably within the timeline.

The initial snapshot can load over the network in less than a day, followed by continuous Change Data Capture (CDC) replication.

Synthesize the optimal hybrid migration plan.

Ship an offline Transfer Appliance for the

800\text{ TB}

file archives while running Database Migration Service with CDC for the

1.5\text{ TB}

MySQL database.

This strategy satisfies both the 10-day total window constraint and the minimal downtime requirement for the live transactional workload.

Key Concept

Selecting between online network transfer mechanisms and offline physical transport appliances based on bandwidth calculations, dataset scale, and database cutover constraints.

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics