AD0-E602 Adobe Real-Time CDP Business Practitioner Professional Exam Questions and Answers

According to the Adobe documentation, attributes are fields that describe profile characteristics or traits, such as demographic information, preferences, or interests. Attributes can be dragged onto the segment builder canvas to define segment rules based on attribute values or ranges. In this case, the practitioner can drag an attribute that indicates the state of residence and set it to California. Reference:https://experienceleague.adobe.com/docs/experience-platform/segmentation/ui/segment-builder.html?lang=en#attributes

According to the Adobe documentation, realized profiles are those that have newly qualified for a segment, while exiting profiles are those that have been removed from a segment due to no longer meeting the segment definition. These profile status types can be used to analyze the segment’s profile count over time. Reference:https://experienceleague.adobe.com/docs/experience-platform/segmentation/ui/segment-profile-count.html?lang=en#profile-status-types

The most likely explanation for the dramatic drop in segment size is that the majority of browsers on the website are not authenticated. This means that they do not have a loyalty account or a unique identifier that can be matched with the gender attribute from the loyalty system. Therefore, they are excluded from the segment that ANDs the gender attribute with the browsing behavior. To increase the segment size, the retailer could use other methods to identify or infer the gender of anonymous browsers, such as cookies, device IDs, or third-party data.

According to the Adobe documentation, some destinations require email addresses to be hashed using SHA256 algorithm before they can be used as target identities. These destinations include Facebook, Salesforce Marketing Cloud, Linkedin Matched Audiences, and Google Customer Match. Reference:https://experienceleague.adobe.com/docs/experience-platform/destinations/ui/destination-actions.html?lang=en#hashing-email-addresses

According to the Adobe documentation, sequential segmentation is a type of segmentation that allows defining a sequence of events or attributes that must occur in a specific order for a profile to qualify for a segment. This type of segmentation can be used to create a segment of users who have purchased an item in the last 90 days and then purchased another item 5 days later. Reference:https://experienceleague.adobe.com/docs/experience-platform/segmentation/ui/sequential-segments.html?lang=en

According to the Adobe documentation, a custom namespace is a namespace that is created by the user to define a specific type or source of identity value that is not available in the predefined namespaces. A custom namespace for memberid would be recommended to fetch profiles for known customers who land on their website from Google organic search and authenticate, because memberid is a unique user id that is specific to this use case and not covered by any predefined namespace. References:https://experienceleague.adobe.com/docs/experience-platform/profile/identity-service/namespace.html?lang=en#custom-namespaces

An example of a profile namespace is email. A profile namespace is a type or source of identity value that is used to identify a customer across different data sources. Email is a predefined profile namespace that represents the email address of a customer. Other examples of profile namespaces are Phone Number, ECID, or CRM ID

According to the Adobe documentation, policies and labels are two key components of the Data Governance framework within AEP. Policies are rules that define how data can be used based on data usage labels and destination labels. Labels are metadata tags that indicate the type, purpose, and usage of data and destinations. The Data Steward must consider these items during set up within AEP to ensure data quality, compliance, and governance. Reference:https://experienceleague.adobe.com/docs/experience-platform/data-governance/home.html?lang=en#data-governance-framework

According to the Adobe documentation, primary identity is an identity that must be set in a schema in order to use it in Real-Time Customer Profile. Primary identity is an identity that uniquely identifies each profile within a dataset and across datasets within a tenant. Primary identity can be either predefined or custom, but it must have cardinality of one-to-one or many-to-one. References:https://experienceleague.adobe.com/docs/experience-platform/profile/identity-service/schema.html?lang=en#primary-identity

According to the Adobe documentation3, batch ingestion is the type of ingestion that supports automatic authentication. Batch ingestion enables data to be ingested periodically from sources such as databases, cloud storage, or CRM systems. Batch ingestion also supports authentication methods such as OAuth 2.0, API key, or username and password. References: 3 https://experienceleague.adobe.com/docs/experience-platform/ingestion/home.html?lang=en#batch-ingestion

According to the Adobe documentation, I2 is a type of identity label that indicates data that is indirectly identifiable, such as hashed email addresses or phone numbers. These datasets can be shared per company policies, as they do not contain directly identifiable data, such as I1 or 11 labels. Reference:https://experienceleague.adobe.com/docs/experience-platform/data-governance/dule/dule-overview.html?lang=en#identity-labels

According to the Adobe documentation, destination labels are labels that indicate the type and purpose of a destination, such as on-site or off-site, personalization or analytics, etc. Data usage policies are rules that define how data can be used based on data usage labels and destination labels. These two must be used to enforce data governance for activating segments to platform destinations by ensuring that only compatible data and destinations are allowed. Reference: https://experienceleague.adobe.com/docs/experience-platform/data-governance/labels/destination-labels.html?lang=en https://experienceleague.adobe.com/docs/experience-platform/data-governance/policies/policies-overview.html?lang=en