You create an Azure Cosmos DB for NoSQL database.
You plan to use the Azure Cosmos DB .NET SDK v3 API for NoSQL to upload the following files:
You receive the following error message when uploading the files: “413 Entity too large”.
You need to determine which files you can upload to the Azure Cosmos DB for NoSQL database.
Which files can you upload?
Azure Cosmos DB for NoSQL has a per-item size limit of 2 MB when using the Azure Cosmos DB .NET SDK v3 API. Considering this, only files that are 2 MB or smaller can be uploaded. Therefore, File1 (1 MB) and File2 (2 MB) are the only files that meet this criterion.
Correct - 2MB limit -https://learn.microsoft.com/en-us/azure/cosmos-db/concepts-limits#per-item-limits
2 GB it is. Maximum size of an item = 2 MB (UTF-8 length of JSON representation) ¹ ¹ Large document sizes up to 16 MB are supported with Azure Cosmos DB for MongoDB only.
Option B is correct. Each file has a maximum size of 2 MB. So File 1, File 2 Only can be uploaded.
this correct: https://learn.microsoft.com/en-us/answers/questions/692455/actual-document-size-limit-for-azure-cosmos-db-s-a While it is possible to store more than 2MB
Correct Answer is E: Azure Cosmos DB limits single request's size to 2MB. The formula is Request Size = Single Document Size * Write Batch Size. If you hit error saying "Request size is too large.", reduce the writeBatchSize value in copy sink configuration https://learn.microsoft.com/en-us/azure/data-factory/connector-azure-cosmos-db?tabs=data-factory
B is correct
E, because the total of files in the batch will exceed 2 MB
I think the correct answer is E not B because the total size for File1 and File2 will be 3 MB
The requirements do not specify that they MUST be uploaded in one batch
I'll go with the agreed answer but it also did not say the files are uploaded individually. So the answer E has some merit.