A global pharmaceutical enterprise plans to migrate its legacy clinical trial platform to … — Google Cloud Professional Cloud Architect

A global pharmaceutical enterprise plans to migrate its legacy clinical trial platform to Google Cloud. The workload comprises $3.2\text{ PB}$ of static genomic sequence files stored on local Network Attached Storage (NAS) arrays and a live $15\text{ TB}$ PostgreSQL transactional database. The organization maintains a $2\text{ Gbps}$ Partner Interconnect connection, but strict QoS policies limit dedicated migration traffic to a maximum of $500\text{ Mbps}$ . The business mandates that the $3.2\text{ PB}$ genomic dataset must be fully ingested into Cloud Storage within $45\text{ days}$ , the database cutover must incur less than $10\text{ minutes}$ of service downtime, and all ingested data must be shielded against unauthorized egress and exfiltration. Which TWO architectural strategies should the lead cloud architect incorporate into the migration plan to meet these requirements?

Order multiple Google Cloud Transfer Appliances to execute an offline bulk transfer of the $3.2\text{ PB}$ genomic dataset, and establish VPC Service Controls security perimeters around the target Cloud Storage buckets.Cevap
Use Database Migration Service (DMS) with continuous Change Data Capture (CDC) over the Partner Interconnect to replicate the on-premises PostgreSQL database to Cloud SQL for PostgreSQL prior to cutover.Cevap
C
Deploy Storage Transfer Service agents on local NAS servers to stream the $3.2\text{ PB}$ genomic sequence files online over the $500\text{ Mbps}$ Partner Interconnect allocation directly into Cloud Storage.
D
Migrate the live $15\text{ TB}$ PostgreSQL database to Cloud Spanner using Cloud Storage dump files and automated schema translation to guarantee continuous multi-region availability without cutover downtime.

Cevap

The architect must specify ordering Google Cloud Transfer Appliances for the

3.2\text{ PB}

static dataset with VPC Service Controls perimeter defense, alongside deploying Database Migration Service with CDC replication to Cloud SQL for the

15\text{ TB}

database cutover.

The correct strategy combines offline physical ingestion via Transfer Appliance for petabyte-scale data constrained by a 500 Mbps network ceiling with VPC Service Controls for exfiltration protection, and uses Database Migration Service with CDC to achieve continuous replication to Cloud SQL for PostgreSQL within a minimal cutover window.

Adım Adım Çözüm

Calculate network throughput limitations for bulk file transfer

Streaming

3.2\text{ PB}

(

25.6 \text{ Pb}

) over

500\text{ Mbps}

takes

\approx 592\text{ days}

, exceeding the

45\text{ day}

SLA.

Determines whether online transfer (Storage Transfer Service) or offline transfer (Transfer Appliance) is required.

Evaluate data transfer mechanism and perimeter security for static storage

Select Transfer Appliance for offline physical transport and wrap destination Cloud Storage buckets in VPC Service Controls.

Satisfies the 45-day transfer timeline and addresses the data exfiltration compliance requirement.

Evaluate continuous database replication strategy for low downtime

Initial seed of

15\text{ TB}

takes

\approx 2.78\text{ days}

over

500\text{ Mbps}

, followed by low-bandwidth CDC sync using Database Migration Service.

Allows transaction catching-up in real time, reducing final cutover downtime to under 10 minutes.

Anahtar Kavram

Selecting optimal data transfer pathways based on bandwidth calculation limits and choosing appropriate database replication tools for minimal-downtime cutovers.

Tahmini Süre:3m 0s

Soru

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Konular