A smart manufacturing company needs to migrate its regional plant monitoring infrastructur… — Google Cloud Professional Cloud Architect

A smart manufacturing company needs to migrate its regional plant monitoring infrastructure to Google Cloud within a 14-day migration window. The legacy environment consists of a $250\text{ TB}$ archive of historical sensor logs stored on local NFS storage and a $400\text{ GB}$ operational PostgreSQL database. The on-premises site has a single dedicated $100\text{ Mbps}$ internet connection, and the database cutover requires near-zero downtime.

Which TWO architectural strategies should the team implement to meet these requirements? (Select TWO.)

Order a GCP Transfer Appliance to physically ingest and transfer the $250\text{ TB}$ sensor archive to Cloud Storage.Answer
Deploy Database Migration Service (DMS) with continuous Change Data Capture (CDC) to migrate the PostgreSQL database to Cloud SQL.Answer
C
Configure Storage Transfer Service to upload the $250\text{ TB}$ sensor archive directly over the $100\text{ Mbps}$ internet connection.
D
Provision a Cloud Spanner instance and perform a full offline database export and restore during the cutover window.

Answer

The team should order a GCP Transfer Appliance to move the

250\text{ TB}

sensor archive offline to Cloud Storage and use Database Migration Service (DMS) with continuous Change Data Capture (CDC) to migrate the PostgreSQL database to Cloud SQL with minimal downtime.

For large multi-terabyte data transfers (

250\text{ TB}

) over limited bandwidth (

100\text{ Mbps}

), online network transfer would take over 230 days, making an offline appliance like GCP Transfer Appliance essential to complete the transfer within a 14-day window. For operational relational database migrations requiring near-zero downtime, using Database Migration Service with CDC enables continuous replication from PostgreSQL to Cloud SQL, allowing a rapid cutover.

Step-by-Step Solution

Calculate the transfer duration for the unstructured sensor log archive over the existing network connection.

Transferring

250\text{ TB}

(

2\times 10^{15}\text{ bits}

) at

100\text{ Mbps}

takes approximately

20,000,000\text{ seconds} \approx 231\text{ days}

, which exceeds the 14-day window.

Large multi-terabyte datasets on constrained network pipes require offline physical transfer via GCP Transfer Appliance.

Select the appropriate data migration mechanism for the

250\text{ TB}

unstructured dataset.

Use GCP Transfer Appliance to load data locally, ship the appliance to Google Cloud, and ingest into Cloud Storage within the 14-day window.

Transfer Appliance bypasses network bandwidth bottlenecks for multi-terabyte dataset migrations.

Select the database migration strategy for the

400\text{ GB}

operational PostgreSQL database requiring near-zero downtime.

Utilize Database Migration Service (DMS) configured with continuous CDC targeting Cloud SQL for PostgreSQL.

CDC continuously syncs real-time transaction logs, allowing applications to perform a fast cutover without extended maintenance windows.

Key Concept

Evaluating network transfer throughput versus offline physical data transport appliances, and designing continuous replication paths for low-downtime relational database migrations.

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics