Adobe AD0-E600 Adobe Experience Platform Technical Foundations Exam Practice Test

A training run involves generating insights from your data while a scoring run is about learning patterns from your data. A training run requires that a scoring run has occurred. References:https://experienceleague.adobe.com/docs/experience-platform/data-science-workspace/overview.html?lang=en#data-science-training-and-scoring

Based on the options for ID stitching and merge method respectively, the appropriate type of merge policy for this use case is:

• ID stitching: None
• Merge method: Dataset precedence

The merge policy determines how data fragments from multiple sources are combined to create a complete view of each individual customer. The merge policy is defined by the ID stitching and merge method options.

In this use case, the marketer wants to create a segment that qualifies profiles from all datasets that are enabled for profile. The use case for the segment is for activation to advertising destinations. Therefore, the appropriate type of merge policy is ID stitching: None and Merge method: Dataset precedence.

https://experienceleague.adobe.com/docs/experience-platform/profile/merge-policies/overview.html%3Flang%3Den

 The segment membership status at each time period is Existing, Realized, Exited, Exited. References:https://experienceleague.adobe.com/docs/segmentation/using/segmentation-workflow/segmentation-job-status.html?lang=en#segment-job-status

If a previously defined mandatory field is no longer available due to some changes in the inbound data, the data architect responsible for maintaining existing schemas has the following options:

• Remove the previously defined field: This option is not appropriate because the field is mandatory and removing it would cause issues with data ingestion.
• Make the current mandatory field optional: This option is appropriate because the field is no longer available and making it optional would allow data ingestion to continue without issues.
• Rename the existing field: This option is not appropriate because renaming the field would cause issues with data ingestion.
• Assign the field a new data type: This option is not appropriate because the field is mandatory and changing its data type would cause issues with data ingestion.

Therefore, the data architect can make the current mandatory field optional.

https://experienceleague.adobe.com/docs/experience-platform/data-prep/home.html

every event loaded into AEP requires a unique ID (_id) that identifies the event. The _id field should be a string that is unique across all events in a dataset.

https://experienceleague.adobe.com/docs/experience-platform/profile/home.html?lang=en