I85PREP
⌘ K
Adobe RT-CDP Business Practitioner Pro study materials
Adobe RT-CDP Business Practitioner Pro study resources

Adobe RT-CDP Business Practitioner Pro practice questions

One question at a time. Build your Adobe RT-CDP Business Practitioner Pro understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Real-Time CDP overview and architecture

Which Adobe solution is primarily responsible for collecting and standardizing customer data before it is made available to other Experience Cloud applications?

  1. Adobe Target
  2. Adobe Campaign
  3. Adobe Experience Platform Correct answer.
  4. Adobe Analytics

Explanation

Adobe Experience Platform is the underlying data foundation that ingests, standardizes, and activates customer data for the broader Experience Cloud ecosystem. The other products are experience applications that consume data rather than serve as the central collection layer.

Question 2Real-Time CDP overview and architecture

In Real-Time CDP terminology, what is a 'profile'?

  1. A schema definition describing a class of data fields
  2. A saved SQL query that returns aggregated segment counts
  3. A real-time representation of an individual customer built from merged identity and attribute data Correct answer.
  4. A configuration template for destination connections

Explanation

A profile is the unified, real-time view of a single individual, assembled by merging identities and attributes from multiple sources. Schemas describe structure and destinations define outbound connections, so those are distinct concepts.

Question 3Real-Time CDP overview and architecture

Which component of Real-Time CDP is responsible for defining the structure and relationships of data that will be ingested?

  1. Merge policies
  2. Segments
  3. Destinations
  4. Schemas Correct answer.

Explanation

Schemas provide the formal structure, field definitions, and relationships that govern how incoming data is organized in the platform. Segments, destinations, and merge policies operate on data after it has been structured.

Question 4Real-Time CDP overview and architecture

What is the primary role of the identity graph in Real-Time CDP?

  1. To store the raw event payloads exactly as they were received
  2. To govern which destinations may receive profile data
  3. To link identifiers that belong to the same person into a single unified identity Correct answer.
  4. To calculate segment membership on a nightly schedule

Explanation

The identity graph resolves and links identifiers such as email, CRM ID, and ECID that refer to the same individual, enabling a unified profile. Raw storage, destination governance, and batch segment evaluation are handled by other capabilities.

Question 5Real-Time CDP overview and architecture

A marketer wants to define a group of customers who meet specific criteria so the group can be sent to an advertising destination. Which Real-Time CDP capability is used?

  1. Datasets
  2. Schemas
  3. Source connectors
  4. Audiences Correct answer.

Explanation

Audiences (segments) are the mechanism for defining populations based on profile criteria and are the unit that gets activated to destinations. Datasets and source connectors concern ingestion, and schemas concern structure.

Question 6Real-Time CDP overview and architecture

Which statement best describes the relationship between datasets and schemas in Real-Time CDP?

  1. A dataset conforms to a schema that defines the fields and data types it can hold Correct answer.
  2. A dataset may contain records governed by multiple unrelated schemas simultaneously
  3. A schema is created automatically from each dataset at ingestion time
  4. A schema stores the actual records while a dataset only stores metadata

Explanation

A dataset is a container for records and is bound to a schema that defines its structure and allowed data types. The schema describes shape, while the dataset holds the actual data.

Question 7Real-Time CDP overview and architecture

What does a merge policy control in Real-Time CDP?

  1. How conflicting attribute values from different data sources are resolved in a profile Correct answer.
  2. Which identities are permitted to enter the identity graph
  3. How often a destination receives an outbound file
  4. How long raw data is retained in the data lake

Explanation

A merge policy determines precedence and conflict resolution when multiple sources contribute attribute values to the same profile, and can also set recency rules. Destination scheduling, identity admission, and data retention are separate settings.

Question 8Real-Time CDP overview and architecture

Which term describes the process of sending audiences from Real-Time CDP to an external system such as an advertising platform or email provider?

  1. Modeling
  2. Activation Correct answer.
  3. Federation
  4. Ingestion

Explanation

Activation is the outbound step in which audiences and their profile attributes are delivered to configured destinations. Ingestion is inbound data collection, and the other terms refer to different capabilities.

Question 9Real-Time CDP overview and architecture

A company ingests website clickstream events and wants profiles updated with near-immediate visibility for downstream personalization. Which processing approach should be used?

  1. Federated query of an external warehouse
  2. Manual CSV upload
  3. Streaming ingestion Correct answer.
  4. Batch ingestion of a nightly file

Explanation

Streaming ingestion processes events continuously so profile data becomes available with low latency, which suits real-time personalization. Batch, manual uploads, and federation introduce delay or do not populate the profile directly.

Question 10Real-Time CDP overview and architecture

What distinguishes a 'union schema' from a base schema in Real-Time CDP?

  1. It defines destination credentials for outbound connections
  2. It combines fields from multiple schemas that share the same class into one view Correct answer.
  3. It removes personally identifiable information before storage
  4. It is the only schema type that can be used for streaming ingestion

Explanation

A union schema aggregates the fields of all schemas sharing a class, providing a consolidated view used for profile enablement. It is not tied to ingestion mode, privacy redaction, or destination setup.

Question 11Real-Time CDP overview and architecture

An architect needs to bring in CRM records that include a stable customer ID and then combine them with anonymous web identifiers. Which two capabilities are most central to this requirement?

  1. Alerting rules and audit logs
  2. Identity namespaces and the identity graph Correct answer.
  3. Merge policies and destination schedules
  4. Data retention policies and sandbox limits

Explanation

Identity namespaces label the different identifier types, and the identity graph links them so CRM and anonymous web activity resolve to the same profile. The other pairs address governance, operations, or monitoring rather than identity resolution.

Question 12Real-Time CDP overview and architecture

What is the purpose of a data source connector in Real-Time CDP?

  1. To deliver an audience to an external marketing system
  2. To define the schema class used for profile data
  3. To ingest data from an external system into a dataset in the platform Correct answer.
  4. To compute segment membership on a schedule

Explanation

Source connectors establish inbound data flows from external systems into datasets. Delivering audiences outbound is a destination function, and schema and segmentation are separate capabilities.

Question 13Real-Time CDP overview and architecture

A team needs to ensure that a specific attribute from the CRM source always wins over the same attribute from a web source when both are present. Where is this configured?

  1. In the destination's attribute mapping
  2. In the identity namespace settings
  3. In a merge policy using dataset precedence Correct answer.
  4. In the schema's field group ordering

Explanation

Merge policies determine which dataset or source takes precedence when attribute values conflict across sources. Destination mapping only controls what is sent outbound, and namespaces and field groups do not resolve value conflicts.

Question 14Real-Time CDP overview and architecture

Which of the following best describes the difference between a segment and a destination?

  1. A segment defines who qualifies, while a destination defines where that population is delivered Correct answer.
  2. A segment is a schema construct, while a destination is a dataset construct
  3. A segment defines where data is delivered, while a destination defines who qualifies
  4. A segment stores raw events, while a destination stores profile attributes

Explanation

Segments answer the 'who' by defining qualifying criteria, and destinations answer the 'where' by specifying the outbound system and payload. The other options either reverse or misclassify these roles.

Question 15Real-Time CDP overview and architecture

What is the function of a sandbox in Real-Time CDP?

  1. To accelerate streaming ingestion throughput
  2. To encrypt profile data at rest within a dataset
  3. To define the retention period for raw event data
  4. To provide an isolated environment for developing and testing without affecting production data Correct answer.

Explanation

Sandboxes isolate development, testing, and production work so that objects and data in one environment do not interfere with another. Encryption, throughput, and retention are separate technical or governance concerns.

Question 16Real-Time CDP overview and architecture

A retailer wants to suppress customers who purchased recently from a re-engagement campaign. Which capability enables this within the platform?

  1. Changing the merge policy to ignore purchase data
  2. Increasing the dataset retention period
  3. Building an audience that excludes recent purchasers and activating it to the campaign destination Correct answer.
  4. Creating a new schema that omits purchase fields

Explanation

Suppression is achieved by defining audience criteria that exclude the unwanted population and then activating that audience. Schema changes, merge policy changes, and retention settings do not filter campaign recipients.

Question 17Real-Time CDP overview and architecture

Which statement accurately describes streaming segmentation in Real-Time CDP?

  1. Audience membership is evaluated once per month across all profiles
  2. Audience membership is recalculated only when a user manually triggers a run
  3. Audience membership is computed only in the destination system
  4. Audience membership is evaluated as new data arrives, enabling timely activation Correct answer.

Explanation

Streaming segmentation continuously evaluates qualifying profiles as events arrive, so membership updates with low latency. Manual, monthly, or destination-side evaluation describes other, slower patterns.

Question 18Real-Time CDP overview and architecture

An organization wants to use data from an external data warehouse for analysis without copying the records into the platform's data lake. Which capability supports this?

  1. Streaming ingestion through the Edge Network
  2. Batch ingestion through a cloud storage source
  3. Profile merge through a merge policy
  4. Federated audience composition querying the external warehouse Correct answer.

Explanation

Federated capabilities let you query external data sources in place and use the results for audience composition without bulk-copying records into the platform. Ingestion copies data in, and merge policies operate on existing profile data.

Question 19Real-Time CDP overview and architecture

Which two platform services work together to turn raw ingested records into a unified, activatable customer profile?

  1. Identity resolution and the profile service Correct answer.
  2. Destination scheduling and file formatting
  3. Alerting and audit logging
  4. Schema registry and destination credentials

Explanation

Identity resolution links identifiers across sources, and the profile service assembles and maintains the unified profile that can be activated. The other pairs concern monitoring, outbound delivery mechanics, or configuration rather than profile construction.

Question 20Real-Time CDP overview and architecture

What role do field groups play in a Real-Time CDP schema?

  1. They determine which destinations a schema may be activated to
  2. They provide reusable collections of fields that can be added to a schema Correct answer.
  3. They enforce identity resolution rules across datasets
  4. They set the data retention period for the schema's records

Explanation

Field groups are reusable components containing a set of fields, often aligned to a standard like XDM, that can be composed into schemas. They do not control destinations, identity resolution, or retention.

Question 21Real-Time CDP overview and architecture

A company has three source systems each supplying a customer's loyalty tier. The values conflict, and the business requires the value with the most recent timestamp to be used. Which merge policy option addresses this?

  1. A timestamp-ordered merge policy that selects the most recent value Correct answer.
  2. An identity namespace policy that links loyalty identifiers
  3. A destination mapping that overwrites values at send time
  4. A dataset precedence policy that always favors the first dataset ingested

Explanation

A timestamp-ordered merge policy resolves conflicts by selecting the value with the latest timestamp, matching the requirement. Dataset precedence uses a fixed order, and the other options address identity or outbound mapping rather than recency-based conflict resolution.

Question 22Real-Time CDP overview and architecture

Which consideration most directly determines whether an audience can be evaluated using streaming segmentation rather than batch segmentation?

  1. Whether the sandbox is a production sandbox
  2. Whether the schema uses a standard field group
  3. Whether the destination supports file-based delivery
  4. Whether the audience's criteria can be evaluated from continuously arriving event data Correct answer.

Explanation

Streaming segmentation requires that the qualifying logic can be evaluated against incoming event data as it arrives. Destination delivery format, field group choice, and sandbox type do not determine eligibility for streaming evaluation.

Question 23Real-Time CDP overview and architecture

An architect observes that a profile shows an outdated email address even though a newer value exists in one source. Which configuration is the most likely cause?

  1. The destination's payload mapping excludes email
  2. The merge policy's precedence favors the source holding the older value Correct answer.
  3. The identity graph has too many linked namespaces
  4. The dataset retention period is too short

Explanation

When sources disagree, the merge policy decides which value wins; a precedence rule favoring the stale source explains the outdated value. Destination mapping, namespace count, and retention do not determine the stored profile value.

Question 24Real-Time CDP overview and architecture

Which scenario best illustrates why identity resolution is essential before activation?

  1. The same customer appears under separate email and device identifiers that must be recognized as one person Correct answer.
  2. A destination requires a specific file format for delivery
  3. A sandbox must be reset before a new project begins
  4. A schema needs additional custom fields for a new data source

Explanation

Without identity resolution, the same individual fragmented across identifiers would be counted and targeted as multiple people, undermining activation accuracy. File formats, schema changes, and sandbox resets are unrelated to unifying identities.

Question 25Real-Time CDP overview and architecture

A team wants to restrict which outbound destinations may receive profiles containing sensitive attributes. Which platform capability is designed for this?

  1. Schema field group composition
  2. Data governance policies and labels applied to datasets and destinations Correct answer.
  3. Streaming ingestion throughput settings
  4. Merge policy precedence rules

Explanation

Governance uses labels on data and enforcement policies on destinations to control which sensitive data may flow to which systems. Merge policies, ingestion settings, and field groups do not enforce outbound data restrictions.

Question 26Real-Time CDP overview and architecture

Which capability of Real-Time CDP is primarily responsible for maintaining a continuously updated, person-level record assembled from multiple sources?

  1. The flow service
  2. The profile store Correct answer.
  3. The query service
  4. The audit log service

Explanation

The profile store ingests and merges data from connected sources to maintain a current, unified record per person. The other services handle querying, ingestion orchestration, and event tracking rather than assembling the unified record.

Question 27Real-Time CDP overview and architecture

Which description best captures the role of the identity graph in Real-Time CDP?

  1. It links identifiers belonging to the same person across devices and sources Correct answer.
  2. It ranks audiences by predicted conversion likelihood
  3. It stores the namespace definitions used to label identifiers
  4. It encrypts profile attributes before they are activated

Explanation

The identity graph maintains the relationships between identifiers so records from different sources can be stitched into one profile. It works with namespaces but is not the definition store, and it does not score audiences or encrypt attributes.

Question 28Real-Time CDP overview and architecture

Which component of the Real-Time CDP architecture is responsible for defining the structure of records that will be ingested into the profile store?

  1. The activation schedule
  2. The experience data model schema Correct answer.
  3. The merge policy
  4. The destination catalog

Explanation

Schemas built on the experience data model describe the fields and types of incoming records and govern how they can be used. Destinations and schedules govern outbound delivery, and merge policies govern how records are combined rather than how they are structured.

Question 29Real-Time CDP overview and architecture

What is the primary purpose of the Real-Time CDP edge network in the data collection path?

  1. To host the profile store in each region
  2. To batch source files before ingestion
  3. To store activated audience membership history
  4. To collect and route incoming event data close to the user Correct answer.

Explanation

The edge network receives data from client-side collection and routes it onward with low latency. It does not perform batch file handling, host the profile store, or retain activation history.

Question 30Real-Time CDP overview and architecture

A company ingests purchase events from its mobile app and wants those events to influence audience membership within minutes. Which architectural characteristic of Real-Time CDP makes this possible?

  1. Streaming ingestion feeding an updatable profile store Correct answer.
  2. Nightly batch ingestion into a data lake
  3. Manual segment refresh triggered by an analyst
  4. Destination-side filtering applied at send time

Explanation

Streaming ingestion delivers events to the profile store, which updates profile attributes and evaluates eligible audiences continuously. Batch ingestion and manual refresh introduce delays, and destination-side filtering occurs after evaluation.

Question 31Real-Time CDP overview and architecture

An architect wants to bring in records from an external system using a scheduled file transfer rather than an event stream. Which ingestion pattern does this describe?

  1. Batch ingestion Correct answer.
  2. Streaming ingestion
  3. Synchronous ingestion
  4. Edge ingestion

Explanation

Batch ingestion processes records on a schedule from files or connectors, in contrast to continuous event streams. Streaming and edge ingestion refer to near-real-time event paths rather than scheduled file transfers.

Question 32Real-Time CDP overview and architecture

A team notices that one source sends a customer's identifier under a namespace that differs from the namespace used by another source for the same person. What must be configured for the identity graph to link these records?

  1. An identity namespace mapping that aligns the identifiers Correct answer.
  2. A destination that accepts both namespaces
  3. A field group that renames the attribute
  4. A merge policy that prefers one source

Explanation

Identifiers must be expressed in a consistent namespace for the identity graph to recognize them as the same person. Merge policies resolve attribute conflicts, destinations govern delivery, and field groups describe attributes rather than identifier alignment.

Question 33Real-Time CDP overview and architecture

Which statement best describes how the Real-Time CDP profile store treats historical event data compared with current profile attributes?

  1. Historical events are retained and queryable while attributes reflect the latest state Correct answer.
  2. Historical events are stored only in the destination catalog
  3. Historical events are discarded once attributes are updated
  4. Historical events replace profile attributes on every update

Explanation

The profile store keeps ingested experience events available while profile attributes reflect the most recent merged state. This separation lets teams analyze behavior history and act on current attributes.

Question 34Real-Time CDP overview and architecture

A marketing team wants to know which customer attributes exist in the profile store and how they are typed before building an audience. Which architectural element should they inspect?

  1. The schema and its field groups Correct answer.
  2. The dataflow run history
  3. The destination configuration
  4. The audience activation schedule

Explanation

Schemas and their field groups define the attributes, their types, and their structure in the profile store. Destinations, dataflow history, and schedules concern data movement and delivery rather than attribute definitions.

Question 35Real-Time CDP overview and architecture

Which platform service evaluates audience rules against profiles and maintains audience membership over time?

  1. The flow service
  2. The segmentation service Correct answer.
  3. The catalog service
  4. The audit service

Explanation

The segmentation service evaluates audience definitions against profiles and updates membership as profiles change. The flow service moves data, the audit service records activity, and the catalog service tracks assets and metadata.

Question 36Real-Time CDP overview and architecture

An organization wants to confirm that data arriving from a source was successfully written to its target dataset before enabling activation. Which architectural artifact provides this evidence?

  1. The identity namespace list
  2. The merge policy evaluation report
  3. The destination audience count
  4. The dataflow run record Correct answer.

Explanation

Dataflow run records report the outcome of ingestion runs, including whether data reached its target dataset. Merge policies, destination audience counts, and namespace lists do not document ingestion success.

Question 37Real-Time CDP overview and architecture

Which statement best explains why Real-Time CDP separates the profile store from the data lake?

  1. The profile store is used for reporting, while the data lake is used for activation
  2. The profile store holds merged person records optimized for activation, while the data lake retains broader raw data for analysis Correct answer.
  3. The profile store stores only anonymous identifiers, while the data lake stores only known customers
  4. The profile store and the data lake hold identical data and differ only in retention length

Explanation

The profile store is optimized for identity-resolved, activatable person records, while the data lake retains broader ingested data for query and analysis. They serve different purposes rather than duplicating each other or splitting by identity type.

Question 38Real-Time CDP overview and architecture

A company needs to guarantee that profiles containing sensitive health attributes are never sent to a particular advertising destination. Which architectural control most directly enforces this?

  1. A merge policy that excludes the health attribute
  2. A dataflow schedule that delays ingestion
  3. A data governance policy that restricts the attribute from the destination Correct answer.
  4. A schema field group that renames the attribute

Explanation

Data governance policies define usage labels and restrict attributes from being activated to specific destinations. Merge policies affect attribute resolution, field groups affect structure, and schedules affect timing, none of which enforce destination-level restrictions.

Question 39Real-Time CDP overview and architecture

An architect must explain why an audience defined on a rarely updated batch attribute cannot be evaluated continuously. Which architectural constraint explains this?

  1. The profile store cannot store batch attributes
  2. The identity graph excludes batch-sourced identifiers
  3. Streaming evaluation depends on incoming events that update the attribute in near real time Correct answer.
  4. Destinations reject audiences built on batch attributes

Explanation

Continuous evaluation depends on the arrival of events or updates that trigger re-evaluation, so an attribute refreshed only by batch runs changes infrequently. The profile store can hold batch attributes, and destinations and the identity graph do not impose this evaluation constraint.

Question 40Real-Time CDP overview and architecture

A business analyst needs to combine profile data with event history to understand which behaviors precede a purchase, without exporting data to an external system. Which architectural capability supports this?

  1. The audit log recording user activity
  2. The query service working against the data lake and profile data Correct answer.
  3. The edge network routing client events
  4. The destination catalog listing available integrations

Explanation

The query service allows SQL analysis across ingested datasets and profile data within the platform. The destination catalog, edge network, and audit log serve delivery, collection, and compliance purposes rather than analytical querying.

Question 41Data ingestion, schemas, identities, and governance

In Adobe Experience Platform, which construct defines the structure and data types of records that can be ingested into a dataset?

  1. An XDM schema Correct answer.
  2. A destination flow
  3. A data usage label
  4. A merge policy

Explanation

An XDM schema acts as the contract describing the fields, structure, and data types that records must conform to. Datasets are then built on top of a schema so ingested data is validated against it.

Question 42Data ingestion, schemas, identities, and governance

Which identity service component is used to link identities that are known to belong to the same individual across sources?

  1. Identity namespace
  2. Identity field group
  3. Identity graph Correct answer.
  4. Identity policy

Explanation

The identity graph stores the relationships between identity values that have been stitched together for a person. Namespaces classify the type of identity, but the graph holds the links.

Question 43Data ingestion, schemas, identities, and governance

A practitioner wants to send streaming web events into Platform and have them validated immediately against the schema. Which ingestion method fits best?

  1. Scheduled SFTP source connector
  2. Streaming ingestion via the HTTP API Correct answer.
  3. Manual dataset upload through the UI
  4. Batch ingestion via a CSV file

Explanation

Streaming ingestion accepts records in near real time and validates them against the dataset schema upon receipt. Batch and file-based methods deliver on a schedule and are not designed for immediate validation of live events.

Question 44Data ingestion, schemas, identities, and governance

What is the purpose of a data usage label in Adobe Experience Platform?

  1. To encrypt sensitive fields at rest
  2. To describe the sensitivity of data so policies can govern its use Correct answer.
  3. To define the primary identity of a dataset
  4. To set the retention period of a dataset

Explanation

Data usage labels describe the nature and sensitivity of data, and policy enforcement uses them to restrict downstream usage. They are governance metadata rather than encryption or retention controls.

Question 45Data ingestion, schemas, identities, and governance

Which schema class should be used for time-series event data such as web clicks or purchases?

  1. XDM Individual Profile
  2. XDM Record
  3. XDM Segment Membership
  4. XDM ExperienceEvent Correct answer.

Explanation

The XDM ExperienceEvent class models time-series event data with a timestamp and event context. Profile-class schemas instead represent the current state of an individual.

Question 46Data ingestion, schemas, identities, and governance

Which field group would a practitioner add to capture standard identity information like email and phone on a profile schema?

  1. Environment Details
  2. Personal Contact Details Correct answer.
  3. Commerce Details
  4. Demographic Details

Explanation

Personal Contact Details provides standard fields such as email address and phone number, which are commonly used as identity values. The other field groups cover unrelated attribute areas.

Question 47Data ingestion, schemas, identities, and governance

A dataset must accept records where the identity value is the customer's email address. What must be configured on the schema before ingestion?

  1. A relationship to a lookup schema
  2. An identity descriptor marking the email field as an identity Correct answer.
  3. A data usage label of 'Contract'
  4. A merge policy referencing the email namespace

Explanation

An identity descriptor tells the Identity Service that a field holds identity values, and the field must reference an identity namespace. Labels, merge policies, and relationships do not declare identity.

Question 48Data ingestion, schemas, identities, and governance

What does a primary identity descriptor determine for a dataset?

  1. Which identity is used when multiple identities exist in the same record Correct answer.
  2. Which field is required in every schema field group
  3. Which merge policy is applied to the dataset
  4. Which namespace is used when records lack any identity

Explanation

The primary identity descriptor designates which identity takes precedence when a record contains more than one identity value. It does not supply a fallback identity or select a merge policy.

Question 49Data ingestion, schemas, identities, and governance

A governance policy must block a dataset labeled with a sensitive health label from being used in marketing activation. Which Platform capability enforces this?

  1. Streaming ingestion limits
  2. Data usage policies Correct answer.
  3. Dataset retention rules
  4. Schema field groups

Explanation

Data usage policies define rules that combine usage labels with allowed actions, and enforcement blocks actions that violate them. Retention, field groups, and ingestion limits do not govern downstream usage.

Question 50Data ingestion, schemas, identities, and governance

Which statement describes the relationship between a schema, a dataset, and ingested records?

  1. A schema references a dataset, and datasets define the fields records must match
  2. A dataset references a schema, and records ingested into the dataset must conform to it Correct answer.
  3. A dataset can reference multiple schemas simultaneously for the same records
  4. Records define the schema, and datasets are created automatically per record type

Explanation

A dataset is created against a single schema, and incoming records are validated against that schema's structure. The schema is the definition; the dataset is the container.