Fastest Method to Transfer 10 TB Database Export to Cloud Storage
Your company wants to migrate their 10-TB on-premises database export into Cloud Storage. You want to minimize the time it takes to complete this activity, the overall cost, and database load. The bandwidth between the on-premises environment and Google Cloud is 1 Gbps. You want to follow Google-recommended practices. What should you do?
Community Insight
The question tests Google's recommended data transfer practices for large datasets; the common trap is choosing Transfer Appliance for data over 1 TB, but at 1 Gbps a 10-TB transfer completes in roughly 30 hours—well under the ~20-day appliance turnaround—so gsutil -m is faster, cheaper, and still Google-recommended for this scale.
This PCA exam question asks the optimal method to migrate a 10-TB on-premises database export into Google Cloud Storage over a 1 Gbps link while minimizing time, cost, and database load. The correct approach is to compress the data and upload it using gsutil -m for multi-threaded parallel transfer, since the ~30-hour transfer time far beats the 1–3 week turnaround of Transfer Appliance.
Most learners choose B (Transfer Appliance) because Google associates it with large transfers over 1 TB, but at 1 Gbps the 10-TB upload finishes in about 30 hours versus 1–3 weeks for appliance shipping, loading, returning, and rehydration—making the appliance both slower and more expensive.
Community Discussion (175 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option D—compress the data and upload it with gsutil -m—minimizes time, cost, and database load simultaneously. At 1 Gbps, 10 TB transfers in roughly 30 hours using multi-threaded parallel uploads, which is dramatically faster than the 1–3 week turnaround for a Transfer Appliance (ship, load, ship back, rehydrate). Google's architecture guidance on transferring large datasets explicitly states that Transfer Appliance should only be considered when the online transfer time is "substantially more than" the ~20-day appliance turnaround time—30 hours is nowhere close. Compression further reduces transfer time and the multi-threaded flag maximizes throughput without adding load to the database, since the export is a file-level upload.
Why the Other Options Are Wrong
Option A (Dataflow job reading directly from the database) would sustain heavy load on the on-premises database for the entire transfer duration, directly contradicting the requirement to minimize database load. Option B (Transfer Appliance) is designed for scenarios where the online transfer time substantially exceeds 20 days; here the online transfer completes in under two days, so the appliance adds weeks of latency and shipping costs with no benefit. Option C (commercial partner ETL solution) is not a Google-recommended practice and introduces unnecessary licensing costs and complexity for what is simply a bulk file transfer.
Community Comment Notes
The most upvoted comment by pr2web provides a concrete calculation: "Time to transfer using 1Gbps: 30 hours" versus "Time to transfer using Transfer Appliance: 1-3 weeks," concluding "Answer is D." Several learners like mikesp note that Google's guidance recommends Transfer Appliance for transfers exceeding 1 TB, but they overlook that the recommendation is conditional on online transfer time exceeding the appliance turnaround. Commenter moota correctly quotes Google's guidance that appliance consideration applies when online transfer is "substantially more than" 20 days, which does not apply here.
Official Reference
Exam Strategy
When comparing transfer methods, always calculate the actual online transfer time from the bandwidth given. If the online transfer completes far faster than appliance turnaround (~20 days), the online method (gsutil -m or Storage Transfer Service) is the correct choice.
Frequently Asked Questions
Why isn't Transfer Appliance (B) faster for a 10-TB database export at 1 Gbps?
At 1 Gbps, 10 TB transfers online in about 30 hours. Transfer Appliance requires shipping, loading, returning, and rehydrating data—totaling 1–3 weeks—so it is substantially slower for this volume and bandwidth.
Google recommends Transfer Appliance for transfers over 1 TB—why doesn't that apply here?
That recommendation is conditional: appliance is preferred only when the online transfer time substantially exceeds the ~20-day appliance turnaround. Here 30 hours is far less than 20 days, so gsutil -m is the faster, cheaper option.
Related Analysis
Practice All PCA Questions
Access 81 questions with complete answers and detailed explanations.
View Full PCA Practice Test →