You’re migrating many files protected by signed URLs from a public HTTPS endpoint using Storage Transfer Service. The transfer ran, then started failing with HTTP 403 on remaining files. Source unchanged. How do you fix and resume migration?
Choose an answer
Tap an option to check your answer.
Correct answer: 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..
Why this is the answer
The HTTP 403 error indicates that the signed URLs have expired, as signed URLs are time-limited. To fix this, new signed URLs with a longer validity period must be generated for the remaining files. Splitting the TSV file and running parallel jobs can improve transfer efficiency and resilience. Incorrect options: Cloud Storage FUSE and a shell script are manual and inefficient for large-scale migrations, and don't address the expired signed URL issue. Renewing the TLS certificate of the HTTPS endpoint is irrelevant to signed URL expiration. Changing checksums from MD5 to SHA256 doesn't resolve the 403 error caused by expired signed URLs.
Pass your exam — without the endless answer hunt
Get every verified question and explanation for this exam in one place, and save hours of prep. 1,000+ certifications · 20+ languages · free to start.
Pass your exam faster → No card needed