A car dealership manages both retail consumers (B2C) and business fleet customers (B2B).

Data 360 supports source-record filters directly on identity resolution rulesets . These filters act as preprocessing gates that determine which records from the ruleset's primary DMO enter that particular unification pipeline.

This is exactly the appropriate architecture when two populations share the same primary DMO but must be unified independently. The consultant can configure criteria distinguishing B2B from B2C records and apply complementary filters to the respective rulesets.

Salesforce specifically identifies separation of B2B and B2C populations as a valid ruleset-filter use case. For example, records can be filtered using an account type, customer type, record type, or other partition-level attribute so that business records don't enter the consumer ruleset and vice versa.

Creating separate DMOs simply to achieve identity-processing isolation isn't necessary when the records properly belong to the same canonical Individual model. Filtering source DLOs also places the separation at the wrong architectural layer because identity-resolution filtering is supported directly at the ruleset level.

The uploaded bank keys B. Salesforce's current ruleset documentation explicitly recommends filters for broad partition-level segregation, including B2B versus B2C scenarios.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Identity Resolution → Ruleset Source Filters.

===============