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

According to the Adobe documentation 3 , identity value and namespace are two elements that must match in the data sources for the profile to merge. Identity value is the unique identifier for a customer, such as an email address or a phone number. Namespace is the type or source of the identity value, such as Email or Phone Number.  When two data sources have the same identity value and namespace, they can be stitched together to form a unified profile. References:  3   https://experienceleague.adobe.com/docs/experience-platform/profile/identity-service/overview.html?lang=en#identity-service-overview

According to the Adobe documentation, segment job is a feature that allows running an on-demand evaluation of segments using batch datasets and getting an updated segment count within minutes. Segment job can be used to achieve this task by selecting the segment and clicking on “Run segment job” from the action bar. Reference: https://experienceleague.adobe.com/docs/experience-platform/segmentation/ui/segment-job.html?lang=en

According to the Adobe documentation, timestamp ordered is a merge method that can be used to create a custom merge policy in Adobe Experience Platform for an upcoming use case to ensure profile attributes take precedence from latest datasets and are applied across all datasets automatically. Timestamp ordered merge method prioritizes profile attributes based on their ingestion timestamp, with newer values taking precedence over older values. Timestamp ordered merge method also applies globally across all datasets within a tenant. References: https://experienceleague.adobe.com/docs/experience-platform/profile/merge-policies/methods.html?lang=en#timestamp-ordered

According to the Adobe documentation 3 , 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, profiles added and profile source are two standard widgets that are available in a Profiles overview dashboard of Real-time CDP. Profiles added widget shows the number of profiles that have been added to the platform over time. Profile source widget shows the breakdown of profiles by their source type, such as batch or streaming. References: https://experienceleague.adobe.com/docs/experience-platform/profile/ui/overview.html?lang=en#profiles-overview-dashboard

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

The explanation for why the segment size which includes both forms is 12,000 is that 3,000 people filled out both form 1 and form 2. This can be derived from the following formula:

Segment size of form 1 OR form 2 = Segment size of form 1 + Segment size of form 2 - Segment size of form 1 AND form 2

Plugging in the given numbers, we get:

12,000 = 5,000 + 10,000 - Segment size of form 1 AND form 2

Solving for Segment size of form 1 AND form 2, we get:

Segment size of form 1 AND form 2 = 3,000

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

According to the Adobe documentation, identity and namespace are the two required fields that must be included in a request to access or delete through the privacy service. Identity is the value of the identifier for the profile, such as an email address or a phone number. Namespace is the type of identifier, such as ECID or CRM ID. Reference: https://experienceleague.adobe.com/docs/experience-platform/privacy/ui/create-request.html?lang=en#required-fields

According to the Adobe documentation, by combining in-store purchase data with online purchase data using a phone number as the primary key, the retailer can create more accurate segments of customers based on their purchase behavior across channels. For example, the retailer can target in-store purchasers who have not bought online yet, or frequent purchasers who have bought both online and offline multiple times. These segments can be targeted in paid campaigns to increase conversion rates and reduce cost per acquisition (CPA). Reference: https://experienceleague.adobe.com/docs/experience-platform/segmentation/home.html?lang=en#segmentation

Two attributes that could be used to understand high-value prospects are household income and credit score. Household income indicates the financial capacity and spending power of a prospect, which could affect their interest in credit cards with crypto currency bonus offers. Credit score indicates the creditworthiness and risk level of a prospect, which could affect their eligibility and approval for credit cards with crypto currency bonus offers.

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