AD0-E600 Exam Dumps : Adobe Experience Platform Technical Foundations

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?

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?

In an AEP implementation, an SFTP source setup performs daily imports. A marketer notices that the segment volumes linked to that data source have dropped in the last days. After a root cause analysis, it is identified that the dataflow that manages the SFTP import has been disabled by mistake.

The missing files must be ingested in AEP, and the daily import must be re-started.

How should these tasks be performed?