These are two possible reasons why some identities have been excluded after mapping a segment to an external destination. Some identities were not recognized by the destination means that there was no matching identifier between AEP and the destination system. For example, if AEP sends email addresses as identifiers but the destination system expects phone numbers as identifiers, then there will be no match and those identities will be excluded. Some identities were not meeting consent policies means that there was a violation of data usage governance rules based on data labels and marketing actions. For example, if AEP sends PII data as part of a segment but the destination system is not authorized to use PII data for personalization purposes, then those identities will be excluded. References: : Identity Mapping Overview : Data Usage Governance Overview

This is the most suitable segment to evaluate streaming data from Adobe Analytics in real-time and filter out customers who are not in the CRM system. By basing the segment on the Adobe Analytics data source, the company can use the streaming ingestion feature of AEP to capture web activity data in near real-time. By using membership in a Customer segment, the company can use an existing segment that contains customers from the CRM system as a filter criterion to exclude non-customers from the segment. References: : Streaming Ingestion Overview : Create a Segment

The correct answers are A, B, and C because they are valid options that can be added to modify the file name. The engineer can add date and time, counter variable, or custom text to make the file name more descriptive. The other options are not available or relevant for modifying the file name. References: