A. Split
B. Notify
C. Wait until duration
D. Join
A. Merge Rules can only be used with Unified Customer Profile type.
B. If a data conflict occurs, you can decide if a new Customer Profile is created or the event data is discarded.
C. In the Unified Customer Profile, you can decide if more than one value is saved for an attribute.
D. Merge Rules can be applied to non-identifier fields.
A. It enables creation of CX Flows and Journeys for new customers.
B. It enables creation of ETL jobs and data pipelines for data ingestion.
C. It enables creation of Matching Rules for joining different pieces of customer data.
D. It enables creation of templates for source/destination REST API applications.
A. Decide whether more than one value can be saved for an attribute
B. Decide whether to concatenate the incoming value with the existing value of the same attribute
C. Decide whether to override existing data, based on the quality of the incoming and existing data
D. Decide what to do if a data conflict occurs for an identifier attribute
A. 200
B. 100
C. 300
D. 50
A. System-defined rules are based on strongest identifier attributes.
B. System-defined rules can be re-ordered for the Contextual Profile.
C. User-defined rules can be based on the firstName attribute.
D. System-defined rules can be edited for the Unified Customer Profile.
E. System-defined rules can be deleted for the Unified Customer Profile.
A. Customer churn
B. Customer order value
C. Customer volume
D. Customer lifetime value
A. Imported data file size should not exceed 250 MB.
B. Metadata fields should be used during an import process.
C. The SAP Customer Data Platform instance should be switched to maintenance mode during an import process.
D. CX flows should be deactivated for data imports.
E. Activities containing segments and activity indicator information should be imported individually.
