PROFESSIONAL-CLOUD-DEVELOPER · Question #47
You need to migrate an internal file upload API with an enforced 500-MB file size limit to App Engine. What should you do?
The correct answer is D. Change the API to be a multipart file upload API. App Engine Standard environment has a 32 MB request body size limit, which makes directly uploading 500 MB files via a standard HTTP POST impossible. Converting the API to a multipart file upload API breaks the large file into smaller chunks, each of which can be sent as a…
Question
You need to migrate an internal file upload API with an enforced 500-MB file size limit to App Engine. What should you do?
Options
- AUse FTP to upload files.
- BUse CPanel to upload files.
- CUse signed URLs to upload files.
- DChange the API to be a multipart file upload API.
How the community answered
(15 responses)- A13% (2)
- B7% (1)
- D80% (12)
Explanation
App Engine Standard environment has a 32 MB request body size limit, which makes directly uploading 500 MB files via a standard HTTP POST impossible. Converting the API to a multipart file upload API breaks the large file into smaller chunks, each of which can be sent as a separate part within the App Engine request limits, allowing the upload to complete successfully. This approach preserves the API's existing HTTP interface while working around the platform constraint. Options A (FTP) and B (CPanel) are not viable approaches for App Engine and are not GCP-native solutions. Option C (signed URLs) would redirect uploads directly to Cloud Storage, bypassing App Engine entirely - while technically functional, it requires restructuring the client to interact with GCS directly rather than the API, making D the more conservative migration choice.
Topics
Community Discussion
No community discussion yet for this question.