Given the following:
How should a data engineer ingest this data?
After creating the Entity Relationship (Diagram (ERD) of the data sources that will be connected into an AEP implementation for a utility company, the service details (including information such as name, cost type, and category) appear multiple times across different entities (for example, in the transactional events and m the customer profile details).
When designing the XDM data model for that ERD, the data architect and the business stakeholders validate that the service details information must be included at both levels, record, and time series. The service details will be used multiple times within the same structure.
How should the service details be defined in the AEP data model to make it consistent and re-usable?
Which choices explain the data lineage that DULE enforces?
This is the data lineage that DULE enforces according to this document.
A data engineer wants to connect a new data source into AEP using an Amazon S3 Bucket. The S3 Bucket currently will be added with the daily deltas.
The historical data and the recurrent deltas must be imported.
In which way can this task be performed with minimal effort?
This will allow you to import both historical data and recurrent deltas without creating multiple dataflows.
A QA engineer needs to determine if the data ingested through three different data sources into three datasets enabled for profile and based in the same XDM Profile schema is processed as expected.
To evaluate the final result, the QA engineer uses the Merge Profile configuration shown;
The primary identity used is '.orgtenant.profilelDs.email".
What data should appear m the user profile?