Northern Trail Outfitters is implementing identity resolution in Data 360 and wants to understand how...

After the initial Identity Resolution processing, Data 360 uses incremental processing so that unchanged source records don't need to be repeatedly rematched. Salesforce's current Identity Resolution documentation explicitly states that preprocessing identifies records that are new or changed and sends only those records into Identity Resolution.

Salesforce determines whether a record changed by converting source records to hash values and comparing those hashes with the values from previous Identity Resolution runs. Records whose current hash indicates no change can be excluded from unnecessary reprocessing.

This behavior has direct credit-consumption implications. Salesforce explains that preprocessing prevents credits from being consumed by repeatedly running Identity Resolution over records that have already been unified in their current form. Even when a source performs a full refresh, preprocessing can protect unchanged records from unnecessary identity-processing work.

Option A is incomplete because an existing record that has been modified must also be reprocessed. Option B incorrectly assumes that every subsequent run rematches the entire source population.

The uploaded master correctly keys C.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Identity Resolution → Incremental Processing and Credit Consumption.

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