1. What objects can duplicate management be applied to?
   1. Only contacts and leads
   2. Accounts, contacts, leads, and custom objects
   3. Accounts, contacts, and leads
   4. Leads and contacts
2. True or false: local duplicate rules rely on record visibility across the org.
   1. True; the algorithm identifies duplicates among the records the current user can view.
   2. False; the algorithm identifies duplicates among all the records, despite the sharing settings.
   3. It depends on the duplicate rule configuration Record-level security setting.
3. What does the View Duplicates link on the Potential Duplicates component do?
   1. Automatically merges all identified duplicates.
   2. Selects the identified duplicates to be merged.
   3. It only gives a list of identified duplicates: the user should merge them from the Merge Duplicates wizard on the lead object.
4. A business wants to stop sales reps from creating potential duplicate leads. Which duplicate action should be set up on record creation or edit?
   1. Block.
   2. Allow.
   3. Notify.
   4. Validate.
5. Will the user be notified if a duplicate is found upon the creation of a custom object?
   1. No, because the Potential Duplicates Lightning component is only available for account, contact, and lead objects.
   2. Yes, it works for any standard and custom object.
   3. No, because matching rules cannot be created for custom objects.
6. What is global duplicate management meant for?
   1. To display a duplication alert when a new record is created.
   2. To run a background job for duplicate record set creation on account, contact, lead, and custom objects (for further reporting).
   3. To run a background job for duplicate accounts, contacts, and leads.

7. The setup item that defines the Salesforce object type we want to identify duplicates on is:
   1. The duplicate rule.
   2. The matching rule.
8. When defining a matching rule, you can define:
   1. Matching criteria and filter logic to identify duplication rules on the account, lead, and contact objects.
   2. Matching criteria and filter logic to match null values on the same record.
   3. Matching criteria and filter logic to identify which objects fields should be used to identify duplicates.
9. If you define a duplicate rule on object X, which uses a matching rule on object Y, which of the following is true?
   1. Object X records can be merged with object Y records with a custom mapping.
   2. You need to configure the proper mapping on the duplicate rule to match object Y's fields defined in the matching rule with the object X fields on which the duplicate rule is defined.
   3. You cannot merge records of type object X with duplicates records of type object Y.
   4. You can merge object X's records with object Y's records only if matching fields have the same API name.
10. Which of the following is true about duplicate management?
    1. Duplicate rules run on a record restored with an undelete.
    2. Duplicate rules run on a record restored with a delete.
    3. Cross-object duplicate rules cannot use custom picklist fields.
    4. When editing a record, a duplicate rule is triggered if the user changes any field on the duplicate rule's object.
    5. When editing a record, a duplicate rule is triggered only if the user changes one of the fields mapped.