I85PREP
⌘ K
Adobe CJA Business Practitioner Pro study materials
Adobe CJA Business Practitioner Pro study resources

Adobe CJA Business Practitioner Pro practice questions

One question at a time. Build your Adobe CJA 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 1Data Architecture, Connections, and Dataset Configuration

In a Customer Journey Analytics event dataset, which field is required to place each record on the reporting timeline?

  1. A lookup key field
  2. A summary metric field
  3. A profile attribute field
  4. A timestamp field Correct answer.

Explanation

Event datasets are time-series data, so CJA needs a valid timestamp to order events and assign them to reporting periods. Lookup keys, profile attributes, and summary metrics serve other purposes and do not establish event time.

Question 2Data Architecture, Connections, and Dataset Configuration

Which CJA dataset type is intended for record-based attributes about a person, such as loyalty tier or email opt-in status?

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

Explanation

Profile datasets hold current record attributes for entities such as customers, and CJA uses them to enrich person-level reporting. Event datasets hold timestamped interactions, lookup datasets provide reference values, and summary datasets store aggregates.

Question 3Data Architecture, Connections, and Dataset Configuration

Which statement best describes a connection in Customer Journey Analytics?

  1. A filter that restricts a report to one segment
  2. A schema that defines field data types and identities
  3. A visualization that combines dimensions and metrics
  4. A container of datasets used for reporting Correct answer.

Explanation

A CJA connection is the reporting container that brings one or more Experience Platform datasets together and establishes settings such as the person identifier. Data views are then built on top of that connection to expose components for analysis.

Question 4Data Architecture, Connections, and Dataset Configuration

Before an Experience Platform dataset can be added to a CJA connection, what must the dataset be based on?

  1. An Experience Platform XDM schema Correct answer.
  2. A comma-separated value file
  3. A saved report segment
  4. A relational database table

Explanation

CJA reads datasets that conform to Experience Platform Experience Data Model schemas. The schema defines fields, data types, and identities that CJA can map into reporting components.

Question 5Data Architecture, Connections, and Dataset Configuration

What is the primary role of the Person ID setting in a CJA connection?

  1. It selects the default data view container
  2. It identifies the person for reporting Correct answer.
  3. It sets the currency used in calculated metrics
  4. It defines the timestamp format for event records

Explanation

The Person ID determines which identity CJA uses to attribute events and profile records to a person for reporting. Currency, timestamp format, and data view containers are configured elsewhere and do not define person attribution.

Question 6Data Architecture, Connections, and Dataset Configuration

A lookup dataset is primarily used in CJA to do which of the following?

  1. Hold only person-level profile records
  2. Replace event records when timestamps are missing
  3. Store aggregated metrics for executive dashboards
  4. Enrich events through a matching key Correct answer.

Explanation

Lookup datasets provide reference values that CJA can attach to event or profile data through a shared key. They are not a substitute for event timestamps, aggregated summary data, or person profile records.

Question 7Data Architecture, Connections, and Dataset Configuration

Summary datasets in CJA are designed to store which kind of data?

  1. Person profile attributes
  2. Pre-aggregated metrics at a chosen granularity Correct answer.
  3. Reference values used for classification
  4. Individual clickstream interactions

Explanation

Summary datasets contain metrics that have already been aggregated, such as daily campaign totals, and are useful when person-level detail is not required. They differ from event, profile, and lookup datasets in both grain and intended use.

Question 8Data Architecture, Connections, and Dataset Configuration

When Adobe Analytics data is imported into Experience Platform with the Analytics source connector, what does the connector typically create for CJA use?

  1. Only a schema without datasets
  2. Only a data view
  3. Only a segment
  4. Event and lookup datasets Correct answer.

Explanation

The Analytics source connector ingests Analytics data into Experience Platform datasets, including event-level data and supporting lookup data. CJA then connects to those datasets rather than reading the Analytics report suite directly.

Question 9Data Architecture, Connections, and Dataset Configuration

Cross-device stitching in CJA is configured primarily to do which of the following?

  1. Normalize every timestamp to UTC
  2. Remove duplicate fields from an XDM schema
  3. Convert lookup datasets into event datasets
  4. Associate events across devices to a person Correct answer.

Explanation

Stitching uses identity information, such as a person ID and a temporary identifier, to connect events that belong to the same person across devices or sessions. It does not change dataset types, timestamps, or schema fields.

Question 10Data Architecture, Connections, and Dataset Configuration

A CJA connection includes several event datasets. Which requirement allows those datasets to report together at the person level?

  1. They must be used by the same data view filter
  2. They must arrive in the same ingestion batch
  3. They must use a compatible person identifier Correct answer.
  4. They must share the same dataset display name

Explanation

CJA combines event datasets in a connection by resolving records to a person and aligning compatible fields. Dataset names, ingestion batches, and filters do not determine whether person-level reporting can combine the data.

Question 11Data Architecture, Connections, and Dataset Configuration

After a dataset is added to a CJA connection, how do its schema fields become available as report dimensions and metrics?

  1. They are mapped to data view components Correct answer.
  2. They are copied into every data view as segments
  3. They are converted into lookup keys automatically
  4. They are exported to Adobe Analytics report suites

Explanation

A data view defines which schema fields from the connection are exposed as dimensions, metrics, and other components. Until those mappings are configured, the fields are not available as reporting components.

Question 12Data Architecture, Connections, and Dataset Configuration

What must be true for CJA to use an Experience Platform dataset in a connection?

  1. The dataset must be publicly shared
  2. The dataset must be in an accessible sandbox Correct answer.
  3. The dataset must be stored as a CSV file
  4. The dataset must be deleted after ingestion

Explanation

CJA connects to datasets that belong to the same Experience Platform organization and an accessible sandbox. Public sharing, CSV storage, and post-ingestion deletion are not requirements and can prevent normal use.

Question 13Data Architecture, Connections, and Dataset Configuration

Why is timezone handling important when configuring event datasets for CJA reporting?

  1. It changes the dataset from event to summary
  2. It converts lookup datasets into profile datasets
  3. It disables identity stitching for the connection
  4. Event timestamps determine session and reporting date boundaries Correct answer.

Explanation

CJA uses event timestamps to order events, form sessions, and assign records to reporting dates. Incorrect timezone interpretation can shift events into the wrong day or session and distort analysis.

Question 14Data Architecture, Connections, and Dataset Configuration

For a lookup dataset to enrich event data in CJA, which configuration is essential?

  1. Every lookup row must include an event timestamp
  2. A lookup key must match an event field Correct answer.
  3. The lookup schema must contain a person ID namespace
  4. Each lookup row must include a summary metric

Explanation

Lookup enrichment depends on a shared key that lets CJA match reference rows to event rows. Lookup rows generally do not need event timestamps, person namespaces, or summary metrics for the match to work.

Question 15Data Architecture, Connections, and Dataset Configuration

Which data is best represented by a profile dataset in CJA?

  1. Aggregated revenue by campaign
  2. Page view events with timestamps
  3. Product catalog records used as lookup values
  4. Current customer attributes and opt-in status Correct answer.

Explanation

Profile datasets contain record-based attributes describing an entity, such as a customer's current loyalty tier or opt-in status. Timestamped interactions belong in event datasets, aggregates in summary datasets, and catalog records in lookup datasets.

Question 16Data Architecture, Connections, and Dataset Configuration

How does streaming ingestion generally differ from batch ingestion for CJA reporting?

  1. Streaming data has lower latency than batch data Correct answer.
  2. Batch data cannot include timestamps
  3. Streaming data does not require an XDM schema
  4. Streaming data is always aggregated and cannot be queried

Explanation

Streaming ingestion sends records continuously so they can be processed sooner, while batch ingestion loads data in scheduled groups. Both still require schemas and valid timestamps, and neither is inherently unqueryable.

Question 17Data Architecture, Connections, and Dataset Configuration

What is the purpose of backfilling a dataset for CJA?

  1. To create a separate data view for every report
  2. To convert event data into summary data
  3. To delete older records automatically
  4. To load historical data for reporting Correct answer.

Explanation

Backfill supplies historical records so reports can cover periods before the current ingestion started. It does not delete records, change dataset type, or create data views.

Question 18Data Architecture, Connections, and Dataset Configuration

New fields are added to an existing Experience Platform schema after a CJA connection has been created. What is generally required before those fields can be used in reporting?

  1. Creating a new Experience Platform organization
  2. Permanently disabling identity stitching
  3. Re-ingesting all historical data as lookup records
  4. Updating the connection or data view Correct answer.

Explanation

Schema additions are not automatically available as reporting components; the connection or data view must be refreshed or edited to include them. Rebuilding the organization, converting history to lookup data, or disabling stitching is not required.

Question 19Data Architecture, Connections, and Dataset Configuration

In a CJA event dataset, what is the identity map primarily used for?

  1. Supporting person identification across namespaces Correct answer.
  2. Replacing the event timestamp during ingestion
  3. Calculating summary metrics for dashboards
  4. Storing lookup descriptions for product categories

Explanation

The identity map holds identity values and namespaces that can help CJA recognize the same person across identifiers. It does not store lookup text, compute summary metrics, or replace event time.

Question 20Data Architecture, Connections, and Dataset Configuration

If an event dataset in a CJA connection lacks a usable person identifier, which reporting capability is most directly affected?

  1. Person-level and cross-device analysis Correct answer.
  2. Total metric aggregation across all events
  3. Timestamp ordering of events
  4. Lookup enrichment of product names

Explanation

Person-level reporting and cross-device analysis depend on a usable identifier to attribute events to the same person. Event time ordering, lookup enrichment, and total aggregation can still function without that person-level linkage.

Question 21Data Architecture, Connections, and Dataset Configuration

Which statement accurately describes how stitching works in CJA?

  1. It applies only to summary datasets and aggregated metrics
  2. It uses identifiers to associate events across devices Correct answer.
  3. It removes the need for event timestamps in the connection
  4. It permanently merges all connected datasets into a single schema

Explanation

Stitching resolves identity by combining a persistent person ID with temporary identifiers observed on events, allowing cross-device or cross-session association. It does not alter schemas, apply to summary data, or eliminate timestamp requirements.

Question 22Data Architecture, Connections, and Dataset Configuration

A key limitation of summary datasets in CJA is that they do which of the following?

  1. Do not support person-level breakdowns like event data Correct answer.
  2. Must contain a unique person ID in every row
  3. Cannot be connected to a data view
  4. Cannot store any numeric metrics

Explanation

Summary datasets store pre-aggregated values, so they lack the row-level detail needed for person-level or session-level breakdowns. They can be used in data views and can contain metrics, but they are not a substitute for event-level data.

Question 23Data Architecture, Connections, and Dataset Configuration

A lookup dataset contains more than one row that matches the same key used to enrich event data. What is the most likely reporting concern?

  1. The person ID is replaced by the lookup key
  2. The event timestamp is discarded
  3. Multiple matches can make enrichment ambiguous Correct answer.
  4. The connection automatically becomes a profile dataset

Explanation

Lookup enrichment expects a clear match between a key and the reference value; duplicate matching rows can create ambiguity or duplicate results. Timestamps, dataset type, and person ID are not automatically changed by a duplicate lookup key.

Question 24Data Architecture, Connections, and Dataset Configuration

What is the likely effect of ingesting the same event record twice into a CJA event dataset?

  1. Event metrics can be inflated by double counting Correct answer.
  2. The dataset is converted into a summary dataset
  3. The person ID is automatically anonymized
  4. The duplicate is always removed by the schema

Explanation

CJA does not automatically assume two event rows are duplicates unless the data is configured or deduplicated appropriately. Repeating a record can therefore double-count interactions and distort event-based metrics.

Question 25Data Architecture, Connections, and Dataset Configuration

Which statement best distinguishes event, profile, and lookup datasets in CJA?

  1. Event rows are aggregates, profile rows are interactions, and lookup rows are attributes
  2. Event rows are interactions, profile rows are records, and lookup rows are reference values Correct answer.
  3. Event rows are reference values, profile rows are aggregates, and lookup rows are interactions
  4. Event, profile, and lookup datasets all use the same row grain by design

Explanation

Each dataset type has a different grain: events describe timestamped actions, profiles describe current entity attributes, and lookups provide reference values for matching. Summary datasets are the type used for pre-aggregated metrics.

Question 26Data Architecture, Connections, and Dataset Configuration

In Customer Journey Analytics, what is the primary role of a connection?

  1. It defines the visual layout and filters used by report dashboards.
  2. It stores a separate copy of event records inside CJA.
  3. It converts Adobe Analytics props and eVars into XDM fields.
  4. It groups Experience Platform datasets that CJA can use for reporting. Correct answer.

Explanation

A connection is the CJA layer that selects and groups Experience Platform datasets for reporting. Data views are then built from a connection to expose dimensions and metrics. Connections do not define dashboard layout, copy event data, or map Analytics variables.

Question 27Data Architecture, Connections, and Dataset Configuration

Which statement correctly distinguishes a schema from a dataset?

  1. A dataset defines identity namespaces, while a schema stores timestamps.
  2. A schema defines the record structure, while a dataset holds records that conform to that structure. Correct answer.
  3. A schema is only for lookup data, while a dataset is only for event data.
  4. A dataset defines the record structure, while a schema holds the actual records.

Explanation

A schema describes the fields, types, and structure that records must follow. A dataset is the container where records conforming to that schema are stored and ingested. Schemas and datasets are not limited to lookup or event data by definition.

Question 28Data Architecture, Connections, and Dataset Configuration

Which field in an event dataset supplies the event time that CJA uses for time-based reporting?

  1. The identity namespace selected in the connection
  2. The ingestion timestamp assigned by Experience Platform
  3. The event timestamp defined in the event schema Correct answer.
  4. The dataset creation timestamp

Explanation

CJA uses the event timestamp from the event data to place events on the reporting timeline. Ingestion timestamps describe when data arrived, not when the event happened. Dataset metadata and identity namespaces do not determine event date.

Question 29Data Architecture, Connections, and Dataset Configuration

A numeric field such as revenue is present in an event dataset. In CJA, this field is most likely exposed as what?

  1. A metric for aggregation and calculation Correct answer.
  2. A lookup key for enriching events
  3. A dimension for breaking down reports
  4. A filter for excluding rows during ingestion

Explanation

Numeric fields are typically used as metrics because they can be summed, averaged, or otherwise aggregated. Dimensions usually describe categories and are often based on string fields. Lookup keys and ingestion filters serve different configuration purposes.

Question 30Data Architecture, Connections, and Dataset Configuration

An administrator needs a dataset that resides in sandbox Dev for a connection being created in sandbox Prod. What is the most likely outcome?

  1. The dataset can be selected if the user has Admin rights in both sandboxes.
  2. The dataset cannot be selected because a CJA connection is scoped to a single sandbox. Correct answer.
  3. The dataset is automatically replicated into Prod when the connection is saved.
  4. The dataset can be selected after it is enabled for Real-Time Customer Profile.

Explanation

CJA connections operate within a selected Experience Platform sandbox, so datasets from another sandbox are not available to that connection. Profile enablement and user permissions do not bridge sandbox boundaries. Saving a connection does not replicate datasets between sandboxes.

Question 31Data Architecture, Connections, and Dataset Configuration

A data view is created from a connection. Which factor determines which datasets' fields can be used as components in that data view?

  1. The datasets included in the connection selected for the data view Correct answer.
  2. The number of data views already created in the organization
  3. The identity namespaces available in the AEP sandbox
  4. The report suite mappings inherited from Adobe Analytics

Explanation

A data view inherits its available data from the connection it is built on. Only datasets included in that connection can supply fields for the data view. Other data views, Analytics report suite mappings, and available namespaces do not define that scope.

Question 32Data Architecture, Connections, and Dataset Configuration

An event occurred on March 1 but was ingested into Experience Platform on March 10. The event dataset has a valid event timestamp. How does CJA generally report the event?

  1. On March 1, because the event timestamp controls the event date. Correct answer.
  2. On both dates, because CJA creates two records.
  3. On March 10, because ingestion date controls reporting.
  4. It is excluded until a manual backfill is run.

Explanation

CJA uses the event timestamp to place the event on the reporting timeline. Late ingestion does not change the event date when the timestamp is valid. A late-arriving event is not automatically duplicated or withheld solely because of ingestion timing.

Question 33Data Architecture, Connections, and Dataset Configuration

Before ingestion, a data prep mapping includes a row-level filter that drops transactions with test traffic. What is the effect in CJA?

  1. The rows are tagged as test data but still included in metrics.
  2. The rows are moved to a lookup dataset automatically.
  3. The rows are retained in AEP but hidden only from dimensions.
  4. The filtered rows are not available to CJA reporting because they never enter the dataset. Correct answer.

Explanation

Data prep filtering removes rows before they are ingested into the dataset. If the rows never enter the dataset, CJA cannot report on them. Filtering at this stage is not a temporary display setting or a move to another dataset.

Question 34Data Architecture, Connections, and Dataset Configuration

An event dataset is removed from an existing CJA connection. What is the most direct effect?

  1. Fields from that dataset are no longer available in data views built on that connection. Correct answer.
  2. The underlying AEP dataset is deleted from Experience Platform.
  3. All data views in the organization are permanently deleted.
  4. The dataset's schema is changed to a lookup schema.

Explanation

A connection defines the dataset scope available to its data views. Removing a dataset removes its data from that connection's reporting scope. The original Experience Platform dataset, other data views, and the schema are not automatically deleted or reclassified.

Question 35Data Architecture, Connections, and Dataset Configuration

Which schema class is required for datasets that CJA treats as event data?

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

Explanation

Event datasets in CJA are based on the XDM ExperienceEvent class, which represents timestamped interactions. Profile and lookup classes serve different data roles. Segment Membership is not the event-time schema class used for CJA event reporting.

Question 36Data Architecture, Connections, and Dataset Configuration

A dataset based on XDM ExperienceEvent has not been enabled for Real-Time Customer Profile. Can it still be added to a CJA connection?

  1. No, Profile enablement is mandatory for every CJA dataset.
  2. Only if the dataset contains a lookup schema.
  3. Yes, Profile enablement is not required for CJA event reporting. Correct answer.
  4. Only after the dataset is exported to a report suite.

Explanation

CJA event reporting uses ExperienceEvent datasets from Experience Platform and does not require those datasets to be enabled for Real-Time Customer Profile. Profile enablement is a separate capability for profile services. CJA also does not depend on exporting data to an Analytics report suite.

Question 37Data Architecture, Connections, and Dataset Configuration

When configuring a connection, why does selecting a person identifier namespace matter?

  1. It provides the identity CJA uses to associate events with people for person-level reporting. Correct answer.
  2. It sets the timezone used for all event timestamps.
  3. It determines which schema fields become metrics.
  4. It controls the retention period of the AEP dataset.

Explanation

The selected namespace identifies which identity value CJA should use to associate events with people. That choice affects person-level reporting and stitching behavior. It does not set timestamps, define metric fields, or control AEP dataset retention.

Question 38Data Architecture, Connections, and Dataset Configuration

A team adds an event dataset to a connection, but its schema contains a field named timestamp with the string type. What issue is most likely when CJA processes events?

  1. The dataset becomes a lookup dataset because timestamp is a string.
  2. CJA automatically converts any string to a valid timestamp without issue.
  3. CJA uses only the ingestion timestamp, so the string field is ignored.
  4. CJA may not interpret the field as a valid event timestamp, so time-based reporting can be unreliable. Correct answer.

Explanation

An event timestamp must be represented as a valid date-time value for CJA to use it reliably for time-based reporting. A string field named timestamp does not necessarily contain a valid timestamp type. CJA does not reclassify the dataset or silently substitute ingestion time as the event time.

Question 39Data Architecture, Connections, and Dataset Configuration

Which statement about using the same Experience Platform dataset in multiple CJA connections is accurate?

  1. No, a dataset can belong to only one CJA connection at a time.
  2. Only after the dataset is copied into a second sandbox.
  3. Yes, multiple connections can reference the same dataset. Correct answer.
  4. Only if the dataset is a lookup dataset rather than an event dataset.

Explanation

Connections are CJA-level selections of datasets, and the same Experience Platform dataset can be referenced by more than one connection. Each connection can then support its own data views and reporting scope. This does not require copying the dataset into another sandbox or changing its dataset type.

Question 40Data Architecture, Connections, and Dataset Configuration

A data prep mapping calculates a new orderValue field from source data. For CJA to report on it, what must happen?

  1. It must be mapped to a field in the dataset's XDM schema. Correct answer.
  2. It must be converted into an identity namespace before ingestion.
  3. The calculated value must first be exported to an Adobe Analytics report suite.
  4. It must be stored only in the data prep log, not in the dataset.

Explanation

CJA reports on fields that exist in the ingested dataset's XDM schema. A value calculated in data prep must be mapped into the schema so it is persisted with the records. It does not need to be exported to Analytics, kept only in logs, or turned into an identity namespace.

Question 41Data Views, Schemas, and Component Curation

In Customer Journey Analytics, what is the primary purpose of a data view?

  1. To ingest raw event data from Adobe Experience Platform source datasets
  2. To schedule recurring exports of warehouse report suites
  3. To control how a connection's data is exposed as reportable components Correct answer.
  4. To store the long-term archive of collected experience events

Explanation

A data view sits on top of a connection and determines how the connected data is interpreted for reporting, including which dimensions and metrics are available and how session rules apply. It does not ingest or store raw data itself.

Question 42Data Views, Schemas, and Component Curation

Which XDM schema class is designed for a dataset that records customer interaction events for Customer Journey Analytics?

  1. XDM Individual Profile
  2. XDM Segment Definition
  3. XDM ExperienceEvent Correct answer.
  4. XDM Data View Record

Explanation

The ExperienceEvent class models time-series event data such as page views, clicks, and purchases. Individual Profile models attributes about a person rather than the events themselves.

Question 43Data Views, Schemas, and Component Curation

In a data view, how is a schema field with an integer data type typically made available?

  1. As a metric Correct answer.
  2. As a dimension
  3. As a filter only
  4. As a segment container

Explanation

Numeric fields such as integers and doubles are surfaced as metrics by default, while string and boolean fields become dimensions. The data type drives the initial component type in the data view.

Question 44Data Views, Schemas, and Component Curation

An administrator wants analysts to see a dimension labeled 'Order Channel' instead of the raw schema field name. Where is that label changed for Workspace?

  1. In the data view's component settings Correct answer.
  2. In the Experience Platform dataset profile
  3. In the schema field descriptor
  4. In the connection's dataset settings

Explanation

Display names shown in Workspace are configured per component in the data view, not in the underlying schema. The schema field keeps its technical name.

Question 45Data Views, Schemas, and Component Curation

What is the effect of adding tags and a description to a component in a data view?

  1. It encrypts the component so that users without administrator rights cannot see it
  2. It improves findability and context when analysts search for components Correct answer.
  3. It automatically generates a matching calculated metric for the component
  4. It rewrites the underlying values that are stored in the connected schema field

Explanation

Tags and descriptions are curation metadata that help analysts find and understand components. They do not alter data values, security, or component creation.

Question 46Data Views, Schemas, and Component Curation

Which setting determines the time zone used for date-based reporting in a data view?

  1. The Experience Platform sandbox region
  2. The analyst's local browser time zone
  3. The connection's dataset time zone
  4. The data view's reporting time zone Correct answer.

Explanation

CJA reports dates using the time zone configured in the data view, so the same connection can be presented consistently across projects. Browser and sandbox regions do not override that setting.

Question 47Data Views, Schemas, and Component Curation

In a data view, what does the 'Include values' setting on a dimension do?

  1. Removes the entire dimension from every Workspace project
  2. Converts the dimension into a numeric metric
  3. Limits which dimension values are available for reporting Correct answer.
  4. Sets the attribution model for the dimension

Explanation

Include values lets an administrator restrict a dimension to selected items, such as only five key channels. The component remains available, but other values are not reported.

Question 48Data Views, Schemas, and Component Curation

What is an XDM field group?

  1. A reusable collection of fields for a schema class Correct answer.
  2. A container for session-level filter logic
  3. A calculated metric that is defined inside the data view
  4. A permission set that controls who can edit the schema

Explanation

Field groups bundle related fields so they can be reused across schemas that share a class. They are schema-building components, not data view components or permissions.

Question 49Data Views, Schemas, and Component Curation

A data view's session timeout is changed from 30 minutes to 15 minutes. What is the effect?

  1. Attribution lookback windows are shortened to 15 minutes for all metrics
  2. Events older than 15 minutes are permanently removed from the connection
  3. Sessions split after 15 minutes of inactivity, changing session-based metrics Correct answer.
  4. The data view stops collecting new events after 15 minutes of idle time

Explanation

Session timeout defines the inactivity gap that starts a new session, so shortening it can increase session counts and change metrics like sessions per person. It does not delete events or alter attribution lookback windows.

Question 50Data Views, Schemas, and Component Curation

Where can a practitioner override the data view's default attribution model for a single metric?

  1. In the schema field's identity descriptor
  2. In the metric's component settings Correct answer.
  3. In the Workspace project's color palette preferences
  4. In the connection's dataset refresh schedule

Explanation

Attribution can be set as a data view default and then overridden on individual metrics in their component settings. This lets one metric use a different model without changing the whole data view.