CCNA Identity Resolution Questions

Ordering match rules from high-confidence exact matches down to controlled fuzzy matches prevents weak criteria from merging unrelated records first. This satisfies the stem's anti-fragmentation goal by ensuring deterministic identifiers drive unification, with fuzzy logic applied only where exact evidence is absent.

By only defining a match rule for exact email and using any match rule, the system will unify records that share an exact email and will not unify records based solely on last name and postal code. This directly satisfies the business requirement to avoid false positives from the common name and location combination.

Scheduled recurring runs let the ruleset process on a defined cadence without manual intervention, ensuring identity resolution keeps pace with steady data volumes. This satisfies the stem's requirement for a management method that triggers ruleset processing automatically and predictably within Salesforce Data Cloud.

The Unified Link Individual object is the output artefact of an Identity Resolution ruleset, storing the reconciled individual profile produced when match and reconciliation rules run. It satisfies the stem's requirement for a core output component, holding the unified record that downstream segmentation and activation consume.

Source Sequence rules only evaluate records from sources included in the ruleset scope, so each participating source must be correctly identified and mapped before priority can be applied. Omitting a source silently excludes its records from reconciliation, producing incorrect golden records.

Fuzzy Name matching handles phonetic variations and common nickname equivalents.

The run history surfaces execution status, timestamps, record counts and logs for each past ruleset run, satisfying the need to audit and troubleshoot identity resolution outcomes. It provides operational visibility into when matching and reconciliation executed and how many records were unified, rather than defining match rules or configuring data streams.

Data Cloud applies E.164 normalisation during ingestion and mapping, converting national-format numbers into a standard international representation before exact matching rules execute. This satisfies the country-code formatting constraint: numbers differing only by prefix or spacing resolve as identical, so exact phone matching succeeds without custom transformation logic.

Overly restrictive or misconfigured match rules prevent any records from satisfying the matching criteria, so no unified profiles are created. Reviewing rule definitions, including exact versus fuzzy matching and normalisation settings, directly addresses the zero-profile constraint by confirming records can actually match before execution.

The Identity Resolution setup interface provides configuration of rulesets, match rules, and reconciliation rules, letting administrators define how unified profiles are matched and merged. This satisfies the stem's requirement for actions available directly from that interface.

The Most Recent reconciliation rule compares source records and retains the value from the source whose activity date is latest, resolving conflicts by recency rather than source priority or frequency. This matches the requirement to keep the First Name from the system of record with the most recent activity.

Longest String compares values across source records and retains the character-length maximum, so the most complete postal address string survives unification. This directly satisfies the requirement to keep the greatest-length address on the unified profile.

Identity Resolution consolidates source records into unified individual profiles, then generates unified link records mapping each contributing source record to its profile. This satisfies the stem's demand for the ruleset's primary output: both the merged profile and the linkage metadata, not merely match scores or duplicate flags.

Source Sequence defines the priority order used during reconciliation, so ranking CRM above POS stops POS values overwriting verified CRM attributes on unified profiles. Integration continues because POS records still contribute where CRM supplies no value.

High-cardinality unique identifiers such as distinct account numbers or verified emails sharply reduce false-positive matches, because shared attributes like surname or address cannot alone collapse separate households. Adding these to the match rules satisfies the stem's constraint of preventing incorrect merges across distinct customer households during identity resolution.

Unified profiles are built by the Unified Link object, which resolves relationships through foreign keys on source DMOs. Without a foreign key on the mobile engagement DMOs pointing to the Individual DMO, no link can be created, so engagement data never reaches the profile.

Using two match rules allows records with the government identifier to match precisely, while records lacking it can still match on last name and date of birth. This increases coverage without sacrificing precision, as the second rule provides a fallback. It aligns with the goal of maximizing accuracy across a dataset with partial identifier coverage.

Combining exact identifiers, such as medical record numbers, with fuzzy demographic criteria increases the likelihood of correctly linking records that share an identifier while still catching records with minor demographic variations. This balanced approach improves recall without sacrificing the precision needed to avoid merging distinct patients.

Identity resolution match rules operate on contact point objects, so telephone-based matching requires the Contact Point Phone DMO to be mapped first. This mapping supplies the normalised phone values the match rule evaluates, satisfying the prerequisite for telephone matching.

Identity resolution rulesets operate strictly within one data space, so matching and reconciliation cannot span records held in separate spaces. This satisfies the stem's requirement for a true statement about data space behaviour, confirming that rulesets are space-scoped rather than global across the org.

'Total Unified Individuals' counts distinct consolidated profiles produced after the ruleset merges source records into unified individuals, so it reflects the deduplicated output of identity resolution rather than raw source counts or match-rule executions. This directly satisfies the stem's requirement to define the metric as the count of unique consolidated profiles generated.

Reconciliation rules operate per attribute, not per ruleset, so each field can use its own strategy — Most Recent for phone, Source Sequence for name. This satisfies the stem's requirement that behaviours characterise identity resolution processing, where attribute-level granularity lets conflicting values resolve differently across the unified profile.

Mapping to standard Data Model Objects enforces the platform's canonical schema, so incoming values are automatically normalised and formatted during processing. This satisfies the stem's requirement for benefits delivered before identity resolution, since consistent field formats and types are established upstream, allowing matching rules to operate on clean, uniform data.

Ingested source profiles are harmonised and written into the Individual DMO, which holds the raw mapped records before identity resolution runs. This mapping step is what feeds the Unified Individual DMO, making the statement true.

Source Sequence reconciliation ranks data sources by priority, so the highest-ranked source supplies values for each field during identity resolution. Ordering sources by the custom data quality score ensures address fields are populated from the best-quality system.

Identity Resolution rulesets are configured through Data Cloud Setup, which requires the Data Cloud Admin or Data Cloud Consultant permission set. These grant the object and field-level access needed to create, match, and reconcile unified profiles, satisfying the configuration privilege the stem demands.

The 'Longest Value' strategy selects the longest string among the source values for an attribute. For address fields, a longer string often indicates more complete information, such as including apartment numbers or postal codes. This strategy directly addresses the requirement to include the most complete mailing address.

Identity Resolution rulesets are configured in Data Cloud Setup, under the Identity Resolution section, where consultants define match rules and reconciliation rules. This location is distinct from the Data Cloud app's data streams and profile areas, satisfying the question's navigation requirement.

Requiring several attributes to agree within one rule raises the combined specificity, so records must match on all fields rather than any single weak one. This conjunctive logic prevents over-merging by filtering out coincidental partial matches.

Name is a fuzzy-matchable attribute because Data Cloud compares first and last name strings using similarity algorithms, tolerating typos, nicknames and transliterations. Exact-match rules cannot absorb such variation, so name qualifies for the fuzzy matching rules the question requires.

Source Sequence assigns explicit priority ordering across data sources, so Salesforce CRM records override Marketing Cloud records when populating unified profile attributes. This directly satisfies the stem's precedence requirement, unlike other reconciliation strategies such as most recent or last updated.

Adding higher-specificity criteria or requiring multiple fields via AND logic narrows the match key, so shared first name and phone number alone no longer trigger a merge. This directly addresses the over-merge constraint by demanding additional corroborating attributes before Data Cloud unifies two profiles.

Fuzzy Email matching normalises common variations and tolerates minor typographical errors, such as transposed characters or misspellings, when comparing email addresses. This satisfies the stem's requirement to understand expected behaviour of the Fuzzy Email match rule, distinguishing it from exact matching, which requires identical values.

Individuation strategies define the reconciliation rules that decide which matched records merge into one unified profile and which remain separate. This directly satisfies the requirement to control how matching records are grouped and consolidated, shaping the final unified profile output.

Highest Frequency selects the surviving attribute value by tallying occurrences of each candidate value across all contributing source records, then keeping the most repeated one. This directly satisfies the stem's requirement that survivorship be driven by how many times a value appears.

Overly broad fuzzy match rules force the matching engine to compare every record against every other record, producing a massive candidate set. Without pre-filtering criteria to narrow candidates first, the quadratic comparison load inflates job execution time and degrades Identity Resolution performance across the entire run.

Reconciliation rules define which source record's value wins for each unified field, so once matching links records, these rules run to resolve conflicts and populate the Unified Individual's attributes. This is the outcome that produces a single consolidated profile rather than merely linking records.

Multiple rulesets in one data space compete during unification, producing conflicting profiles and duplicated processing. Consolidating all match and reconciliation rules into one ruleset per data space gives deterministic, ordered reconciliation and eliminates redundant compute.

Within a ruleset, match rules combine using OR logic, so a record pair is linked when it satisfies any single active rule. Exact Name and Exact Email therefore each independently trigger a match, broadening rather than narrowing the linked set.

The Unified Link Individual object stores the mapping between each source profile's individual record and the resulting unified individual profile, resolving identity across disparate sources. It is the join artefact that Data Cloud's identity resolution writes when consolidating source records.

Identity resolution matches on standard profile and contact point data models. Mapping email to a custom attribute bypasses the Contact Point Email DMO, so no matching key exists between source and CRM records, preventing merges despite identical addresses.

Data spaces provide logical isolation, so separating B2C and B2B sources into distinct spaces lets each run its own identity resolution ruleset, producing independent unified profiles. This satisfies the requirement for separate consumer and business-buyer profile structures without cross-contamination between datasets.

The Unified Individual DMO consolidates source profiles into one canonical record by applying identity resolution match and reconciliation rules, satisfying the requirement for a single customer view. It resolves duplicates across data streams, linking related identifiers to the unified profile, which downstream segments and activations then reference.

Match rules specify the comparison logic, such as exact or fuzzy matching on fields, that determines whether source records refer to the same individual. They drive the linking decision within the ruleset, directly enabling unified profiles.

Longest String compares conflicting values and retains the lengthiest phone number string, preserving the most complete representation across source systems. This directly satisfies the requirement to keep the longest available phone number when conflicts arise during profile unification.

Identity resolution rulesets are scoped to a single data space, so matching and reconciliation only process records held within that space. This satisfies the stem's multi-space constraint: cross-space unification requires separate reconciliation, since rules cannot span or merge data across space boundaries.

Match rule edits do not trigger automatic reprocessing; the ruleset must be run manually or on a schedule before Unified Individual counts and links recalculate. This explains why the counts remained unchanged immediately after modification.

Identity Resolution evaluates criteria within a single match rule as a combined condition, so first name, last name, and postal code are compared together for each record pair. Separate rules would match independently, producing looser, unintended links.

Identity resolution rulesets run as batch jobs on a scheduled or manual basis, not as continuous streaming. The architect must therefore accept that unified profiles lag behind high-velocity record updates, which conflicts with the stem's near-real-time requirement.

Contact Point Email is a standard contact point Data Model Object, so its email address field can be referenced in standard identity resolution match rules. Matching on normalised email values links source profiles belonging to the same individual, satisfying the requirement for a supported contact point object.

Party Identification matching requires the Party Identification Data Model Object to be mapped, because it stores the identifiers (such as email or loyalty number) that link source profiles to a unified party. Without this DMO, identity resolution cannot resolve records via Party Identification.

Fuzzy match rules compare many record pairs, and a poorly bounded rule can trigger Cartesian explosion, exhausting memory and timing out the Identity Resolution batch job. Removing or refining that rule reduces the comparison volume, so the job completes within resource limits.

Commerce, CRM and Marketing store identifiers in incompatible formats, so match rules must normalise emails, phone numbers and loyalty IDs before comparison. Without this tolerance, the consolidation produces duplicate unified profiles rather than a single customer view.

Email address is a high-cardinality, deterministic identifier, so exact-match rules on it reliably unify profiles across sources. It satisfies the stem's requirement for a commonly evaluated identity resolution match attribute, since most ingested datasets carry it and duplicates indicate the same customer.

The wizard walks administrators through defining match rules and reconciliation rules, which determine how source records are compared and merged into unified individual profiles. It therefore configures the identity resolution logic rather than merely reporting on it.

Exact Phone is a native, out-of-the-box match rule type in Data Cloud Identity Resolution, comparing phone values for precise equality rather than fuzzy or normalised matching. It satisfies the stem's constraint of natively available rule types, alongside Exact Email, Exact Name, and Fuzzy Name, requiring no custom configuration.

A match rule is mandatory because identity resolution cannot reconcile profiles without explicit matching criteria. The ruleset requires at least one match rule to define which fields, such as email or phone, determine when two source profiles unify into a single unified profile. Without it, no reconciliation logic exists.

Data spaces partition data and metadata, so identity resolution rulesets run only within each space's boundary. Records from separate regional units therefore never match or merge, satisfying the compliance constraint even when email addresses are identical across regions.

Executing an identity resolution ruleset writes its consolidated output to the Unified Individual DMO, which holds the reconciled golden profile for each matched individual. This satisfies the stem's requirement for the primary automatic output, since the ruleset's match and reconciliation logic populates this DMO directly rather than any source or link DMO.

Reconciliation rules define which source value wins for a given unified field when multiple sources contribute conflicting values. Ordering the Email Address reconciliation rule so the CRM stream outranks marketing automation guarantees the CRM value survives even if the marketing record is newer, which is exactly the deterministic outcome the scenario demands.

Data Cloud keeps multiple contact points as related records linked to the unified individual rather than collapsing them to one value. This allows several valid emails or phones to coexist on the unified profile, satisfying the reconciliation scenario where sources disagree.

Identity resolution links source records by comparing shared match attribute values. If those values change or are removed at source, previously unified profiles no longer satisfy the match criteria, so the refresh splits them apart — even though the ruleset itself is unchanged.

Mapping streams to standard DMO fields lets Data Cloud's built-in normalisation run during matching, applying case insensitivity and whitespace stripping. This directly resolves the ALL CAPS versus Title Case mismatch that currently blocks legacy billing and CRM records from linking.

Reconciliation rules specify how to resolve conflicts when multiple matched records have different values for the same field. For example, they can select the most recent value, the most frequent value, or the value from the highest-priority source. This is essential for creating a coherent unified profile.

Identity resolution matches profiles across ingested source data, so source objects must first be mapped to the Individual DMO and related DMOs. Without this mapping, no unified profile data exists to reconcile, making ingestion and DMO mapping the mandatory prerequisite before any ruleset can be created.

Fuzzy match rules operate on normalized address values and tolerate the character-level differences produced by abbreviations and missing prefixes. Setting an appropriate fuzzy tolerance balances recall against false positives. This is the intended configuration when source addresses vary in formatting, because normalization plus fuzzy comparison absorbs the variations without requiring rigid exact equality on every token.

Broad match criteria in the new phone rule bridge previously separate clusters into one unified profile, reducing the total count through over-merging. The stem's drastic decrease reflects consolidation, not data loss, because fewer distinct profiles remain after aggressive matching.

Reconciliation rules govern how attribute values are chosen for the unified profile when multiple source records are matched. They support strategies like 'Most Recent' or 'Source Priority'. Configuring a reconciliation rule with the 'Most Recent' strategy on the Loyalty Tier field ensures the unified profile reflects the value from the latest updated source record, exactly as required.

Overly broad match rules force the engine to compare excessive record pairs, and poor primary/foreign key modelling prevents efficient blocking. Tightening match criteria and modelling keys correctly reduces candidate comparisons, directly cutting the job's runtime while preserving accurate unified profiles.

The Unified Link Individual object holds the many-to-one mapping linking each source individual record to its unified individual profile. This mapping is what lets Data Cloud resolve multiple source records into one golden profile, satisfying the stem's requirement for source-to-unified relationship storage.

Run history records the outcome of each ruleset execution, showing how many matches occurred and how unified profiles were produced during that run. This lets the consultant validate that the ruleset behaved as intended and compare runs over time, which is exactly the operational visibility the scenario asks about.

Omitting or unmapping matching attributes such as email or phone causes records to fall through to broader rules, inflating unified profiles. Reviewing match rule criteria confirms every required attribute is mapped and populated, directly addressing the inflated-count constraint in the stem.

Exact Email normalises the address (lowercasing, trimming) before comparing, so records match only when the formatted values are identical. This satisfies the stem's requirement for matching on identical emails after standard formatting, rather than fuzzy or phonetic matching.

Evaluating identification number together with identification type prevents a passport number and a driver's licence number sharing digits from being treated as the same party. This satisfies the stem's requirement by adding the type discriminator that avoids cross-system collisions.

Reconciliation rules determine, for each unified profile field, which source record's attribute value wins when multiple records reconcile. They govern field-level survivorship, not match rules or reconciliation ordering, satisfying the requirement to control which values populate unified profile fields.