An energy utility provider is migrating its historical meter telemetry data archive of 450… — Google Cloud Professional Cloud Architect

An energy utility provider is migrating its historical meter telemetry data archive of $450\text{ TB}$ and an operational $2\text{ TB}$ relational database from an on-premises data center to Google Cloud. The facility has a dedicated $100\text{ Mbps}$ internet uplink available for the migration process, and business requirements specify that all data must be transferred within a $30\text{ day}$ window with minimal disruption to ongoing database transactions. Which data transfer strategy best satisfies these technical and operational constraints?

Order a Google Cloud Transfer Appliance to transfer the $450\text{ TB}$ telemetry archive offline, and use Database Migration Service (DMS) with continuous replication over a dedicated network connection for the operational database.Answer
B
Use Storage Transfer Service over the existing $100\text{ Mbps}$ internet uplink to move both the $450\text{ TB}$ telemetry archive and the $2\text{ TB}$ database files directly into Cloud Storage buckets.
C
Migrate the operational database to Cloud Spanner and use Cloud VPN over the internet link to stream the $450\text{ TB}$ archive using parallel gsutil uploads.
D
Establish a single HA VPN tunnel to stream the $450\text{ TB}$ telemetry archive while using VPC Network Peering to directly copy database snapshots to target subnets.

Answer

Order a Google Cloud Transfer Appliance for the

450\text{ TB}

telemetry archive and use Database Migration Service (DMS) for the

2\text{ TB}

operational database.

The correct strategy combines Transfer Appliance for the static

450\text{ TB}

dataset with Database Migration Service (DMS) for the

2\text{ TB}

database. Transferring

450\text{ TB}

over a

100\text{ Mbps}

network line requires over 400 days, making online transfer impossible within the 30-day requirement. Transfer Appliance bypasses this network bottleneck by physically shipping high-capacity hardware. Meanwhile, DMS supports continuous change data capture for the active operational database to minimize cutover downtime.

Step-by-Step Solution

Calculate the theoretical minimum transfer time for the

450\text{ TB}

dataset over the available network bandwidth.

100\text{ Mbps}

(

12.5\text{ MB/s}

), transferring

450\text{ TB}

(

450,000\text{ GB}

) requires

\frac{450,000 \times 10^9 \text{ bytes}}{12.5 \times 10^6 \text{ bytes/sec}} \approx 36,000,000\text{ seconds} \approx 416\text{ days}

An online transfer exceeds the 30-day window, mandating an offline physical transfer option.

Select the appropriate Google Cloud offline transfer service for the large static dataset.

Transfer Appliance allows shipping high-capacity physical appliances to ingest the

450\text{ TB}

data locally and upload it to Cloud Storage within days.

Offline transfer bypasses network bandwidth bottlenecks completely.

Select the online migration method for the dynamic

2\text{ TB}

database workload.

Database Migration Service (DMS) performs an initial backfill followed by continuous change data capture (CDC) replication over the network.

DMS enables minimal downtime cutover for active relational database workloads.

Key Concept

Selecting data transfer tools based on bandwidth math and workload state (offline physical transfer for petabyte/terabyte-scale static data over limited links vs. continuous replication for databases).

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics