The Oracle Cloud Infrastructure (OCI) Object Storage Multipart Upload API is designed for uploading large objects efficiently. The process involves splitting a large object into individual parts. According to OCI service limits, each part can have a maximum size of 50 GiB. An object can be split into a maximum of 10,000 parts. These parts can be uploaded independently and in parallel, and after all parts are uploaded, a final commit operation is required to assemble them into a single object in the storage bucket.

A. A final commit operation is mandatory. Without it, the uploaded parts are not assembled into a final object, and the upload remains incomplete.

B. The core concept of a multipart upload is to split a large object into smaller, more manageable parts for parallel and resilient uploads.

1. Oracle Cloud Infrastructure Documentation, "Using Multipart Uploads": This document outlines the three-step process for multipart uploads: Initiate, Upload Parts, and Commit. It explicitly states, "After you have uploaded all the object parts, you commit the upload." This directly refutes option A. It also describes the fundamental concept: "In a multipart upload, a large object is broken into smaller parts," which refutes option B.

Reference: Oracle Cloud Infrastructure Documentation > Storage > Object Storage > Using Multipart Uploads > Multipart Uploads for the Console, CLI, and SDKs.

2. Oracle Cloud Infrastructure Documentation, "Service Limits": This official documentation page lists the specific service limits for Object Storage.

Reference: Oracle Cloud Infrastructure Documentation > Solution & Platform > Core Services > Service Limits > Object Storage and Archive Storage Service Limits.

Under the "Object Storage and Archive Storage Service Limits" table, the "Maximum size for an object part in a multipart upload" is listed as "50 GiB," confirming option C.

The "Maximum number of parts for a multipart upload" is listed as "10,000," confirming option D.