You need to migrate an internal file upload API with an enforced 500-MB file size limit to App Engine.
What should you do?
Click on the arrows to vote for the correct answer
A. B. C. D.C.
https://wiki.christophchamp.com/index.php?title=Google_Cloud_PlatformThe correct answer for this question is D. Change the API to be a multipart file upload API.
Explanation: To migrate an internal file upload API with an enforced 500-MB file size limit to App Engine, it's important to consider the constraints and requirements of the App Engine environment. Here are a few reasons why the other options are not suitable for this task:
A. Use FTP to upload files: FTP (File Transfer Protocol) is a standard network protocol used to transfer files from one host to another over a TCP-based network. However, App Engine doesn't support FTP, and even if it did, it would not be an optimal solution for uploading large files.
B. Use CPanel to upload files: cPanel is a web hosting control panel that allows website owners to manage their websites from a web-based interface. However, it's not relevant to this question as cPanel is not a file upload API.
C. Use signed URLs to upload files: Signed URLs are a way to grant temporary access to a specific resource or object in a Cloud Storage bucket. However, they are typically used for granting access to a limited set of users or clients, rather than as a general file upload API.
D. Change the API to be a multipart file upload API: This is the correct answer. A multipart file upload API allows for the upload of large files by breaking them into smaller parts that can be uploaded in parallel. This approach is more efficient and reliable for large file uploads and is commonly used in cloud environments like App Engine.
In conclusion, the best option for migrating an internal file upload API with a 500-MB file size limit to App Engine is to change the API to be a multipart file upload API.