I85PREP
⌘ K
Adobe Real-Time CDP Developer Expert study materials
Adobe Real-Time CDP Developer Expert study resources

Adobe Real-Time CDP Developer Expert practice questions

One question at a time. Build your Adobe Real-Time CDP Developer Expert 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 1Data ingestion and schema design

Which construct in Adobe Experience Platform defines the structure, data types, and identity settings for a class of records that a dataset can hold?

  1. A dataset
  2. A dataflow run
  3. A schema Correct answer.
  4. A segment definition

Explanation

A schema is the declarative description of the shape of data, including fields, data types, and identity/primary-key metadata. Datasets are containers that reference a schema; they do not define the structure themselves.

Question 2Data ingestion and schema design

Which XDM class should be used for a dataset that stores time-series event data such as web clicks and purchases?

  1. XDM ExperienceEvent Correct answer.
  2. A union schema
  3. A custom class extending nothing
  4. XDM Individual Profile

Explanation

The XDM ExperienceEvent class models time-series event records with a timestamp and event-oriented fields. Individual Profile models identity-keyed attribute records, not events.

Question 3Data ingestion and schema design

A developer needs to add organization-specific attributes to every profile record. What is the recommended approach in Experience Platform?

  1. Store the attributes in a separate event dataset only
  2. Create a brand-new class and abandon the standard profile class
  3. Add the fields directly to the union schema
  4. Create a field group with the custom fields and include it in the profile schema Correct answer.

Explanation

Field groups are reusable components that bundle fields and are included in schemas to extend them. Custom attributes belong in a custom field group added to the schema, not in the union schema directly.

Question 4Data ingestion and schema design

Which descriptor on a schema field marks that field as the primary identity for records in the dataset?

  1. Deprecated descriptor
  2. Searchable descriptor
  3. Relationship descriptor
  4. Identity descriptor Correct answer.

Explanation

Identity descriptors designate a field as an identity namespace, and one identity field in the schema is marked primary. Relationship descriptors define links between schemas, not identity.

Question 5Data ingestion and schema design

Which ingestion method writes data directly into a dataset through the Data Lake APIs without requiring a configured source connector?

  1. Source connector ingestion
  2. Query Service scheduled query
  3. Streaming ingestion via the HTTP API
  4. Batch ingestion via the Data Ingestion API Correct answer.

Explanation

The Data Ingestion API supports batch ingestion by uploading files to a dataset directly. Streaming ingestion sends individual records, and source connectors use prebuilt integrations.

Question 6Data ingestion and schema design

Which file format is supported for batch ingestion into Experience Platform?

  1. OpenDocument Spreadsheet
  2. Apple Numbers
  3. Parquet Correct answer.
  4. Microsoft Access MDB

Explanation

Batch ingestion supports formats such as JSON, CSV, and Parquet. Proprietary spreadsheet formats like MDB, Numbers, and ODS are not supported for direct ingestion.

Question 7Data ingestion and schema design

What does a union schema represent in Experience Platform?

  1. A schema used only for streaming ingestion
  2. A schema that replaces the need for field groups
  3. A merged view of all schemas that share the same class Correct answer.
  4. A schema that combines fields from multiple different classes

Explanation

A union schema aggregates the fields of all schemas sharing a class, providing a single view for querying and profile composition. It cannot combine fields across different classes.

Question 8Data ingestion and schema design

Which data type should be used for a schema field that must store a monetary amount with decimal precision?

  1. Integer
  2. String
  3. Double Correct answer.
  4. Boolean

Explanation

The double data type stores floating-point numbers with decimal precision, which suits monetary amounts. Integer stores whole numbers only.

Question 9Data ingestion and schema design

A developer configures a streaming ingestion flow that sends records to a dataset. Which endpoint is used to send individual records?

  1. The streaming ingestion endpoint that accepts records over HTTP Correct answer.
  2. The identity graph endpoint
  3. The batch ingestion endpoint that accepts an uploaded file
  4. The schema registry endpoint

Explanation

Streaming ingestion sends records individually to a dedicated HTTP endpoint tied to a dataset. Batch ingestion uploads files, and the schema registry manages schema definitions.

Question 10Data ingestion and schema design

A developer needs to validate that incoming records conform to the schema before they are committed to the data lake. What should be configured on the dataset?

  1. A relationship descriptor on the schema
  2. A scheduled query in Query Service
  3. Schema validation enabled on the dataset Correct answer.
  4. A union schema override

Explanation

Datasets can enforce schema validation so records that do not match the schema are rejected during ingestion. Relationship descriptors and union schemas do not perform record validation.

Question 11Data ingestion and schema design

Why should a developer use an identity namespace such as Email or ECID when defining identity fields?

  1. Namespaces control the compression of batch files
  2. Namespaces set the retention period for the dataset
  3. Namespaces determine the file format used for ingestion
  4. Namespaces classify identity values so they can be matched and resolved consistently Correct answer.

Explanation

Identity namespaces provide a semantic label for identity values, enabling consistent matching and identity graph construction. They do not affect file format, retention, or compression.

Question 12Data ingestion and schema design

A developer must ingest CSV data where column headers should map to schema fields. Which configuration supports this mapping during batch ingestion?

  1. An identity descriptor on each column
  2. A relationship descriptor between datasets
  3. A union schema that merges all fields
  4. A mapping set that maps source columns to target schema fields Correct answer.

Explanation

Mapping sets define how source fields are transformed and mapped to target schema fields during ingestion. Identity and relationship descriptors serve different purposes.

Question 13Data ingestion and schema design

A developer creates a schema with a custom class and later needs to ingest data into a dataset. What is required before the dataset can be created?

  1. The schema must be converted to a field group
  2. The schema must be deprecated
  3. The schema must be saved and enabled for use in datasets Correct answer.
  4. The schema must be added to the union schema manually

Explanation

A dataset requires an existing enabled schema, so the schema must be saved and made available before dataset creation. Union schemas are derived automatically, and deprecation would prevent use.

Question 14Data ingestion and schema design

What is the purpose of the primary identity setting on a schema?

  1. It selects the file format for streaming records
  2. It designates the identity field used to key records in the identity graph Correct answer.
  3. It sets the time zone for event timestamps
  4. It defines the compression used for batch files

Explanation

The primary identity identifies the main identity field for a schema so records can be keyed and resolved in the identity graph. It does not affect compression, timestamps, or file format.

Question 15Data ingestion and schema design

A developer needs to ingest nested JSON objects into a schema. How should the schema be structured?

  1. Use object-type fields that contain nested child fields Correct answer.
  2. Store the JSON as a single string field
  3. Flatten all nested data into top-level string fields
  4. Use only array fields at the top level

Explanation

XDM supports object-type fields that contain nested child fields, preserving hierarchical structure. Flattening or storing raw JSON strings loses the modeled structure.

Question 16Data ingestion and schema design

Which descriptor would a developer use to define a reference from one schema field to another schema?

  1. Relationship descriptor Correct answer.
  2. Identity descriptor
  3. Searchable descriptor
  4. Deprecated descriptor

Explanation

Relationship descriptors define references between schemas, enabling joins and lookups. Identity descriptors mark identity fields, and deprecated/searchable descriptors affect field usage and indexing.

Question 17Data ingestion and schema design

A developer wants to reuse a standard set of fields for demographic attributes across multiple schemas. What should be used?

  1. A union schema per attribute
  2. A new class for each schema
  3. A separate dataset per attribute
  4. A field group containing the demographic fields Correct answer.

Explanation

Field groups are reusable components that can be included in multiple schemas, promoting consistency. Classes define the base record type and should not be duplicated per schema.

Question 18Data ingestion and schema design

Which statement about the relationship between schemas and datasets is accurate?

  1. A dataset references exactly one schema that defines its structure Correct answer.
  2. A dataset can reference multiple schemas of different classes
  3. A dataset defines its own fields without a schema
  4. A schema can hold data independently of any dataset

Explanation

A dataset is a container that references a single schema defining its structure. Schemas hold no data themselves; data resides in datasets.

Question 19Data ingestion and schema design

A developer ingests a batch file and some records fail schema validation. What is the expected outcome?

  1. The invalid records are rejected and reported while valid records proceed Correct answer.
  2. The invalid records are stored in the union schema
  3. The entire batch is discarded silently
  4. The schema is modified automatically to accept the records

Explanation

With schema validation enabled, invalid records are rejected and surfaced in the batch report while valid records continue. The schema is not altered automatically.

Question 20Data ingestion and schema design

A developer needs to send records to a dataset with low latency as they are generated. Which approach fits?

  1. Scheduled batch ingestion of files
  2. Streaming ingestion to a dataset Correct answer.
  3. A one-time file upload
  4. A Query Service scheduled query

Explanation

Streaming ingestion accepts records as they are produced, providing low latency. Batch ingestion and scheduled queries operate on files or existing data at intervals.

Question 21Data ingestion and schema design

A developer marks an event field as the primary identity for an ExperienceEvent schema. Why is this problematic?

  1. Event schemas must use the Individual Profile class
  2. Event schemas cannot be ingested via streaming
  3. Event schemas cannot contain any identity fields
  4. Event schemas typically use an identity field tied to a person or device, not an event-specific attribute Correct answer.

Explanation

Identity in event schemas should identify the person or device so records can be resolved in the identity graph; an event-specific attribute would not serve that purpose. Event schemas can and do contain identity fields.

Question 22Data ingestion and schema design

A developer adds a custom field group to an event schema and expects the new fields to appear in the union schema immediately. What should they verify?

  1. That the field group has been converted into a class
  2. That the schema including the field group has been saved and is part of the union for its class Correct answer.
  3. That the fields have been marked as deprecated descriptors
  4. That the dataset has been deprecated

Explanation

The union schema is composed from saved schemas that share a class, so the schema using the field group must be saved and included. Field groups are not converted into classes, and deprecation would remove fields.

Question 23Data ingestion and schema design

A developer must ingest records where the identity value is sometimes an email and sometimes a hashed email. What is the soundest schema design?

  1. Use a single identity field with a namespace and normalize values before ingestion Correct answer.
  2. Use two unrelated identity fields without namespaces
  3. Rely on the union schema to resolve identities
  4. Store identities only as non-identity string fields

Explanation

Identity values should be normalized and associated with a consistent namespace so they resolve correctly in the identity graph. Unrelated fields or non-identity strings will not resolve.

Question 24Data ingestion and schema design

A developer maps a source timestamp string into an XDM date-time field during batch ingestion. What must the mapping ensure?

  1. The value is transformed into a format the target date-time type accepts Correct answer.
  2. The value is split into separate integer fields
  3. The value is stored as a free-form string regardless of type
  4. The value is dropped if it contains a time zone

Explanation

Mapping must produce values conforming to the target field's data type, so timestamp strings need transformation into an accepted date-time format. Storing as string would violate the schema type.

Question 25Data ingestion and schema design

A developer needs to model a one-to-many relationship between a profile schema and a purchase schema. Which construct supports this?

  1. A field group shared by both schemas
  2. A union schema combining both classes
  3. A relationship descriptor referencing the related schema field Correct answer.
  4. An identity descriptor on the purchase schema

Explanation

Relationship descriptors define references between schemas, enabling one-to-many modeling and lookups. Union schemas cannot combine different classes, and shared field groups do not express references.

Question 26Data ingestion and schema design

Which XDM field type should be used to store a value that must be one of a fixed, predefined set of string values?

  1. String
  2. Boolean
  3. Integer
  4. Enum Correct answer.

Explanation

An enum restricts a field to a defined set of allowed values, which enforces data quality at the schema level. A plain string accepts any text and cannot enforce membership in a fixed list.

Question 27Data ingestion and schema design

What is the purpose of a schema field group in Experience Platform?

  1. To define the dataset's retention policy
  2. To bundle a reusable set of fields that can be included in multiple schemas Correct answer.
  3. To control which users can view a dataset
  4. To assign identities to incoming records

Explanation

Field groups are reusable components that hold a collection of fields, so common attribute sets can be shared across schemas without redefining them. They are composed into schemas rather than governing access or identity.

Question 28Data ingestion and schema design

Which class should be used as the basis for a schema that records customer interactions such as page views or purchases over time?

  1. A custom class with no fields
  2. XDM Segment Definition
  3. XDM Individual Profile
  4. XDM ExperienceEvent Correct answer.

Explanation

The XDM ExperienceEvent class models time-series event data such as interactions and transactions. Profile is for entity attributes representing a person, not for event records.

Question 29Data ingestion and schema design

What does a schema's identity descriptor accomplish?

  1. It encrypts the field value at rest
  2. It links the field to a field group
  3. It tells the system that a field holds an identity value within a namespace Correct answer.
  4. It makes the field mandatory for all records

Explanation

An identity descriptor marks a field as an identity and associates it with an identity namespace so it can participate in identity resolution. It does not govern encryption or requiredness.

Question 30Data ingestion and schema design

Which ingestion method is designed for sending individual records to Experience Platform with minimal delay after they occur?

  1. Scheduled SFTP drop
  2. Streaming ingestion Correct answer.
  3. Batch ingestion
  4. Manual file upload through the UI

Explanation

Streaming ingestion accepts records as they are produced and makes them available with low latency. Batch methods collect data and process it on a schedule, which introduces delay.

Question 31Data ingestion and schema design

Which data type in XDM is appropriate for storing a timestamp that includes date, time, and time zone information?

  1. Date
  2. DateTime Correct answer.
  3. Integer
  4. String

Explanation

The DateTime type represents an ISO 8601 date-time value including time zone information. Date captures only the calendar date, and string or integer would not carry the standard time semantics.

Question 32Data ingestion and schema design

What is the role of a dataset in relation to a schema in Experience Platform?

  1. It provides the field definitions for the schema
  2. It stores records that conform to a referenced schema Correct answer.
  3. It defines the identity namespace for the schema
  4. It replaces the need for a schema

Explanation

A dataset is the storage container that holds records conforming to a schema it references. The schema defines structure; the dataset holds the data.

Question 33Data ingestion and schema design

Which statement correctly describes how a schema relates to the XDM data model?

  1. A schema is an independent format unrelated to XDM
  2. A schema is a query written against the data lake
  3. A schema is a JSON structure that conforms to the XDM model Correct answer.
  4. A schema is a database table definition generated automatically

Explanation

Schemas are expressed as JSON Schema structures that follow XDM rules, allowing data to be described consistently across the platform. They are not arbitrary formats or generated tables.

Question 34Data ingestion and schema design

A developer is adding a custom field to an existing event schema and wants the change to be available for ingestion. What must happen after the schema is saved?

  1. The dataset must be deleted and recreated
  2. A new sandbox must be created
  3. The schema change takes effect for new data without recreating the dataset Correct answer.
  4. The field group must be removed first

Explanation

Schema changes are applied to the schema definition and take effect for subsequent ingestion into datasets that reference it. Deleting datasets or creating sandboxes is unnecessary.

Question 35Data ingestion and schema design

A developer wants to ingest JSON records where each record contains an array of line-item objects. How should the line items be represented in the schema?

  1. As an array field whose items are an object type Correct answer.
  2. As a single string field containing serialized JSON
  3. As a field with the Boolean type
  4. As four separate scalar fields

Explanation

An array of object type models a repeated structured element, preserving each line item as its own object. Serializing into a string or splitting into scalars loses the structure and cardinality.

Question 36Data ingestion and schema design

A developer needs to define a relationship where a profile record references an external entity such as a product. Which mechanism is used to express this reference in the schema?

  1. A field group with the same name
  2. A union schema of both classes
  3. A relationship descriptor that points to the target schema Correct answer.
  4. A primary identity on the product field

Explanation

Relationship descriptors define references between schemas so fields can point to another schema's entity. Identity settings and naming conventions do not create schema-to-schema references.

Question 37Data ingestion and schema design

A developer is configuring a batch dataflow and needs to transform source values before they land in the dataset. Which capability should be used?

  1. Field groups
  2. Identity namespaces
  3. Mapping sets with transformations Correct answer.
  4. Sandbox reset

Explanation

Mapping sets define how source fields map to target schema fields and can include transformations during the dataflow. Identity namespaces and field groups describe structure, not field-level transformation.

Question 38Data ingestion and schema design

A developer wants to ensure that a specific attribute is always present on every record ingested into a dataset. Which schema configuration enforces this?

  1. Marking the field as required Correct answer.
  2. Setting the field type to string
  3. Adding the field to a field group
  4. Assigning the field an identity descriptor

Explanation

Marking a field as required enforces its presence during validation. Identity descriptors and field group membership do not impose requiredness.

Question 39Data ingestion and schema design

A developer needs to combine attributes from multiple field groups into a single schema for a profile entity. What is the correct approach?

  1. Compose the field groups into one schema based on the profile class Correct answer.
  2. Create a union schema for each field group
  3. Create separate datasets for each field group
  4. Convert each field group into its own class

Explanation

A schema is built by composing one or more field groups onto a base class, so multiple field groups can be combined in a single schema. Splitting into datasets or classes fragments the entity.

Question 40Data ingestion and schema design

A developer needs to ingest records from a cloud storage location into a dataset on a recurring schedule. Which configuration element defines the recurrence?

  1. The dataset's field group
  2. The dataflow's schedule Correct answer.
  3. The identity namespace
  4. The schema's primary identity

Explanation

A dataflow connects a source to a target dataset and its schedule controls recurring runs. Identity and field group settings do not control timing.

Question 41Data ingestion and schema design

A developer must ingest a CSV file whose delimiter is a pipe character instead of a comma. Which setting should be adjusted in the source configuration?

  1. The primary identity
  2. The column delimiter setting Correct answer.
  3. The identity namespace
  4. The schema class

Explanation

Source configuration includes parsing options such as the column delimiter, which must match the file's actual separator. Schema and identity settings do not affect parsing of delimiters.

Question 42Data ingestion and schema design

A developer wants to enrich incoming records with a calculated field derived from other source fields. Which step in the ingestion flow is the appropriate place?

  1. In the mapping step using a calculated field Correct answer.
  2. In the schema class definition
  3. In the identity namespace
  4. In the dataset's access control

Explanation

Calculated fields are defined during mapping so derived values are computed as records flow into the dataset. Schema classes and access controls do not compute values.

Question 43Data ingestion and schema design

A developer needs to send records to a dataset using the streaming ingestion API. Which requirement must the payload satisfy?

  1. It must be a CSV file
  2. It must include a field group definition
  3. It must conform to the dataset's schema Correct answer.
  4. It must contain only string values

Explanation

Streaming payloads must conform to the target dataset's schema so records validate before being stored. The format and value types must follow the schema rather than arbitrary constraints.

Question 44Data ingestion and schema design

A developer is designing a schema for product catalog data that is unrelated to people or events. Which class choice is appropriate?

  1. XDM Individual Profile
  2. XDM ExperienceEvent
  3. A custom class Correct answer.
  4. XDM Segment Definition

Explanation

When data does not fit the standard profile or event models, a custom class provides a base tailored to the entity. Standard classes impose semantics that do not match a product catalog.

Question 45Data ingestion and schema design

A developer wants to store a field that should accept a nested object with its own subfields but should not appear as a repeated list. Which XDM type fits?

  1. Boolean
  2. String
  3. Array
  4. Object Correct answer.

Explanation

An object type holds a structured set of named subfields as a single value. An array implies repetition, and scalar types cannot hold subfields.

Question 46Data ingestion and schema design

A developer is defining an identity field and must choose a namespace. Which consideration determines the correct namespace?

  1. The meaning and origin of the identifier value Correct answer.
  2. The number of fields in the schema
  3. The field's data type
  4. The dataset's creation date

Explanation

The namespace must reflect what the identifier represents, such as email or a device ID, so identity resolution groups values correctly. Data type or unrelated schema metadata does not determine namespace semantics.

Question 47Data ingestion and schema design

A developer ingests records where a source field called `created` holds an epoch timestamp in milliseconds. The target schema field uses the DateTime type. What must the ingestion configuration ensure?

  1. The field is marked as an identity
  2. The value is left unchanged as an integer
  3. The value is converted to an ISO 8601 date-time representation Correct answer.
  4. The field is removed from the schema

Explanation

DateTime fields expect ISO 8601 formatted values, so an epoch value must be transformed during mapping to that representation. Leaving it as an integer would not satisfy the target type.

Question 48Data ingestion and schema design

A developer adds a new field group to a profile schema and expects the new fields to appear in the union schema. What determines whether they appear?

  1. The fields appear only after a manual export
  2. The fields appear only if the dataset is deleted
  3. The fields are automatically included if the schema shares the profile class Correct answer.
  4. The fields appear only if a new sandbox is created

Explanation

Union schemas aggregate fields from schemas sharing the same class, so fields added to a profile-class schema become part of the profile union. Manual exports or dataset deletion do not drive union composition.

Question 49Data ingestion and schema design

A developer needs to model a schema where each record must carry a unique identifier used to merge records across sources. Which combination is required?

  1. A custom class and a union schema
  2. A field group and a relationship descriptor
  3. A required string field and a Boolean flag
  4. A primary identity and an identity namespace on the identifier field Correct answer.

Explanation

Merging records across sources relies on identity fields marked with a primary identity and associated namespace so identity resolution can link them. Field groups and classes alone do not establish identity.

Question 50Data ingestion and schema design

A developer must ingest a large historical dataset once and then keep ingesting new records continuously. Which approach best fits this requirement?

  1. Use batch ingestion for both phases
  2. Use manual uploads for both phases
  3. Use batch ingestion for the historical load and streaming ingestion for ongoing records Correct answer.
  4. Use streaming ingestion for both phases

Explanation

Batch ingestion efficiently handles bulk historical loads, while streaming ingestion suits continuous low-latency records. Using one method for both phases ignores the tradeoffs of each.