Yes. Only 1 record will be available in profile with a given _id. Second record won’t be processed to profile. —ssj

Yes. It is normal and as expected. Lookup attributes won't show up in profile lookup, neither available for profile export. Lookup attributes are available for conditions in audience creation.  If you need them, then you need to consider ingesting the lookup attributes as individual profile attribut...

Hi Gowthamr123 For csv, in general you need to avoid the character which you are using as delimiter, and the single row should not be split into multiple rows, meaning there should not be any enter character in between the data of a single record. --ssj

It is very well possible to ingest data into array object from Parquet file. Source Parquet file should be XDM compliant file, as you don't have option for data mapping. fyi, Data of array object won't be visible in UI. you need to query the dataset to see the data of array object attribute. --ssj

As far my understanding, ABAC rules apply only to UPS (RTCDP) not for data lake. As CJA reads data from data lake, ABAC is not applicable for CJA. --SSJ

if you are ingesting into dataset of individual profile schema, then both _id and createdByBatchID are not mandatory.  _id - its to identify the record uniquely. you can think of something like surrogate key in a data warehouse. createdByBatchID - you don't need to pass any value for this. --SSJ

consider having a container only to exclude audience with the condition "event with (eventType=userUpdate and Status not equal to = A/B/C/D)" in the first segment. --SSJ

Minimum frequency to export audience to DLZ is 3 hours. You can consider streaming destination like HttpAPI streaming to activate instantly.  --SSJ

please check the below link which explains about sequential segment. https://experienceleague.adobe.com/docs/platform-learn/tutorials/audiences/create-sequential-audiences.html?lang=en In your case you can give condition as like event with "x" product purchase and a sequential condition saying there...

Timeseries Attributes cannot be exported to destination.