I85PREP
⌘ K
Adobe Customer Journey Analytics Developer Expert study materials
Adobe Customer Journey Analytics Developer Expert study resources

Adobe Customer Journey Analytics Developer Expert practice questions

One question at a time. Build your Adobe Customer Journey Analytics 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 connection configuration

In Adobe Customer Journey Analytics, what is the fundamental difference between a connection and a data view?

  1. A connection groups datasets for analysis, while a data view defines how that data is interpreted and reported Correct answer.
  2. A connection stores raw event data, while a data view permanently deletes unused fields
  3. A connection defines report suites, while a data view maps them to Experience Platform sandboxes
  4. A connection applies attribution models, while a data view applies only filters to sessions

Explanation

A connection is the container that brings one or more Experience Platform datasets together for CJA analysis. A data view sits on top of a connection and controls component definitions, settings, and how the underlying data is presented in reporting.

Question 2Data ingestion and connection configuration

Which Adobe Experience Platform object must exist before a dataset can be selected when building a CJA connection?

  1. A project template shared across users
  2. A schema with a defined XDM structure and a dataset created from it Correct answer.
  3. A segment published to the segment library
  4. A calculated metric registered in Component Manager

Explanation

Datasets in Experience Platform are always based on an XDM schema, so a schema and a dataset built from it must exist before CJA can ingest that data. Segments, calculated metrics, and project templates are downstream CJA constructs.

Question 3Data ingestion and connection configuration

A developer needs CJA to recognize timestamps from an ingested dataset. Which schema field should carry the event time?

  1. The XDM timestamp field mapped to the event time Correct answer.
  2. The ingestion batch identifier
  3. The primary identity namespace field
  4. A custom string field named eventTime

Explanation

CJA uses the XDM timestamp field as the event time for the dataset. This field must be populated with a valid timestamp so events are placed correctly on the timeline.

Question 4Data ingestion and connection configuration

What does the person ID setting on a CJA connection establish?

  1. The time zone applied to all report timestamps
  2. The identity used to stitch events into a person across datasets Correct answer.
  3. The maximum number of rows returned per query
  4. The default attribution model for all metrics

Explanation

The person ID on a connection defines the identity namespace used to associate events with people across the datasets in that connection. It is foundational to cross-dataset person stitching.

Question 5Data ingestion and connection configuration

Which statement best describes how dataset records are associated with people in a CJA connection?

  1. Records are matched by the ingestion order of batches
  2. Records are matched only by exact timestamp alignment
  3. Records are matched by dataset name conventions
  4. Records are matched using the configured identity namespace values Correct answer.

Explanation

CJA associates records with people by resolving identity values against the connection's configured identity namespace. Timestamps, dataset names, and batch order do not determine person association.

Question 6Data ingestion and connection configuration

When configuring a data view, what is the purpose of the container settings?

  1. They determine the schema class used for ingestion
  2. They set the retention period for raw dataset storage
  3. They control how event, session, and person containers behave in reporting Correct answer.
  4. They define which report suites receive the data

Explanation

Container settings in a data view govern the behavior of event, session, and person scopes used throughout reporting. They shape how metrics and dimensions aggregate within each scope.

Question 7Data ingestion and connection configuration

A team wants a numeric field from their dataset to be usable as a metric in CJA reporting. Where should this be configured?

  1. In the connection by marking the dataset as a metric source
  2. In the workspace project by creating a quick calculated metric
  3. In the Experience Platform schema as a metric type
  4. In the data view by adding the field as a component Correct answer.

Explanation

Components such as metrics and dimensions are defined in the data view, which exposes dataset fields for reporting. The schema describes structure but does not designate reporting metrics.

Question 8Data ingestion and connection configuration

A data view includes a field that contains free-text values with high cardinality. What is the recommended approach before exposing it as a dimension?

  1. Use it directly because CJA automatically buckets text values
  2. Disable the field and rely on the raw schema instead
  3. Create a derived field or classification to reduce cardinality Correct answer.
  4. Convert the field to a metric to avoid cardinality limits

Explanation

High-cardinality free-text fields can degrade reporting performance and usability, so they are typically transformed via derived fields or classifications into a controlled set of values. CJA does not automatically bucket arbitrary text.

Question 9Data ingestion and connection configuration

Which Experience Platform feature allows CJA to combine datasets that share a common identity?

  1. Batch ingestion scheduling
  2. Sandbox reset tooling
  3. Real-time Customer Profile identity graph Correct answer.
  4. Dataset schema versioning

Explanation

The Real-time Customer Profile identity graph links identities across datasets, enabling CJA to associate records for the same person. This underlies cross-dataset person stitching in a connection.

Question 10Data ingestion and connection configuration

A data view is configured with a non-default time zone. What is the effect on reported timestamps?

  1. Timestamps are converted to each user's local browser time
  2. Timestamps are shifted by the ingestion delay offset
  3. Timestamps are always displayed in UTC regardless of the setting
  4. Timestamps are converted to the data view time zone for reporting Correct answer.

Explanation

The data view time zone determines how event timestamps are presented and bucketed in reporting. This ensures consistent day and hour boundaries for reports built on that data view.

Question 11Data ingestion and connection configuration

What is the primary role of a lookup dataset in a CJA connection?

  1. To enrich event data by joining additional attributes on a key Correct answer.
  2. To replace the event dataset when events are missing
  3. To hold audit logs for ingestion
  4. To store calculated metric definitions

Explanation

Lookup datasets provide supplementary attributes that are joined to event data using a matching key. This enriches reporting without altering the underlying event records.

Question 12Data ingestion and connection configuration

Which schema class is typically required for a dataset that records user interactions such as page views and clicks?

  1. Lookup
  2. ExperienceEvent Correct answer.
  3. Segment definition
  4. Profile

Explanation

ExperienceEvent is the XDM class for time-series interaction data such as page views and clicks. Profile classes describe entities rather than events.

Question 13Data ingestion and connection configuration

A connection contains two event datasets with overlapping data for the same interactions. What is the recommended way to handle this?

  1. Apply a filter to hide duplicate rows at report time
  2. Merge the datasets in the data view by renaming fields
  3. Deduplicate at the source or exclude the redundant dataset from the connection Correct answer.
  4. Include both and rely on deduplication by timestamp

Explanation

CJA does not automatically deduplicate overlapping event records across datasets, so duplicates should be resolved before or excluded from ingestion. Relying on reporting filters leaves inflated underlying data.

Question 14Data ingestion and connection configuration

When adding a dataset to a connection, what does the dataset's data retention setting affect?

  1. How long CJA can query that data based on the Experience Platform retention window Correct answer.
  2. How long the data view retains component definitions
  3. How long workspace projects remain shared
  4. How long calculated metrics cache results

Explanation

Experience Platform dataset retention limits how far back data remains available for querying in CJA. Data outside the retention window is not accessible regardless of data view configuration.

Question 15Data ingestion and connection configuration

What happens when a field is not added as a component in the data view but exists in the connected dataset?

  1. It is removed from the Experience Platform dataset
  2. It is available in reporting but hidden by default
  3. It cannot be used in reporting until added to the data view Correct answer.
  4. It is automatically converted to a calculated metric

Explanation

Only fields exposed as components in the data view are available for reporting in CJA. Fields present in the dataset but not mapped remain inaccessible until added.

Question 16Data ingestion and connection configuration

Which identity configuration is required for CJA to stitch events across datasets that use different identity namespaces?

  1. Each dataset must use the same schema version
  2. Each dataset must share an identical primary key field name
  3. Each dataset must be ingested in the same batch
  4. The identities must be resolvable through a common identity graph Correct answer.

Explanation

Cross-dataset stitching depends on identities being linked through the identity graph so records resolve to the same person. Field names, schema versions, and batch timing do not establish identity linkage.

Question 17Data ingestion and connection configuration

What is the effect of enabling the 'all visitors' style person setting versus a specific identity namespace on a connection?

  1. It changes the attribution model applied to session metrics
  2. It changes which identity namespace is used to associate events with people Correct answer.
  3. It changes the time zone used for reporting
  4. It changes the number of datasets allowed in the connection

Explanation

The person ID setting selects the identity namespace used for person association. Different selections change how events are grouped into people for reporting.

Question 18Data ingestion and connection configuration

A data view needs a dimension that combines two source fields into a single value. Which CJA capability should be used?

  1. A report suite mapping
  2. A dataset schema update
  3. A derived field Correct answer.
  4. A calculated metric

Explanation

Derived fields let you create new dimensions from existing data using rules and transformations within the data view. Calculated metrics operate on metrics, not dimensions.

Question 19Data ingestion and connection configuration

Which statement about the relationship between a connection and multiple data views is accurate?

  1. Data views cannot share a connection across projects
  2. Each data view requires its own separate connection
  3. Each connection can support multiple data views with different component configurations Correct answer.
  4. Each connection can support only one data view

Explanation

A single connection can back multiple data views, each with its own component definitions and settings. This lets teams tailor reporting for different audiences from the same ingested data.

Question 20Data ingestion and connection configuration

What does the 'sandbox' selection determine when creating a CJA connection?

  1. Which isolated Experience Platform environment supplies the datasets Correct answer.
  2. Which users can view the data view
  3. Which attribution model is applied
  4. Which report suite receives the data

Explanation

Experience Platform sandboxes are isolated environments, and the connection draws datasets from a chosen sandbox. This controls which data is available to the connection.

Question 21Data ingestion and connection configuration

A dataset contains a field representing product categories as a numeric code. To report readable category names, what should be configured?

  1. A timestamp field override
  2. A calculated metric mapping codes to names
  3. A container setting to translate values
  4. A lookup dataset or classification mapping codes to labels Correct answer.

Explanation

Mapping numeric codes to readable labels is done through a lookup dataset join or classification. This enriches the dimension values without changing the raw event data.

Question 22Data ingestion and connection configuration

Which scenario best indicates that a dataset should be excluded from a connection?

  1. The dataset shares an identity namespace with other datasets
  2. The dataset contains events from a different business unit that should not appear in reports Correct answer.
  3. The dataset uses an ExperienceEvent schema
  4. The dataset has a timestamp field

Explanation

Datasets whose events should not appear in a given reporting context should be excluded from that connection. Schema class, timestamps, and shared identities are normal characteristics of included datasets.

Question 23Data ingestion and connection configuration

What is required for a lookup dataset to enrich event data in a connection?

  1. A separate data view dedicated to the lookup
  2. The same schema class as the event dataset
  3. A shared key that matches records between the lookup and event datasets Correct answer.
  4. An identical timestamp in every record

Explanation

Lookup enrichment depends on a matching key that links lookup records to event records. Without a shared key, attributes cannot be joined to events.

Question 24Data ingestion and connection configuration

A data view's component settings include an option to hide a component. What is the effect of hiding a component?

  1. It prevents ingestion of the associated field
  2. It deletes the underlying data from the dataset
  3. It changes the component's data type
  4. It removes the component from the reporting UI while retaining its data Correct answer.

Explanation

Hiding a component removes it from the reporting interface without deleting or altering the underlying data. This is useful for decluttering workspaces while preserving data availability.

Question 25Data ingestion and connection configuration

Which factor most directly limits how far back historical data is available in a CJA connection?

  1. The data view's component count
  2. The number of calculated metrics
  3. The number of workspace projects
  4. The Experience Platform dataset retention policy Correct answer.

Explanation

Historical availability in CJA is bounded by the Experience Platform dataset retention policy. Once data ages out of retention, it is no longer queryable.

Question 26Data ingestion and connection configuration

Which type of dataset is used to enrich event data in a CJA connection with additional attributes?

  1. Summary dataset
  2. Profile dataset
  3. Lookup dataset Correct answer.
  4. Event dataset

Explanation

Lookup datasets provide supplementary attributes that can be joined to event data based on a common key, enabling enrichment of event records.

Question 27Data ingestion and connection configuration

What is the primary purpose of the 'Person ID' setting when configuring a connection in CJA?

  1. To specify the identity namespace used to stitch events across datasets Correct answer.
  2. To define the time zone for reporting
  3. To select which metrics are available in the data view
  4. To determine the data retention period for the connection

Explanation

The Person ID setting selects the identity namespace that CJA uses to link events belonging to the same individual across datasets.

Question 28Data ingestion and connection configuration

When creating a connection, what does the 'Rolling Data Window' setting control?

  1. The number of days of historical data available for reporting Correct answer.
  2. The time zone used for date boundaries in reports
  3. The frequency of data ingestion from Experience Platform
  4. The maximum number of datasets that can be added to the connection

Explanation

The rolling data window defines how many days of historical data are retained and available for analysis in the connection.

Question 29Data ingestion and connection configuration

Which CJA feature allows you to combine data from multiple datasets that share the same person identifier?

  1. Connection Correct answer.
  2. Calculated metric
  3. Data view
  4. Segment

Explanation

A connection in CJA is used to integrate multiple datasets from Experience Platform, enabling combined reporting when they share a common identity.

Question 30Data ingestion and connection configuration

A developer needs to add a new dataset to an existing CJA connection. What is a prerequisite for the dataset to be available for selection?

  1. The dataset must be ingested in the same sandbox as the connection Correct answer.
  2. The dataset must be enabled for Profile in Experience Platform
  3. The dataset must be associated with a data view
  4. The dataset must have a schema that includes a timestamp field

Explanation

CJA connections operate within a single Experience Platform sandbox; datasets from other sandboxes are not visible or selectable.

Question 31Data ingestion and connection configuration

Which identity setting in a CJA connection determines how events are associated with a person when multiple identity namespaces exist in the data?

  1. The 'Identity Graph' setting in the data view
  2. The 'Stitching' setting in the connection
  3. The 'Namespace' setting in the dataset schema
  4. The 'Person ID' setting Correct answer.

Explanation

The Person ID setting in the connection specifies which identity namespace is used to link events to a person across datasets.

Question 32Data ingestion and connection configuration

A company wants to ensure that data from a new dataset is included in an existing connection without reprocessing historical data. What should they do?

  1. Create a new connection and merge the data views
  2. Modify the existing data view to include the new dataset
  3. Add the dataset to the connection and enable backfill Correct answer.
  4. Add the dataset to the connection without backfill

Explanation

When adding a dataset to a connection, enabling backfill will populate historical data for that dataset, ensuring it is available for reporting.

Question 33Data ingestion and connection configuration

Which statement about the relationship between a connection and a data view is correct?

  1. Data views and connections are independent and not linked.
  2. A connection can have multiple data views, but a data view belongs to exactly one connection. Correct answer.
  3. A data view can be based on multiple connections.
  4. A connection can have only one data view.

Explanation

In CJA, a connection is the data source, and you can create multiple data views from a single connection, each tailored for different reporting needs.

Question 34Data ingestion and connection configuration

What happens when a dataset is removed from a connection?

  1. The dataset is deleted from Experience Platform.
  2. The data view automatically updates to exclude the dataset's components.
  3. Historical data from the dataset remains available in reports.
  4. The data from that dataset is no longer available for reporting in associated data views. Correct answer.

Explanation

Removing a dataset from a connection disconnects it from CJA, so its data will not be included in any data views built on that connection.

Question 35Data ingestion and connection configuration

A developer is configuring a connection and needs to ensure that data from a dataset is joined with event data using a common key. Which dataset type should be used?

  1. Profile dataset
  2. Lookup dataset Correct answer.
  3. Summary dataset
  4. Event dataset

Explanation

Lookup datasets are designed to be joined with event data based on a matching key, allowing enrichment with additional attributes.

Question 36Data ingestion and connection configuration

Which factor determines the maximum time range for which data can be reported in a CJA connection?

  1. The time zone setting of the data view
  2. The data retention policy of the dataset in Experience Platform Correct answer.
  3. The granularity of the timestamp field in the dataset
  4. The rolling data window setting of the connection

Explanation

The dataset's retention policy in Experience Platform defines how long data is stored, which in turn limits the historical range available in CJA.

Question 37Data ingestion and connection configuration

When adding a dataset to a connection, what is the effect of selecting a non-default time zone for the connection?

  1. It changes the time zone of the data view, overriding its setting.
  2. It shifts the timestamps of events to the selected time zone for reporting. Correct answer.
  3. It has no effect; time zone is only set in the data view.
  4. It affects only the display of dates in the connection interface.

Explanation

The connection time zone determines how event timestamps are interpreted and displayed in reports, effectively shifting them to the selected zone.

Question 38Data ingestion and connection configuration

A company has a dataset with a schema that includes a field 'product_id' that they want to use to join with a lookup dataset containing product details. What must be true for the join to work in CJA?

  1. The lookup dataset must be added to the connection before the event dataset.
  2. The 'product_id' field must be defined as an identity in the schema.
  3. The lookup dataset must have a matching field with the same name and data type. Correct answer.
  4. The 'product_id' field must be included as a dimension in the data view.

Explanation

For a lookup join to work, the key field in the event dataset and the corresponding field in the lookup dataset must match in name and data type.

Question 39Data ingestion and connection configuration

A developer is troubleshooting a connection where data from a newly added dataset is not appearing in reports. The dataset is correctly configured and contains data. What is the most likely cause?

  1. The data view has not been updated to include components from the new dataset.
  2. The connection's rolling data window is set to a short period that excludes the data.
  3. The dataset was added without enabling backfill, and no new data has arrived. Correct answer.
  4. The dataset's schema does not include a timestamp field.

Explanation

If backfill is not enabled when adding a dataset, only data ingested after the addition will be available; if no new data has arrived, reports will not show data.

Question 40Data ingestion and connection configuration

Which statement accurately describes the behavior of the 'All Visitors' person setting in a CJA connection?

  1. It stitches events across all datasets regardless of identity namespace. Correct answer.
  2. It requires that all datasets share the same identity namespace.
  3. It uses the Experience Cloud ID as the default identity for stitching.
  4. It includes events that do not have a person identifier.

Explanation

The 'All Visitors' setting allows CJA to stitch events across datasets even when they use different identity namespaces, by using the identity graph.

Question 41Data view and component configuration

In a Customer Journey Analytics data view, what is the primary purpose of the container settings for a component?

  1. To set the time zone used for date-based reporting
  2. To define the attribution model applied to the metric
  3. To determine which sandbox the data view connects to
  4. To control the scope at which the component's values are evaluated and reported Correct answer.

Explanation

Container settings determine the scope (for example person, session, or event) at which a component is evaluated, which directly affects how values are counted and reported. They do not set attribution, time zone, or sandbox connectivity.

Question 42Data view and component configuration

A developer needs to add a new dimension to an existing data view without rebuilding it. Which approach is appropriate?

  1. Recreate the data view from scratch with the new component
  2. Add the component to the data view from the underlying connection's schema Correct answer.
  3. Create a new connection and migrate all reports
  4. Edit the raw dataset schema in the data lake

Explanation

Components in a data view are drawn from the schema of its underlying connection, so new fields available in the connection can be added to the data view. Rebuilding the data view or editing the raw schema is unnecessary and disruptive.

Question 43Data view and component configuration

Which data view setting determines how long event data remains available for reporting before it is excluded?

  1. Report suite calendar type
  2. Attribution lookback window
  3. Data retention window Correct answer.
  4. Session timeout

Explanation

The data retention window in a data view controls how far back event data is retained and reportable. Attribution lookback and session timeout govern attribution and sessionization, not data retention.

Question 44Data view and component configuration

What does the session timeout setting in a data view control?

  1. The time window used to attribute conversions to a channel
  2. The maximum duration a report can run before timing out
  3. The inactivity period after which a new session is started for a person Correct answer.
  4. The frequency at which data is ingested from the connection

Explanation

Session timeout defines the period of inactivity after which a subsequent event begins a new session for a person. It does not govern report execution, attribution windows, or ingestion frequency.

Question 45Data view and component configuration

A team wants a metric to count only events where a specific dimension value is present. Which data view feature supports this?

  1. A component-level container change
  2. A calculated metric using a segment filter Correct answer.
  3. A derived field with a numeric transform
  4. A data view-level time zone adjustment

Explanation

Calculated metrics can incorporate segment filters so the metric counts only events matching a condition. Derived fields transform values rather than filter counts, and container or time zone settings do not restrict counting by dimension value.

Question 46Data view and component configuration

What is the effect of setting a component's attribution model to 'last touch' on a metric?

  1. Credit is given to the last touchpoint before the conversion Correct answer.
  2. Credit is split evenly across all touchpoints
  3. Credit is given to the touchpoint with the highest value
  4. Credit is given to the first touchpoint in the lookback window

Explanation

Last touch attribution assigns full credit to the final touchpoint preceding the conversion within the lookback window. First touch, linear, and value-based models behave differently.

Question 47Data view and component configuration

Which statement best describes a derived field in a data view?

  1. It permanently alters the source data in the data lake
  2. It creates a new reportable component by transforming one or more existing fields at report time Correct answer.
  3. It duplicates the entire dataset for a separate data view
  4. It replaces the need for a connection

Explanation

Derived fields create new reportable components by applying transformations to existing fields during reporting, without altering source data. They do not modify the data lake, duplicate datasets, or replace connections.

Question 48Data view and component configuration

A developer wants reports to reflect a business time zone different from UTC. Where is this configured?

  1. In each individual metric's attribution settings
  2. In the data view's time zone setting Correct answer.
  3. In the workspace project's date range
  4. In the connection's data ingestion schedule

Explanation

The data view has a time zone setting that governs how dates and times are bucketed in reporting. Metric attribution, ingestion schedules, and project date ranges do not set the reporting time zone.

Question 49Data view and component configuration

What happens when a component is hidden in a data view?

  1. It becomes read-only for all users
  2. It stops collecting data from the source
  3. It is permanently deleted from the connection schema
  4. It is excluded from the component picker but existing references may remain Correct answer.

Explanation

Hiding a component removes it from the component picker to reduce clutter while not deleting the underlying schema field, and existing references can persist. It does not delete schema fields, stop data collection, or make components read-only.

Question 50Data view and component configuration

A calculated metric divides revenue by sessions. Which consideration is most important when configuring it?

  1. Ensuring both numerator and denominator use compatible container scopes Correct answer.
  2. Assigning a numeric derived field to the denominator
  3. Changing the data view time zone to match the denominator
  4. Setting the metric's attribution to first touch

Explanation

When dividing metrics, compatible container scopes help avoid misleading results, since mismatched scopes can produce inconsistent ratios. Attribution, derived fields, and time zone are not the primary concern for a ratio metric.