A media archiving enterprise needs to migrate 600 TB of uncompressed video assets from on-premises NFS and SMB storage arrays to Google Cloud Storage. The organization has established the following operational constraints: The dedicated outbound network connection available for the migration is limited to 100 Mbps The entire data migration and validation must be completed within 30 days due to an upcoming data center lease termination The transfer process must maintain data integrity and support local POSIX/SMB share access without requiring application refactoring Which data transfer strategy should you recommend to meet these requirements?

Order physical Google Cloud Transfer Appliance devices, mount the local shares via NFS/SMB to copy the data, and ship the appliances back to Google for ingestion: ### What Transfer Appliance Is **Transfer Appliance** is a high-capacity, ruggedized physical storage server provided by Google Cloud to facilitate offline data migration. It allows organizations to securely transfer large data volumes—from tens of terabytes to petabytes—into Cloud Storage when internet bandwidth is insufficient or project timelines are tight. ### How It Meets the Requirements - **Project Timeline vs. Network Bandwidth**: At a dedicated bandwidth of 100 Mbps, transferring 600 TB online would theoretically take more than **550 days** (approx. 1.08 TB/day). Physical shipment via **Transfer Appliance** bypasses network throughput limits and completes within days to a couple of weeks. - **Storage Protocol Support**: Transfer Appliance provides native support for **NFS**, **SMB/CIFS**, and local filesystem mounts, allowing direct ingestion from existing on-premises network storage. - **Data Integrity and Security**: Data written to Transfer Appliance is encrypted locally with AES-256 before transit, ensuring secure offline logistics. ### Key Advantages - **Bypasses WAN bottlenecks**: Eliminates reliance on limited internet or VPN bandwidth. - **High local capture throughput**: Ingests data at multi-gigabit local network speeds. - **End-to-end encryption**: Secures data at rest and during shipping. - **Seamless Cloud Storage ingestion**: Automatically uploads encrypted data to target buckets upon receipt at Google facilities. ### Why This Is Optimal When the math dictates that online transfer over the existing connection exceeds the 30-day deadline by hundreds of days, **Transfer Appliance** is the only architecturally viable and cost-effective approach.

StudyCerts

Compare Storage Transfer Service Transfer Appliance | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Compare Storage Transfer Service Transfer Appliance

Section: Movement of data

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

A media archiving enterprise needs to migrate 600 TB of uncompressed video assets from on-premises NFS and SMB storage arrays to Google Cloud Storage.

The organization has established the following operational constraints:

The dedicated outbound network connection available for the migration is limited to 100 Mbps
The entire data migration and validation must be completed within 30 days due to an upcoming data center lease termination
The transfer process must maintain data integrity and support local POSIX/SMB share access without requiring application refactoring

Which data transfer strategy should you recommend to meet these requirements?

Order physical Google Cloud Transfer Appliance devices, mount the local shares via NFS/SMB to copy the data, and ship the appliances back to Google for ingestion

Execute parallel gcloud storage rsync commands across multiple local Linux workstations to copy files to Cloud Storage

Configure Cloud Storage FUSE on all on-premises servers and execute asynchronous file write operations over an IPsec VPN tunnel

Deploy Storage Transfer Service on-premises agents to stream the dataset over the existing 100 Mbps internet connection directly to Cloud Storage

Professional Cloud Architect

Compare Storage Transfer Service Transfer Appliance

Related questions