CCNA Master Data Management Questions

The cross-system key mapping problem is solved by storing the legacy identifier in a custom external ID field on the Salesforce Account. This field is indexed and can be used by the integration's upsert operation to match and update the correct record, preventing duplicates. It also preserves the legacy key in the source system, avoiding disruption to existing processes.

A composite key of source system code and native ID provides a globally unique identifier that also indicates the record's origin. This is essential for master data management, as it allows the organization to trace data back to its source and perform accurate merges. It also supports upsert operations in Salesforce via an external ID field.

Change Data Capture provides a near real-time stream of record changes that an external middleware can consume and use to update the ERP. It is the most direct and scalable way to synchronize address changes without requiring the ERP to call Salesforce. Scheduled jobs and outbound messages introduce latency or require specific endpoints, while Platform Events add an unnecessary layer.

Validation rules are the native Salesforce mechanism to enforce required values and format constraints at save time. A REGEX check can confirm the external identifier is a valid 15- or 18-character ID, blocking bad records before they reach the ERP. Triggers, field-level security, and email alerts do not prevent invalid data from being saved, so they cannot satisfy the integration requirement.

A data stewardship program and a data governance council are both strategic practices that establish accountability and policies for master data. They ensure that data is managed consistently, which is essential for a single source of truth. The other options are either tactical tools or unrelated to data quality management.

Survivorship rules with trust scores allow the MDM system to apply business logic such as 'most recent, but verified for legacy ERP' when consolidating records. Trust scores can be assigned based on data source and verification status, ensuring the golden record reflects the most reliable and recent information.

A robust governance framework requires a combination of clear ownership, standardized processes, and technical automation. Without these pillars, data quality degrades over time due to inconsistent entries and lack of accountability. Prioritizing these actions ensures that all stakeholders understand their responsibilities, data is handled consistently, and the organization has a mechanism to detect and remediate issues before they impact business operations.

Cross-source customer matching with inconsistent names and addresses requires probabilistic matching over multiple attributes with a tuned threshold, because exact keys alone miss too many true matches. Adding deterministic rules for unique identifiers like loyalty number anchors high-confidence matches. This hybrid strategy controls false positives through scoring while preserving recall, which is exactly what the scenario demands.

Data profiling uncovers hidden quality issues, such as inconsistent formatting, missing values, or unexpected dependencies. By understanding the true state of the source data, the architect can design effective cleansing and transformation rules. Failing to profile leads to 'garbage in, garbage out,' where inaccurate data undermines the value of the new Salesforce implementation and causes significant post-migration remediation costs and user frustration.

Salesforce provides declarative Matching Rules and Duplicate Rules that evaluate candidate records on create and edit, plus a standard merge interface for consolidation. Together these cover both prevention and remediation natively. Validation rules, activity capture, and custom Apex each address something adjacent but not the core duplicate detection and merge requirement, so they cannot be the primary recommendation.

A functioning MDM governance model needs both accountability and measurement. Stewardship assigns human ownership for resolving exceptions and approving merges, while defined quality dimensions and thresholds give the program objective success criteria. Integration patterns, UI standardization, and administrator-only editing are technical or operational choices that do not by themselves establish governance over master data.

The requirement is about linking records whose names differ lexically but refer to the same real-world entity. Deterministic rules and identifier-only matching both fail when the input strings vary, while blocking is a performance layer rather than a matching algorithm. Probabilistic scoring with a tunable threshold is the standard MDM technique for this kind of fuzzy corporate-name reconciliation.

Probabilistic matching uses statistical algorithms to determine the likelihood that two records refer to the same entity based on similarity rather than exact matches. This is vital in MDM because data across systems is rarely perfectly identical due to typos, variations, or formatting differences. Using algorithms allows the system to identify matches that deterministic logic would miss, significantly improving the completeness and accuracy of the resulting golden record.

Near real time bidirectional synchronization between Salesforce and an ERP without middleware is best achieved with Salesforce's native eventing: Change Data Capture streams Salesforce record changes, and Platform Events can carry ERP changes back. This decouples systems, preserves throughput, and supports the required latency. Batch or synchronous dual-write approaches either miss the latency target or create fragile coupling that undermines master data consistency.

Fragmented data silos often result in the same customer existing as multiple records across different systems (e.g., Salesforce, SAP, and Marketing Cloud). This leads to poor customer service, conflicting marketing messages, and inaccurate financial reporting. Identifying these symptoms is critical for a Data Architect to justify the investment in an MDM solution, as these issues directly impact the bottom line through operational inefficiency and missed sales opportunities.

Identity resolution is the process of linking data points from disparate sources to create a unified profile. By defining clear matching rules and prioritizing data attributes, the CDP can accurately identify unique individuals even when they use different identifiers across channels. This is vital for personalized marketing and accurate customer analytics, ensuring that the organization does not treat the same individual as multiple distinct records.

Data stewards bridge the gap between IT and business by overseeing the quality and lifecycle of master data. They define policies, resolve data conflicts, and ensure compliance with governance standards. This role is crucial because technical solutions alone cannot solve issues stemming from inconsistent business processes or ambiguous data definitions, requiring human oversight to make final decisions on data accuracy and business logic interpretation.

The requirement combines two distinct survivorship policies: source-priority for billing attributes and last-updated-wins for everything else. Only an MDM layer that resolves conflicts at the individual attribute level can apply different rules per field and then distribute the golden record back to the source systems. Record-level duplicate detection, validation rules, or blunt overwrites cannot express that per-attribute logic and would either leave conflicts unresolved or overwrite valid newer data.

The scenario defines a clear attribute-level system of record: the ERP owns billing address, Salesforce merely consumes it. That maps to a unidirectional publish-and-subscribe integration combined with UI-level protection so Salesforce users cannot create authoritative edits. Bi-directional approaches and federation both contradict either the direction requirement or the expectation that the value is persisted and usable natively inside Salesforce.

Consolidating heterogeneous source systems calls for a neutral surrogate master identifier plus cross-reference attributes that retain each source system's original key. This avoids collisions between country numbering schemes, keeps political decisions out of the technical design, and preserves the traceability that tax reporting and reconciliation demand. Reusing one country's scheme or discarding legacy numbers both break auditability.

Establishing a centralized hub or golden record strategy is critical for large enterprises. By defining a source of truth for specific data attributes and orchestrating updates through an integration layer, organizations prevent data drift. This approach ensures that downstream systems consume validated, reliable data, which is essential for maintaining compliance, improving reporting accuracy, and providing a unified customer experience across disparate business units and global regions.

Survivorship rules are the logic engine that determines which source provides the 'best' version of a record when multiple systems provide conflicting data. This is essential for MDM because without these rules, the system cannot intelligently reconcile discrepancies, leading to a fragmented customer view. Proper survivorship logic ensures the golden record is reliable, accurate, and reflects the most trusted information available across the entire enterprise ecosystem.

Deterministic, attribute-level golden records require two foundations: a consistent identity across sources and explicit trust ranking with survivorship rules. A global identifier and cross-reference table group all source records for the same entity, while source ranking with field-level survivorship and documented tie-breakers decides which value wins. Together they deliver the required trust and determinism; duplicate management, manual review, and external read-only access do not.

Data cleansing identifies and fixes errors such as duplicates, invalid formats, and incomplete fields before they are propagated into a new system. If dirty data is ingested, it corrupts the new MDM environment, rendering reports unreliable and forcing developers to build complex, expensive workarounds. Cleaning first ensures the initial state of the master system is pristine, providing a reliable foundation for all future business operations and data-driven decisions.