Free Salesforce Certified Data 360 Consultant practice test: 30 questions with answers

A segment is a set of unified individuals selected by filter criteria, such as recent purchase behaviour. It is not a copy of data lake objects, a permission set, or a dashboard layout.

Segment membership is updated when the segment refreshes, so a customer whose activity arrived after the last refresh can be missing. The permission set, activation target, and sandbox checks do not explain a missing segment member.

An activation delivers segment members to a configured activation target, which is how an audience reaches an external platform. A count emailed to the platform, a zero-copy connection, or per-person webhooks do not deliver the audience the way an activation does.

A data action reacts to a qualifying event and calls an external endpoint, which matches the near real-time requirement. A daily spreadsheet export, a weekly count, and a permission set do not trigger anything when the event occurs.

Checking membership after refreshes and adjusting criteria as definitions change are ongoing management tasks that keep an audience accurate. Segments are not converted into data model objects, and permission sets do not hold audience membership lists.

Near-real-time personalization needs events to arrive continuously, and a streaming data stream fed by the Ingestion API or an SDK connector delivers that. Nightly, monthly, and weekly approaches deliver data too late, and a calculated insight does not ingest events at all.

A data stream is the ingestion configuration for one source, and it controls how that source's records are written into a data lake object. The other terms describe audience delivery, data partitioning, and identity matching, which are different parts of the platform.

Zero-copy access lets Data 360 use data that remains in the external warehouse, which avoids a full copy. The nightly export and manual copy recreate the duplication the company wants to avoid, and a calculated insight does not import rows as profiles.

Batch data transforms read data lake objects, reshape them, and write the output to a new data lake object on a schedule. Segments select audiences, data actions react to events, and permission sets control access, so none of them reshape data.

Clickstream and app engagement events arrive continuously, and streaming ingestion keeps downstream features current. The tax code table and the annual product catalog change rarely, so scheduled batch loads are the better fit for them.

A calculated insight aggregates unified data with a query-based definition and refreshes on a schedule, which suits lifetime value. A data action reacts to events, a data stream copies records rather than aggregating them, and a permission set controls access.

Calculated insights are computed on a schedule, so their values refresh in batches rather than on each event. They do not store original files, and they do not perform identity matching, which is handled by identity resolution.

A data graph precomputes related records so that a service can retrieve connected data quickly at run time. The data action, segment, and dashboard options do not provide precomputed relationships for fast lookups.

Connecting Data 360 data to CRM Analytics makes it available as a dataset that dashboards can combine with other sources. Email templates, segment builder access, and identity resolution do not create a data connection for dashboards.

When records for one person are combined and fields are harmonized, each feature describes the customer consistently across sources. The other options claim that data quality removes validation, eliminates training needs, or automatically publishes predictions, which are not true.

Mapping aligns source fields such as email_addr and EmailAddress with one common data model field, so unification and activation see a consistent meaning. Encryption, deduplication, and changing the source schema are not what mapping does.

The only configured rule is a match on normalized email, and both records satisfy it, so they are linked into one unified individual. The first-name difference is not part of that rule, and the deletion and CRM merge options describe actions the configuration does not perform.

Identity resolution links records that describe the same person, so a segment counts that person once rather than once per source record. The other options describe conversions, activation shortcuts, or scheduling behaviour that identity resolution does not provide.

Data lake objects store ingested records in a structure close to the source before mapping. Data model objects hold the harmonized structure that mapping targets, while activation targets and Data Graphs serve other purposes.

Data model objects provide the common structure that source fields map into, and their shared fields give unification something consistent to compare. Publishing to advertising platforms happens through activations, and data model objects do not replace data streams.

Data 360 ingests data from many sources, harmonizes it into a common model, and resolves records into unified profiles that marketing can use continuously. The spreadsheet, replacement database, and file share options do not produce a current, unified customer view.

A unified individual is the resolved profile that links source records describing the same person, which lets segments and insights treat that person as one customer. The raw table, dashboard widget, and permission set are other kinds of objects or features and do not define a resolved profile.

Grounding a prompt with current unified data lets the assistant reference real order and case details without retraining the model. Retraining, replacing the model with templates, and storing transcripts do not supply the live customer context the assistant needs.

Consent and data-use settings must be respected before data is activated, so records that the marketing use does not permit should be excluded from the audience. Relying on later unsubscribes, hiding fields, or deleting consent evidence does not make the activation compliant.

Data 360 is the platform previously branded Data Cloud, which ingests, harmonizes, unifies, and activates customer data. Marketing Cloud Intelligence, Tableau CRM, and Marketing Cloud Personalization are separate Salesforce products.

Visibility of unified profile data depends on the user's permission set and on access to the data spaces that hold it, so that is the first thing to confirm. A browser plug-in, calculated insight settings, and field order in a source file do not control whether an analyst can see profiles.

Data spaces are logical partitions, so an administrator uses them to keep data for different brands or regions apart and to control which users can access each partition. Splitting files, publishing segments automatically, and removing source connections are not purposes of data spaces.

Data Kits bundle Data 360 configuration so that it can be moved from one environment to another. Calculated insights, activation targets, and Data Graphs are runtime features that process or deliver data and are not packaging tools for deployment.

Run errors show which mapping no longer matches the source, and pointing that mapping at the renamed field repairs the broken reference. Deleting objects, disabling identity resolution, or adding an unmapped stream does not fix the mapping that failed.

Testing in a sandbox and then deploying the verified configuration keeps production stable and surfaces problems before users are affected. Editing production directly, sharing logins, and skipping documentation all increase risk and make changes hard to trace.