Adobe AD0-E602 Practice Test - Questions Answers, Page 5

According to the Adobe documentation2, a union schema is a feature of Real-Time CDP that can be used to view the amalgamation of all the fields contained within multiple schemas sharing the same class. A union schema is automatically generated by the platform and reflects the latest changes in the underlying schemas. A union schema can be used to create segments or explore profiles across different datasets. Reference: 2 https://experienceleague.adobe.com/docs/experienceplatform/profile/home.html?lang=en#union-schemas

According to the Adobe documentation3, 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.

Reference: 3 https://experienceleague.adobe.com/docs/experience-platform/profile/identityservice/overview.html?lang=en#identity-service-overview

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. Reference: https://experienceleague.adobe.com/docs/experienceplatform/ profile/identity-service/namespace.html?lang=en#custom-namespaces

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. Reference:

https://experienceleague.adobe.com/docs/experience-platform/profile/identityservice/schema.html?lang=en#primary-identity

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. Reference:

https://experienceleague.adobe.com/docs/experience-platform/profile/mergepolicies/methods.html?lang=en#timestamp-ordered

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, 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.

Reference: https://experienceleague.adobe.com/docs/experienceplatform/profile/ui/overview.html?lang=en#profiles-overview-dashboard

According to the Adobe documentation, Profiles > Browse is where a Real-Time CDP Business

Practitioner can go to search for Profiles by Merge Policy in the UI. Profiles > Browse allows the user to search for individual profiles or groups of profiles based on various criteria, such as identity value, namespace, dataset, or merge policy. The user can also view the profile details and timeline for each profile. Reference: https://experienceleague.adobe.com/docs/experienceplatform/profile/ui/browse.html?lang=en#searching-for-profiles

According to the Adobe documentation, merge policies are a feature of Real-Time CDP that can be used to determine how data will be prioritized and what data will be combined to create a unified view of a customer profile. Merge policies define the rules and logic for merging profile attributes from different data sources into a single profile. Merge policies can be either predefined or custom, and they can be applied at the dataset level or the tenant level. Reference:

https://experienceleague.adobe.com/docs/experience-platform/profile/mergepolicies/overview.html?lang=en#merge-policies-overview