You need to migrate an internal file upload API with an enforced 500-MB file size limit to App Engine.
What should you do?
You need to migrate an internal file upload API with an enforced 500-MB file size limit to App Engine.
What should you do?
To migrate an internal file upload API with a 500-MB file size limit to App Engine, you should use signed URLs to upload files. Signed URLs provide a secure way to allow users to upload large files directly to Google Cloud Storage without passing through your App Engine, thus bypassing App Engine's file size limitations. This enables handling large files efficiently, ensuring that the platform's limitations do not hinder the file upload process.
While C is a very good option if you want to people to upload files, it does not solve the problem represented by the size.
C is correct answer
true https://stackoverflow.com/a/18882565/8681600
https://cloud.google.com/appengine/docs/standard/php/googlestorage/user_upload: "Note that you must start uploading to this URL within 10 minutes of its creation. Also, you cannot change the URL in any way - it is signed and the signature is checked before your upload begins" C is the answer
It should use multipart to upload big size files
The correct answer is C because signed url permits to upload a big file in multipart-mode
C is the best choice
C is correct
How is C correct ? Isn't it used to give temporary access to objects in buckets ?
By changing the API to support multipart file uploads, you can maintain the functionality of your existing API while adapting it to the App Engine environment.
https://stackoverflow.com/questions/45812595/google-cloud-storage-signed-urls-how-to-specify-a-maximum-file-size
C. Use signed URLs to upload files: Signed URLs are a secure way to give time-limited read or write access to a specific Google Cloud Storage object, without needing Google account credentials. You can create a signed URL that allows an object to be accessed with the specified restrictions such as HTTP method (PUT for uploads) and an expiration time. This method would allow your API users to upload files directly to Google Cloud Storage, which can handle large files efficiently. Your App Engine application can then process or reference these files as needed.
D. Change the API to be a multipart file upload API: While multipart uploads can be helpful for large files, they don't address the core issue of App Engine's size limitations. The uploads would still need to go through App Engine, potentially exceeding the limits.
C is correct: Signed URLs allow you to generate URLs with limited-time access to upload directly to Google Cloud Storage. This method bypasses App Engine's file upload limitations and allows clients to upload large files directly to Cloud Storage.