Question

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?

Accepted Answer

The Company ID and Hashed Employee Email must be combined outside of AEP and passed as a unique primary identity.

Answer

The Company ID (non-people identifier) must be set up as a primary ID. The Hashed Employee Email as a secondary ID and AEP will automatically reconcile them.

Answer

The Company ID and Hashed Employee Email must be combined in AEP data prep and passed as a unique primary identity.

Answer

The Hashed Employee Email must be set up as a primary ID. The Company ID (non-people identifier) as a secondary ID and AEP will automatically reconcile them.

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…

Take the free AD0-E600 practice test

Other AD0-E600 practice questions