The dimensional entity that exists within the Real-Time Customer Profile data store (also sometimes referred to as lookup or classification schemas) is primarily used for what two purposes? (Choose two.)
Correct Answer: A,B
Explanation A dimensional entity is a type of entity that exists within the Real-Time Customer Profile data store and describes a business entity or concept that is not directly related to a customer, such as product, location, or campaign. A dimensional entity is primarily used for two purposes: * It helps simplify the modeling process in XDM by avoiding having to restate common data on either the event or the traits of a profile. For example, instead of repeating the product name, price, and description on every product view event, the developer can create a product dimensional entity and reference it by its ID on the event. * It allows Journey Optimizer to leverage the data for audience and segment qualification initiated customer journeys. For example, the developer can create a segment based on customers who viewed products from a certain category or location, or who interacted with a certain campaign. The other options are not valid or relevant purposes of a dimensional entity. A dimensional entity is not leveraged during batch segmentation jobs that are run within the Real-Time Customer Profile, as these jobs are based on profile data, not dimensional data. A dimensional entity does not ensure that data is optimally stored to deliver real-time experiences and segmentation, as this is a function of the Real-Time Customer Profile data store, not the dimensional entity itself. References: https://experienceleague.adobe.com/docs/experience-platform/profile/home.html?lang=en#dimensional-en https://experienceleague.adobe.com/docs/journey-optimizer/using/get-started/data-ingestion.html?lang=en
