Google Professional Data Engineer
Get started today
Ultimate access to all questions.
Comments
Loading comments...
Ultimate access to all questions.
You are migrating a large number of files from a public HTTPS endpoint to Google Cloud Storage. These files are protected from unauthorized access using signed URLs, which provide limited-time access control. To facilitate the migration, you created a TSV file that contains the list of object URLs, and you initiated a transfer job using Google's Storage Transfer Service.
After some time, you observed that the transfer job had been running for an extended period before eventually failing. Upon inspecting the logs of the transfer job, you found that it was progressing smoothly until it encountered a series of HTTP 403 errors, which caused the remaining files to fail to transfer. You have confirmed that there were no changes to the source system during this time. To resume and complete the migration process, what steps should you take to address this issue?
A
Set up Cloud Storage FUSE, and mount the Cloud Storage bucket on a Compute Engine instance. Remove the completed files from the TSV file. Use a shell script to iterate through the TSV file and download the remaining URLs to the FUSE mount point.
B
Renew the TLS certificate of the HTTPS endpoint. Remove the completed files from the TSV file and rerun the Storage Transfer Service job.
C
Create a new TSV file for the remaining files by generating signed URLs with a longer validity period. Split the TSV file into multiple smaller files and submit them as separate Storage Transfer Service jobs in parallel.
D
Update the file checksums in the TSV file from using MD5 to SHA256. Remove the completed files from the TSV file and rerun the Storage Transfer Service job.