Answer-first summary for fast verification
Answer: Create a new TSV file for remaining files by generating signed URLs with a longer validity period, split the TSV file into smaller files, and submit them as separate Storage Transfer Service jobs in parallel.
The correct answer is C. The HTTP 403 errors on the remaining files are likely due to the expiration of the signed URLs. Generating new signed URLs with a longer validity period ensures they remain valid longer, allowing the Storage Transfer Service job to complete without further 403 errors. Other options do not address the root cause of expired signed URLs: A involves unnecessary setup without solving the URL expiration, B incorrectly focuses on TLS certificate renewal, and D changes checksum types without addressing URL validity.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You are transferring a large number of files from a public HTTPS endpoint to Cloud Storage, secured with signed URLs to prevent unauthorized access. After creating a TSV file with the object URLs and initiating a transfer job using Storage Transfer Service, the job fails after some time due to HTTP 403 errors on remaining files, despite no changes to the source system. What should you do to resolve this issue and ensure a smooth migration?
A
Set up Cloud Storage FUSE, mount the Cloud Storage bucket on a Compute Engine instance, remove completed files from the TSV file, and use a shell script to download remaining URLs to the FUSE mount point.
B
Renew the TLS certificate of the HTTPS endpoint, remove completed files from the TSV file, and rerun the Storage Transfer Service job.
C
Create a new TSV file for remaining files by generating signed URLs with a longer validity period, split the TSV file into smaller files, and submit them as separate Storage Transfer Service jobs in parallel.
D
Update the file checksums in the TSV file from MD5 to SHA256, remove completed files from the TSV file, and rerun the Storage Transfer Service job.
No comments yet.