Given a Customer Scenario, Identify the Issues Impacting Data Quality Along Key Dimensions (such as Data Duplication, Completeness, Accuracy, Integrity, Etc.). DATA-ARCHITECT Practice Questions (Page 4)

Questions 16–20

1. 16expert · hard

   A company has a Salesforce org with a custom object 'Task' that is linked to Accounts. They find that some Task records reference Account IDs that no longer exist, and some Task records have a 'Status' field that is not in the picklist. The company wants to clean up the data and prevent future issues. Which approach is MOST appropriate?

   • ARun a report to identify orphaned Task records and update or delete them
   • BUse a data cleansing tool to identify and fix orphaned records and enforce integrity rules
   • CUse a validation rule to ensure the Account field is not blank and the Status is in the picklist
   • DUse a workflow rule to update the Account field to a default value
   Reveal Solution Discussion Select an answer first
2. 17application · medium

   A retail company has a Salesforce org that has been in use for several years. They notice that the same customer appears multiple times with slightly different spellings of their name (e.g., 'John Smith' vs 'Jon Smith') and different email addresses. This is causing marketing campaigns to send duplicate emails and sales reps to see conflicting history. What is the MOST likely root cause of this data quality issue?

   • AInsufficient field-level security
   • BPoor page layout design
   • CLack of a unique identifier and no deduplication rules
   • DIncorrect validation rules
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   A company has a Salesforce org with a custom object 'Project' that is linked to Accounts. They notice that the same project has been created multiple times under different Accounts, each with slightly different project names. This is causing confusion in project tracking and reporting. What is the MOST effective way to prevent this duplication in the future?

   • AUse a formula field to concatenate project name and Account name
   • BUse a validation rule to require a unique project name
   • CImplement duplicate rules on the Project object
   • DTrain users to search before creating new records
   Reveal Solution Discussion Select an answer first
5. 19foundation · easy

   A customer reports that the same account appears multiple times in their Salesforce org with slightly different names. What is the most likely cause of this data duplication?

   • AThe org uses a single record type for all accounts
   • BThe integration with an external system is updating the wrong records
   • CThe org has too many custom fields on the Account object
   • DLack of a standardized data entry process and missing duplicate detection rules
   Reveal Solution Discussion Select an answer first
6. 20expert · hard

   A company has a Salesforce org with a custom object 'Order' that is linked to Accounts. They have a large number of duplicate Order records for the same customer, but the duplicates have different 'Order Date' and 'Amount' values. The company wants to merge the duplicates, but they are concerned about losing data. Which approach is MOST appropriate to consolidate the duplicates while preserving data?

   • AUse a third-party data cleansing tool that supports custom objects
   • BDelete the duplicate records and keep the one with the most recent date
   • CManually update the records to consolidate the data
   • DUse Salesforce's built-in merge functionality for the Order object
   Reveal Solution Discussion Select an answer first