SF-Data-Arch Master Data Management Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Enabling Lightning Experience for all users to standardize the interface used for master data entry.

  Why it's wrong here

  Standardizing the UI can reduce variance in data entry, but it is a user-experience decision rather than a governance control. It does not define ownership, quality metrics, or remediation processes, and it can be achieved without any governance framework at all. Treating it as essential to governance confuses a platform migration with an accountability model.

• ✓

  A defined data stewardship role with authority to resolve match exceptions and approve merges.

  Why this is correct

  Stewardship is the human control that keeps an MDM hub accurate over time. Automated matching will always produce borderline pairs that require judgment, and without an accountable steward those exceptions accumulate as unresolved duplicates or incorrect merges. Naming the role, granting merge authority, and documenting escalation paths is therefore a foundational governance capability rather than an optional nicety.

• ✗

  A nightly full refresh of all Salesforce records into the data warehouse using Bulk API 2.0.

  Why it's wrong here

  Full nightly extracts are an integration pattern, not a governance capability. They say nothing about who owns data, how quality is measured, or how conflicts are resolved. In fact, an indiscriminate full refresh can propagate poor-quality records downstream and amplify problems. It is a technical choice that may or may not be appropriate, but it does not belong in the governance model itself.

• ✗

  Configuring field-level security so that only system administrators can edit any master data attribute.

  Why it's wrong here

  Restricting all edits to administrators would centralize control but destroy business ownership and slow data maintenance to a crawl. Effective governance distributes edit rights to the accountable business role while protecting specific attributes, rather than concentrating everything in IT. It also creates a bottleneck that undermines the stewardship model, so it is not an essential governance capability.

• ✓

  A documented set of data quality dimensions and thresholds, such as completeness and uniqueness targets per attribute.

  Why this is correct

  Governance without measurable quality targets cannot demonstrate improvement or trigger remediation. Defining dimensions like completeness, accuracy, and uniqueness, then assigning thresholds per critical attribute, gives the program objective pass/fail criteria and feeds dashboards that show whether the MDM investment is working. This is a standard and necessary component of any MDM governance model.