AD0-E600 Exam Dumps : Adobe Experience Platform Technical Foundations

A national workout studio chain is introducing a new Family discount program. They have already deployed AEP with the following data model:

• Members Schema (Individual Profile Based):

• Primary ID: Member ID

• Secondary IDs: Email Hash. Phone Hash

• Training Sessions Management (Experience Event):

• Primary ID: Member ID

• Secondary IDs: ECID

• Subscription Management (Experience Event):

• Primary ID: Email Hash

• Secondary IDs: ECID

The workout studio wants to be able to use all of this information together with the family details to segment For example, they want to target families where one family member trams daily or one family member has the yearly subscription plan.

To start collecting Family information, the workout studio creates a form where the members can create a Family account and associate the different members to it The form will collect a list of Member IDs and generate a Family ID. A data architect will design a new schema to store the Family information.

Which identities should be used in the schema(s) to collect this form information?

A B2B business (the client) is migrating its data warehouse (DWH) solution to AEP. Currently, they are using what they call Recipient ID as the main identifier to recognize client employees. That Recipient 10 is generated inside the DWH. That solution will not be available once AEP is live, so the solution architect needs to consider potential alternatives.

After working with the client lead and a data engineer, the solution architect identifies that a combination of Company ID and Hashed Employee Email would be a good replacement for the Recipient ID to make it more unique.

How can the solution architect generate that identity within AEP?

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?