A smart energy grid company plans to migrate its legacy telemetry and management infrastru… — Google Cloud Professional Cloud Architect

A smart energy grid company plans to migrate its legacy telemetry and management infrastructure to Google Cloud within a strict 4-week window. The environment consists of $800\text{ TB}$ of historical meter reading archives stored on an on-premises NFS storage system and an active $12\text{ TB}$ transactional PostgreSQL database. The organization has an existing dedicated $1\text{ Gbps}$ network connection to Google Cloud, which is currently heavily utilized by business-critical operations. The business requires minimal downtime for the transactional database during cutover and must complete the entire static file migration within the 4-week timeframe. Which data transfer and migration strategy should you recommend?

Order a Google Cloud Transfer Appliance to physically transport the $800\text{ TB}$ of historical meter archives to Cloud Storage, and deploy Database Migration Service (DMS) with continuous Change Data Capture (CDC) over the existing network connection to replicate the PostgreSQL database prior to cutover.Cevap
B
Configure Storage Transfer Service with self-hosted transfer agents to stream the $800\text{ TB}$ of historical archives directly over the $1\text{ Gbps}$ network connection, and deploy Database Migration Service (DMS) for the PostgreSQL database.
C
Order a Google Cloud Transfer Appliance for the $800\text{ TB}$ historical archives, and migrate the PostgreSQL database by exporting full database dumps to Cloud Storage and loading them into Cloud Spanner during the cutover window.
D
Establish multiple high-throughput Cloud VPN tunnels in parallel to transfer the $800\text{ TB}$ static archives to Cloud Storage, and perform a manual database backup and restore procedure to Cloud SQL during cutover.

Cevap

Order a Google Cloud Transfer Appliance for the

800\text{ TB}

static archives and use Database Migration Service (DMS) with CDC for the PostgreSQL database.

The correct strategy combines Google Cloud Transfer Appliance for offline transfer of the

800\text{ TB}

historical archives and Database Migration Service (DMS) with continuous Change Data Capture (CDC) for the

12\text{ TB}

PostgreSQL database. Network calculations show that transferring

800\text{ TB}

over a

1\text{ Gbps}

link requires over 74 days, making online streaming impossible within the 4-week window. Transfer Appliance avoids network congestion and completes the bulk load on time. Meanwhile, DMS with CDC handles continuous database replication in the background, allowing a near-zero downtime cutover.

Adım Adım Çözüm

Calculate network bandwidth capacity for static data transfer

Streaming

800\text{ TB}

over

1\text{ Gbps}

takes

\frac{800 \times 10^{12} \times 8}{10^9} \approx 6.4 \times 10^6\text{ seconds} \approx 74\text{ days}

, exceeding the 4-week (28-day) constraint.

Large multi-hundred terabyte or petabyte dataset transfers over low or shared bandwidth links must use offline physical appliances to meet time limits.

Select the appropriate offline data transfer method

Google Cloud Transfer Appliance enables shipping

800\text{ TB}

of data securely within a few days without using network bandwidth.

Transfer Appliance bypasses network constraints and protects production traffic on the existing

1\text{ Gbps}

link.

Select the database migration pattern for minimal downtime

Database Migration Service (DMS) uses Change Data Capture (CDC) to perform an initial backfill followed by real-time continuous sync.

Continuous replication allows the application to stay online until a very quick final cutover phase.

Anahtar Kavram

Selecting data transfer appliances vs. online transfer services based on bandwidth calculations and choosing CDC-based database migration tools for minimal downtime cutovers.

Soru

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Konular