You have 32 GB of data in a single file that you need to upload to a Nearline Storage bucket.
The WAN connection you are using is rated at 1 Gbps, and you are the only one on the connection.
You want to use as much of the rated 1 Gbps as possible to transfer the file rapidly.
How should you upload the file?
Click on the arrows to vote for the correct answer
A. B. C. D.B.
The most efficient way to transfer a large file to a Nearline Storage bucket while utilizing the available bandwidth is to use parallel composite uploads. Therefore, option B is the correct answer.
Parallel composite uploads split the file into multiple parts and upload them simultaneously, enabling multiple TCP connections to transfer the data concurrently. This approach allows the bandwidth to be fully utilized, and the file can be uploaded much faster than with a single connection.
Using the GCP Console to transfer the file (option A) is not the most efficient option since the Console uses a single connection to transfer files, and it may not be able to fully utilize the available bandwidth. It is better to use a command-line tool like gsutil, which supports parallel composite uploads.
Decreasing the TCP window size on the machine initiating the transfer (option C) can limit the amount of data that can be sent per unit of time, reducing the throughput and potentially increasing the transfer time.
Changing the storage class of the bucket from Nearline to Multi-Regional (option D) will not impact the upload speed, but it will change the storage cost and access time of the data. Multi-Regional storage is more expensive than Nearline, but it provides faster access times.