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
.
A known customer buys a TV that is delivered late. SAP Customer Data Platform is configured to
ingest the customer data for late deliveries so that the business can react and keep good customer
satisfaction metrics.
Which type of customer profile is best to use in this scenario?
C
Explanation:
The Unified Customer Profile within the SAP Customer Data Platform is designed to provide a
comprehensive view of the customer by unifying various types of data from multiple sources. This
profile type is best suited for scenarios where businesses need to react quickly to specific customer
situations, such as late deliveries, to maintain customer satisfaction. By leveraging the Unified
Customer Profile, businesses can access all relevant customer information, including activity
indicators and segments the customer is part of, which is essential for timely and effective customer
service.
Reference = The explanation aligns with the information provided in the SAP Customer Data Platform
documentation, particularly in the sections discussing customer profiles and identity resolution123
.
The Unified Customer Profile (UCP) is ideal for this scenario. Here's why:
Consolidated Data: The UCP integrates data from various sources (e.g., CRM, e-commerce, delivery
systems) to create a comprehensive, 360-degree view of the customer, including their purchase
history and the late delivery event.
Real-time Updates: The UCP can be updated in real-time as new data, like the late delivery
information, becomes available.
Actionable Insights: The UCP enables the business to quickly identify affected customers and trigger
appropriate actions for service recovery (e.g., personalized apologies, compensation), maintaining
customer satisfaction.
Reference:
SAP Help Portal: Unified Customer Profile in SAP CDP (Find the latest documentation on the SAP Help
Portal)
What would you use activity indicators as building blocks for? Note: There are 3 correct answers to
this question.
A B E
Explanation:
Activity indicators within the SAP Customer Data Platform are calculated metrics that measure the
performance of various business areas based on customer activities. They serve as foundational
components for constructing Customer Experience (CX) flows, building audiences for targeted
marketing, and marking entries in CX journey milestones. These indicators are recalculated
whenever relevant customer activity is ingested, allowing for dynamic segmentation and triggering
of CX flows or journey milestones based on customer behavior.
Reference = This information is corroborated by the SAP Help Portal documentation on Activity
Indicators, which outlines their role in gauging business performance and their application in CX
flows, audience building, and CX journey milestones1
.
Why does SAP Customer Data Platform provide two views of the customer?
C
Explanation:
The SAP Customer Data Platform supports two views of a single customer to ensure that the right
profile is available for every customer experience use case.
This is achieved through the use of
matching and merge rules that unify data from various sources to create a complete view of
customers. Reference = This explanation is aligned with the information provided in the SAP
Customer Data Platform documentation, which outlines the platform’s capabilities to connect
different types of customer data and generate rich customer insights1
.
What tools are supported by SAP Customer Data Platform to call external REST APIs? Note: There are
2 correct answers to this question.
B C
Explanation:
The SAP Customer Data Platform supports the use of the Generic Webservice Provider and
Connector Studio to call external REST APIs. The Generic Webservice Provider can call any external
REST API endpoints, and when the outbound action is executed, the SAP Customer Data Platform
prepares the data and sends it to the configured REST API endpoint.
The Connector Studio is
recommended for building integrations with REST applications1
.
Reference = This information is verified using the SAP Help Portal documentation on the Generic
REST API Connector1
.
You are importing orders into SAP Customer Data Platform. What is the recommended type of
schema to model it?
C
Explanation:
The recommended schema for modeling orders when importing them into the SAP Customer Data
Platform is the Activity schema. This schema is designed to contain all potential customer activities,
which include orders, service calls, service requests, marketing campaigns, registration, subscription,
and more.
The ‘Orders’ activity is specifically preconfigured in the Activities schema, and it is made
up of nodes that hold activity data such as order ID, currency description, order amount, and tax
amount1
.
Reference = The information is based on the SAP Customer Data Platform documentation,
particularly the section on the Activity Schema found in the SAP Help Portal1
.