What are the possible application identifier conflict policy options when ingesting customer data
using the Unified Customer Profile? Note: There are 2 correct answers to this question.
AC
Explanation:
In the context of SAP Customer Data Platform and specifically when dealing with the Unified
Customer Profile, handling conflicts during data ingestion is critical for maintaining data integrity and
coherence. The possible application identifier conflict policy options are designed to provide flexible
handling of such conflicts based on the business requirements.
A . Raise an error and abort the entire ingestion operation: This option is used when the system
encounters a conflict with the application identifiers during the ingestion process. The approach here
is to prioritize data integrity by stopping the ingestion process if there's any ambiguity or conflict in
the identifiers. This ensures that no erroneous data is incorporated into the Unified Customer Profile,
maintaining its accuracy and reliability.
C . Create new Customer Profile: When a conflict is detected with application identifiers, another
approach is to create a new customer profile. This option is chosen in scenarios where the incoming
data is considered to be representing a new customer entity, and therefore, warrants the creation of
a new profile to avoid overwriting or merging with existing data inaccurately.
Options B and D are not standard practices within the SAP Customer Data Platform for handling
identifier conflicts during data ingestion into the Unified Customer Profile, as they could lead to data
duplication or loss, compromising data quality.
Reference:
SAP Customer Data Cloud documentation on data ingestion and conflict resolution.
SAP help articles and tutorials related to the Unified Customer Profile in the SAP Customer Data
Platform.
Which of the following flow controls are supported in CX flows? Note: There are 2 correct answers to
this question.
B D
Explanation:
The SAP Customer Data Platform supports various flow controls within CX flows to manage the
customer journey. Specifically, the ‘Wait Until Duration’ control allows the stalling of a CX flow’s path
for a specified period or until a certain date and time. The ‘Join’ control enables the merging of
different paths of a CX flow into one. These controls are essential for orchestrating complex customer
interactions and ensuring timely engagements.
Reference = The information is verified and matched with the details provided in the SAP Customer
Data Platform documentation and learning resources, particularly the SAP Help Portal and SAP
Learning Journey123
.
You are creating a new legacy variant business unit.
Which matching rules does SAP Customer Data Platform preconfigure for both the Contextual Profile
view and the Unified Profile view? Note: There are 3 correct answers to this question.
B C D
Explanation:
The SAP Customer Data Platform preconfigures matching rules to ensure accurate customer data
matching. These rules are applied sequentially; if no match is found using the first identifier, the next
identifier is tried. The predefined matching rules include:
Match Customers based on masterDataId
Match Customers based on crmId
Match Customers based on ciamId
This setup helps in identifying and matching customer data accurately for both the Contextual Profile
view and the Unified Profile view.
Reference = The information is verified and matched with the details provided in the SAP Customer
Data Platform documentation and learning resources12
.
For an incoming event, what value can SAP Customer Data Platform store for an active processing
purpose status field?
C
Explanation:
In the context of the SAP Customer Data Platform, the active processing purpose status for an
incoming event is always attached to the event. This status indicates whether the data is allowed to
be stored in the system, and which data may be sent out to destination applications. The processing
purpose can be dynamic, meaning it is part of the incoming event’s data model and is saved to the
customer profile with the status and timestamp data that was sent with the event. This is achieved by
mapping the event purpose nodes to the data privacy framework within the platform.
Reference = The information is based on the SAP Help Portal documentation on Processing Purposes,
which details the use cases, core concepts, and data governance enforcement related to processing
purposes within the SAP Customer Data Platform1
.
The customer schema of a group includes two predefined attributes that can be used for B2B
scenarios. Which one of the following attributes is one of the two predefined ones?
D
Explanation:
In B2B scenarios within the SAP Customer Data Platform, accurately identifying and managing
business entities is crucial. The customer schema is designed to accommodate the complexities of
B2B interactions, including the need to manage relationships between individual contacts and their
associated organizations.
D . BusinessId: This predefined attribute is essential in B2B scenarios, as it serves as a unique
identifier for business entities within the platform. The BusinessId allows for the clear distinction and
management of business accounts, facilitating effective B2B data handling, segmentation, and
personalized engagement strategies.
The inclusion of predefined attributes like BusinessId in the customer schema underscores the
platform's capability to cater to both B2C and B2B environments, providing the necessary tools for
comprehensive customer data management.
Reference:
SAP Customer Data Platform documentation on customer schemas and B2B capabilities.
SAP help articles and best practices for managing B2B scenarios within the SAP Customer Data
Platform.
You need to ingest some customer data into SAP Customer Data Platform while observing data
compliance regulations.
What needs to be configured inside SAP Customer Data Platform before you can do this?
D
Explanation:
Before ingesting customer data into the SAP Customer Data Platform (CDP), it is essential to
configure processing purposes within the system. This is a built-in mechanism that identifies the
different purposes for handling customer data that streams into and out of the system. The
processing of personal data is governed by regional and local regulations, such as GDPR and CCPA.
The CDP ingestion process allows businesses to ensure compliance with these regulations,
restrictions, and policies applicable to customer data usage. It is important to note that the CDP
ingestion process does not collect, audit, or handle the actual collection of processing purposes.
Instead, it allows for storing those collected purposes and applying data governance based on those
purposes. In the context of CDP, the processing purpose is sent as data points in an event from a
source, and multiple processing purposes may be defined per business unit. Only those processing
purposes needed for managing customer data in CDP should be added.
Reference = The detailed explanation is based on information found in the SAP Help Portal,
specifically within the documentation for processing purposes in the SAP Customer Data Platform1
.
You want to authenticate requests to event listeners created by the source server application. How
can you do this? Note: There are 2 correct answers to this question.
B D
Explanation:
When using a server application to make API calls to the SAP Customer Data Platform, you can
authenticate requests to event listeners by passing a constructed JWT as the bearer token or by using
the user key and secret key as parameters. The use of an asymmetric RSA key pair is also mentioned,
which is typically involved in the creation of a JWT. However, passing the SSL certificate of the client
or a one-time password generated by the REST API endpoint is not specified as a method for
authenticating these requests.
Reference = The information is based on the SAP Customer Data Platform documentation, which
details the methods for signing requests to the platform1
.
Which functionalities are always used when ingesting customer data into SAP Customer Data
Platform? Note: There are 2 correct answers to this question.
A D
Explanation:
The SAP Customer Data Platform ingests data from various source applications to build a coherent
view of the customers. It defines a customer schema to create a common data model for all incoming
customer data. Events are also a part of the data ingestion process, as they represent the actions
taken by customers and are crucial for creating a complete customer profile. Reference =
SAP
Customer Data Platform | SAP Help Portal
,
How does SAP Customer Data Platform do it? - SAP
Learning
Which of the following can be used as audience conditions? Note: There are 3 correct answers to this
question.
C D E
Explanation:
In the SAP Customer Data Platform, audiences are groups of customers that marketers can target in
marketing campaigns. Marketers build audiences by applying conditions to profile attributes,
segments, and activity indicators. These conditions help in defining the specific characteristics of the
audience members based on their profiles and behaviors. Reference =
Audiences | SAP Help
Portal
,
Creating Audiences - SAP Learning
Which of the following describes a business unit in SAP Customer Data Platform?
B
Explanation:
In the SAP Customer Data Platform, a business unit is defined as the part of a business that is tasked
with maintaining continuous business relationships with customers within a specific market. This
definition implies that a business unit is not just a segment or a division, but a functional entity
within the organization that directly interacts with the customer base.
Furthermore, it is important to
note that a single business unit can encompass multiple brands, indicating that it can operate across
different product lines or service offerings under the broader corporate umbrella. Reference = This
information is corroborated by the SAP Help Portal, which provides a clear definition of a business
unit within the context of the SAP Customer Data Platform1
.
Which steps are mandatory to create a processing purpose? Note: There are 3 correct answers to this
question.
A C D
Explanation:
To create a processing purpose within the SAP Customer Data Platform, the mandatory steps include:
Processing purpose definition: This is the core step where the actual purpose for processing personal
data is defined.
Inbound data governance: This step ensures that the data being ingested into the system complies
with the defined processing purposes.
Outbound data governance: This step ensures that the data being sent out of the system adheres to
the processing purposes.
These steps are crucial for complying with regional and local regulations, such as GDPR and CCPA,
and for applying privacy and trust to the data streaming into and out of the CDP.
Reference = The information is based on the SAP Customer Data Platform documentation which
outlines the process of creating a new processing purpose and configuring inbound and outbound
data governance to enforce data governance12
.
Which of the following are steps in a CX flow? Note: There are 3 correct answers to this question.
A C D
Explanation:
In the context of SAP Customer Data Platform, a CX flow is designed using logic blocks that may
include triggers, actions, decisions, and flow controls. Triggers are the entry points or conditions that
set the context of the CX flow experience. Decisions split a CX flow based on a simple Yes-No logic so
that different paths can be created within the CX flow.
Flow controls help set the beginning, end,
duration, and frequency of communication with a customer on their journey. Reference = The
information is verified from the SAP Learning Journeys and SAP Help Portal, which detail the
components of a CX flow, including triggers, actions, decisions, and flow controls12
.
You need to perform a quick ingestion test to evaluate your configuration. What is the simplest
recommended way of doing this?
D
Explanation:
The simplest recommended way to perform a quick ingestion test to evaluate your configuration is
by using the Event Playground. The Event Playground allows you to easily test application events,
actions, and CX flows by ingesting a test event with test values you provide via a dedicated form. The
submitted test data runs through the entire CDP flow, which is then displayed in the playground as a
visualization of that flow and its results.
It helps identify errors in the different steps: ingestion,
schema mapping, identity resolution, CX flow steps, CX flow actions, providing transparency and
confidence in the flow of data1
.
Reference =
SAP Help Portal: Event Playground1
.
Which tab in the customer dashboard shows the segments of the customer profile?
B
Explanation:
In the SAP Customer Data Platform, the customer dashboard provides a comprehensive view of
individual customer profiles, including their attributes, behaviors, and interactions with the brand. To
view the segments a customer profile belongs to:
B . Overview: The "Overview" tab in the customer dashboard is designed to provide a holistic view of
the customer profile, which includes the segments the customer is part of. This tab aggregates
essential information about the customer, including demographic details, interaction history, and
their categorization into various segments based on predefined criteria. This segmentation allows
businesses to understand customer preferences and behaviors better, enabling targeted engagement
strategies.
The "Overview" tab serves as the central hub for accessing a broad spectrum of customer data,
making it an invaluable tool for gaining insights and driving personalized customer experiences.
Reference:
SAP Customer Data Platform user guide on navigating the customer dashboard.
Tutorials on customer segmentation and profile management within the SAP Customer Data
Platform.
How many conditions are allowed per single segment?
A
Explanation:
In the SAP Customer Data Platform, a single segment can be defined with a maximum of 200
conditions. This allows for the creation of highly customized customer segments by using various
‘include/exclude’ and ‘and/or’ conditions, as well as different operators. These segments are
evaluated in real-time whenever a customer profile is updated, ensuring that the segmentation is
always current and applied to both the contextual profile and the unified customer profile views.
Reference = This information is confirmed by the SAP Help Portal documentation on Segments and
Segment Attributes within the SAP Customer Data Platform12
.