Which type of constraint can be defined in the Batch API's payload while sending bulk data to Adobe Real-Time CDP?

When ingesting data using the Batch Data Ingestion API, the payload must conform to a specific Experience Data Model (XDM) schema. This schema acts as a constraint, defining the structure, data types, and fields that are permissible within the batch. If the data in the payload does not validate against the referenced XDM schema, the batch will fail. This ensures data consistency and quality within the Adobe Experience Platform data lake and Real-Time Customer Profile.

A. Encryption Type: Encryption is a transport-level or storage-level concern, not a constraint defined within the API payload for a specific batch.
B. Batch Size: Batch size is a constraint on the overall batch file or set of files, but it is not a parameter defined within the JSON payload itself.
D. Batch Frequency: Batch frequency relates to how often data is sent. It is a scheduling aspect of the data pipeline, not a constraint within the data payload.

1. Adobe Experience Platform Documentation. (2023). Batch Data Ingestion API overview. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/data-ingestion/batch-ingestion/overview.html. (The "How it works" section explains that data must conform to an XDM schema).

2. Adobe Experience Platform Documentation. (2023). Create a batch. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/data-ingestion/batch-ingestion/api-reference.html#create-a-batch. (The API reference shows the datasetId is required, which is associated with a specific XDM schema, thus enforcing the schema constraint).