DupeBlocker

Question 1 of 70

1. Question

Which statement best describes deduping best practices?

It is best to have multiple scenarios deployed ranging from a rigid match to a loose match within your definition of a duplicate. Using multiple scenarios per object allows for different actions to be taken based on the scenario’s rigidness.
One scenario per object is typically best. It allows the user to match data with medium rigidness and still be confident in the duplicates being detected. This way users can confidently use the auto-merge option.
Standard objects should follow a rigid to loose scenario approach. Custom objects should use no more than two scenarios each.
Objects with higher record volume should only use one scenario per object. Lower volume objects should use two or three scenarios each.

Question 2 of 70

2. Question

For block bypassing to work, all blocking scenarios of the same type must have the Allow Block Bypass option enabled.

Correct
Incorrect

Question 3 of 70

3. Question

When the Match on Insert/Update Action is set to Do Not Insert/Update, there is an option to Bypass the Block using the Allow Block Bypassing feature.

In order for a warning to be created when this option is utilized, what additional step must be taken?

When using Allow Block Bypassing, warnings will automatically be created if a user selects bypass the block.
On the Settings tab, the default Block Bypass Creates Warnings option must remain selected.
In the Scenario edit screen, the Block Bypass Creates Warnings option must be selected.
When bypass block is selected, a warning will never be created.

Question 4 of 70

4. Question

DupeBlocker can be temporarily disabled from the Settings tab without having to uninstall or undeploy all scenarios.

Correct
Incorrect

Question 5 of 70

5. Question

When importing settings, all existing settings and scenarios will remain and the new information will be added.

Correct
Incorrect

Question 6 of 70

6. Question

Which of the following is NOT true of the Batch Apex Key Builder?

(Select all that apply)

Runs faster than the Original Key Builder
The key building window can be closed and the job will run in the background
An email notification will be sent when the key build is complete
Batch key builder progress can be monitored from Setup – Administration Setup – Monitoring – Apex Jobs

Question 7 of 70

7. Question

Which statements are true for the Original Key Builder?

(Select all that apply)

Runs faster than the Batch Key Builder
The key building window must remain open until the build is complete
Can only be used when building keys for a single scenario
Can be scheduled to run nightly

Question 8 of 70

8. Question

If Jill wants to see how effective her scenarios are, what can she do?

(Select all that apply)

View the statistics on the scenario
View the Scenario Effectiveness tile on the Dashboard tab
There is no way to know how effective they are
View the Scenario Effectiveness section in General Settings

Question 9 of 70

9. Question

Any error messages triggered by DupeBlocker will automatically be sent to:

The email address indicated in the Administrator Email field on the Settings tab
The individual Scenario Owner
The user who installed the application
All Salesforce administrators

Question 10 of 70

10. Question

How can the Account, Contact or Lead page layouts be customized to indicate that a match was detected?

(Select all that apply)

Add the DupeBlocker Potential Duplicate related list
Add the DupeBlocker Warning related list
Add the Inline Duplicate Lists visualforce page to the detail section of the page
Add custom fields to flag records with the action taken by DupeBlocker when a record is inserted or updated

Question 11 of 70

11. Question

Joe wants to be able to identify duplicates regardless of the users’ Salesforce sharing settings.

Which option must be enabled for this to occur?

Bypass Block in Scenario Details
Bypass Security in Scenario Details
Ignore Security Settings in DupeBlocker Settings
There is no way to do this, DupeBlocker will only detect duplicates for records the user has view access to

Question 12 of 70

12. Question

Who can receive the Task alert when duplicates are reported via a Warning?

The current user only
The scenario owner only
Both the scenario owner and current user
Admins only

Question 13 of 70

13. Question

The Account scenario rule count is the total number of rules for all deployed _________ scenarios.

(Select all that apply)

Account
Lead to Account
Contact
Lead to Contact
Lead

Question 14 of 70

14. Question

Scenario keys are an internal table of duplicate keys that need to be maintained for all scenarios to function properly.

Correct
Incorrect

Question 15 of 70

15. Question

What scenario changes require the rebuilding of keys?

(Select all that apply)

Scenario is initially deployed/redeployed
Scenario Rules (matching criteria) are updated, deleted or added
A Scenario object filter is added or updated
A current user filter is added or updated

Question 16 of 70

16. Question

What general changes require the rebuilding of keys?

(Select all that apply)

When changes are made to Clean Account Name Settings, FirstName, State or Country Mappings in DupeBlocker Settings for the scenarios that include these mapping types
Re-enabling DupeBlocker
Upgrading to a new version
Disabling DupeBlocker

Question 17 of 70

17. Question

A Scenario set to Auto-Merge will always keep an existing record as the Master and will never keep the newly created duplicate record as the Master record.

Correct
Incorrect

Question 18 of 70

18. Question

John can create an Opportunity when a Lead is converted to a Contact.

Correct
Incorrect

Question 19 of 70

19. Question

How many scenarios are needed to find duplicates that match on First Name and Last Name and Street and City and/or Email?

1
2
3
4
5

Question 20 of 70

20. Question

The Auto-Convert action is applicable to what types of scenarios?

(Select all that apply)

Lead to Contact
Lead to Account
Lead
Contact
Account

Question 21 of 70

21. Question

Warnings should be reviewed on a regular basis to avoid high Salesforce storage usage and running the risk of exceeding APEX governor limits when inserting/updating records that trigger DupeBlocker scenarios.

Correct
Incorrect

Question 22 of 70

22. Question

What is the purpose of the Match Blank Values option?

Enables blank values in the designated field to be seen as matching data
Updates the designated field with data from the subordinate record when the master value is blank
Enables records where one value is blank and the other value is populated in the designated field to be seen as matching data
Enables the user to customize which value will remain in Salesforce if one field is blank

Question 23 of 70

23. Question

Jill has a Lead scenario set to Auto-Merge.

How can she ensure the email opt-out field always retains the true value?

(Select all that apply)

In the Auto-Merge Settings, set the Default Mergeable Field Action to Merge
In the Auto-Merge Settings, set the Default Non-Mergeable Field Action to Update if Blank
In the Auto-Merge Settings, add a new Merge Mapping for the opt-out field and set the Merge Action to Merge Values
In the Auto-Merge Settings, add a New Merge Mapping for the opt-out field and set the Merge Action to Update if Blank
In the Auto-Merge Settings, set the Default Mergeable Field Action to Update

Question 24 of 70

24. Question

Which feature allows users to filter their source data and target data separately?

Bypass Block
Enable Dual Filters
Nothing needs to be enabled, this is default functionality
Bypass Security

Question 25 of 70

25. Question

Joe wants to exclude records inserted by System Administrators from being evaluated by his Account Scenarios.

Which of the following Scenario Filters should he use to accomplish this?

Filtered Object: Current User | Filtered Field: Profile ID != SystemAdministrator
Filtered Object: Account | Filtered Field: Created By ID != (select all users in the System Administrator Profile)
Filtered Object: Account | Filtered Field: Profile ID != SystemAdministrator
Filtered Object: Current User | Filtered Field: Created By ID != (select all users in the System Administrator Profile)

Question 26 of 70

26. Question

Which Match on Insert Actions will block a record from entering Salesforce?

(Select all that apply)

Do Not Insert
Report Duplicate
Redirect to Existing
Redirect to VisualForce Page

Question 27 of 70

27. Question

DupeBlocker keys will take approximately how much of an organization’s current storage per object/per scenario in Salesforce?

10%
15%
20%
25%
DupeBlocker Keys do not use any Salesforce storage space

Question 28 of 70

28. Question

How will a user know if a scenario requires a rebuild of keys?

The rebuild needed checkbox will be checked on the scenario
Keys should be built every day for all deployed scenarios
An email will be sent to the administrator indicating that keys need to be built
Keys are automatically rebuilt as needed, users will never need to rebuild keys

Question 29 of 70

29. Question

Where can a user find current rule counts per object?

(Select all that apply)

DupeBlocker Settings tab
DupeBlocker Today page
Individual Scenario page
By contacting support

Question 30 of 70

30. Question

John has two Contact Scenarios.

One is set to Report Duplicate and the other is set to Auto-Merge.

Both scenarios have identified duplicates for a newly created record.

Which action will be taken for the found duplicate?

A Warning will be created showing the potential duplicate records.
The record will be auto-merged into an existing record.
The records will be auto-merged AND a Warning will be created.
The duplicate will be inserted and an email will be sent to the user with the matching record ID’s so they can then be merged in Salesforce.

Question 31 of 70

31. Question

Which of the following statements are true?

(Select all that apply)

DupeBlocker is a real-time duplicate prevention tool that installs directly inside Salesforce.
Duplicates are detected when inserting records in batch mode.
Duplicates are detected when inserting via the Salesforce user interface.
Scenarios can be used to find and automatically merge existing duplicates.

Question 32 of 70

32. Question

Which 2 ways can a user check which version is installed?

(Select Two)

Setup -> Build ->Develop -> Installed Packages
DupeBlocker Today tab
DupeBlocker Settings tab
Right clicking on any of the DupeBlocker tabs and clicking Help -> About DupeBlocker

Question 33 of 70

33. Question

When installing/upgrading, which user option is recommended to ensure all user profiles have the appropriate access to utilize the end-user features of DupeBlocker?

Install for Admins Only
Install for All Users
Select Specific Profiles -> Set all for Non-Admins

Question 34 of 70

34. Question

Existing custom Salesforce profiles will be assigned Read only access to the following DupeBlocker Custom Objects when Set All for non-admins is selected during installation:

Warnings and Potential Duplicates ONLY
Warnings, Potential Duplicates and Scenarios ONLY
Warnings, Potential Duplicates, Scenarios, Rules and Filters ONLY
None, access to the DupeBlocker custom objects can only be granted after the installation is complete

Question 35 of 70

35. Question

At a minimum, the 3 steps needed to start detecting duplicates for newly create/updated records against all existing records are:

(1) Deploy desired scenarios (2) Build matching keys (3) Navigate to Setup -> Deploy -> View Installed packages and deploy the application
(1) Assign a DupeBlocker license to each user that you want it to trigger for (2) Build matching keys (3) Select Enable in DupeBlocker Settings
(1) Access DupeBlocker Settings to create/enable the license and load default scenarios (2) Deploy desired scenarios (3) Build matching keys
(1) Access DupeBlocker Settings and enable all objects that duplicates should be detected for (i.e. Accounts, Contacts, Leads etc.) (2) Deploy desired scenarios (3) Select Enable in DupeBlocker Settings

Question 36 of 70

36. Question

Which 4 Mapping types can be customized in DupeBlocker Settings?

(Select Four)

First Name Match
State Match
Country Match
Cleaned Account Name
Relaxed NA Phone Match

Question 37 of 70

37. Question

When a Lead is inserted with one of the specified sources in the Web Lead Sources settings, what action will be taken if it is detected as a duplicate by a scenario with an Insert action set to Do Not Insert?

The insert will be blocked and a Task will be created on the existing record capturing all the field data from the web Lead.
The insert will be allowed and a DupeBlocker Warning will be created listing the duplicate records.
The insert will be allowed, no action will be taken by DupeBlocker.
The insert will be blocked and an email will be sent to the DupeBlocker Scenario Owner alerting that the new Lead could not be created.

Question 38 of 70

38. Question

Which of the following statements are true about the insert/update tracking fields?

(Select Two)

Users can customize the values that will be assigned based on the action taken by DupeBlocker
Records will be updated with the values none, warn, merge or convert and cannot be customized
Their primary purpose is to allow users to bypass round robin style Lead Assignment rules when inserted records are merged or converted (but can be used to trigger/not trigger any custom code)
Custom fields will automatically be created on the desired object when field names are populated in the DupeBlocker Settings tab

Question 39 of 70

39. Question

Which of the following is NOT true about the Inline Duplicates List?

(Select all that apply)

When DupeBlocker is installed, a visualforce page is automatically added to the Account, Contact and Lead page layouts to show all potential duplicates when a record is inserted/updated.
DupeBlocker ships with pre-built visualforce pages that can be added to the Account, Contact, and Lead page layouts.
A sample visualforce page is provided that can be customized to show any desired field from the matching object, and/or customized to show duplicates for an enabled custom object.
When a custom object is enabled for duplicate detection, a visualforce page is automatically created that can be added to the custom objects page layout.

Question 40 of 70

40. Question

Which statistics are available when viewing a Scenario?

(Select all that apply)

Current Duplicate Warning Count and Potential Duplicate Record Count for all current Warnings
Duplicates Blocked (via Do Not Insert or Redirect)
Duplicates Auto-Merged
Duplicates Auto-Converted
Duplicates Merged (combined count of records auto merged/converted and manually merged records via a Warning)

Question 41 of 70

41. Question

John is using the Report Duplicate Insert/Update action on all scenarios and is being inundated with pop-ups alerting him of these warning tasks.

What can John do to ensure the warnings are still being created without receiving the pop-ups?

There is no way to turn off pop-ups. He will have to remove the Create Task option from each scenario.
On the Settings tab, check the Disable Warning Task Reminders field.
Go to Setup – Tasks and update the Salesforce setting to turn off notifications for all DupeBlocker tasks.
From the Scenario Edit screen, check the Disable Warning Task Reminders field.

Question 42 of 70

42. Question

Which of the following statements is NOT TRUE regarding DupeBlocker Scenarios:

Different actions can be taken for Inserts vs. Updates
Multiple Scenarios can be defined for the same object
Best practice is to define a series of scenarios to detect duplicates and act on the duplicate records in different ways depending on how rigid the matching criteria
Auto-Convert will only trigger when a Lead is inserted (not when a matching Contact or Account is inserted)
DupeBlocker Scenario actions will be triggered for batch inserts (batch size greater than 1)

Question 43 of 70

43. Question

In the Auto-Convert and Auto-Merge Settings there are options to select which existing record the new record should be converted or merged into (e.g. Oldest Record, Newest Record, Last Modified Record).

If none of these options fits the user’s business needs, a custom rule can be created to indicate which existing record to use.

Correct
Incorrect

Question 44 of 70

44. Question

Which of the following statements are true regarding Lead to Contact and Lead to Account Scenarios?

(Select all that apply)

They only trigger when inserting/updating a Lead record.
When Do Not Insert is selected as the Match on Insert Action, by default, only Lead records will be blocked when there is a matching Contact or Account.
They will work in either direction, but will ONLY block if the Block Account/Contact Matches option is enabled.
Warnings will be created when inserting Contacts or Accounts when Auto-Convert is selected as the Match on Insert Action.

Question 45 of 70

45. Question

Which of the following statements regarding the use of filters is true?

(Select all that apply)

Filters can be based on specific fields within the object itself.
Filters can be based on the attributes of the current Salesforce user who is inserting or updating a record.
Only one Filter can be specified on a particular Scenario.
Multiple Filters can be specified, and all Filters are AND'd together.

Question 46 of 70

46. Question

Which of the following statements regarding Dual Filters is correct?

Dual Filters must be enabled in Scenario Details before they can be used.
Both a Source and Target filter is required.
In order for a Scenario to only fire (or not fire) for a specific groups of users, Dual Filters must be enabled.
Dual Filters must be enabled in the DupeBlocker Settings tab before they can be used.

Question 47 of 70

47. Question

What are the 3 possible ways you could still get a Warning even when the Match on Insert/Update action IS NOT set to Report Duplicate?

(Select Three)

When an auto-convert or auto-merge fails.
When a user selects the Bypass Block option when inserting/updating a record.
When inserting a Lead that matches a scenario set to block with a Lead Source specified in the Web Lead Source in DupeBlocker Settings.
When the user inserting the record has not been added to the list of approved DupeBlocker Users.
When inserting a Contact/Account that matches a Lead to Contact/Account Scenario set to either block or auto-convert.

Question 48 of 70

48. Question

When a duplicate is created that matches multiple scenarios set to Report Duplicate, how many Warnings will be created?

One | Once DupeBlocker finds a match and creates a Warning it stops checking additional Scenarios for matches.
Multiple | One Warning will be created for EACH matching scenario.

Question 49 of 70

49. Question

It is recommended that field history tracking be turned on for any key fields that may be overwritten in an auto-merge/auto-conversion.

Correct
Incorrect

Question 50 of 70

50. Question

If the amount of storage used for the DupeBlocker Scenario Keys table is more than 10% per object/per scenario, which key rebuild option should be used to ensure keys only exist for currently deployed scenarios?

Select the Rebuild Keys button for each deployed scenario
Select the Rebuild All Keys button in any scenario
From a Scenario View, check all scenarios, and click the Rebuild Scenario Keys button
From a Scenario View, check all deployed scenarios, and click the Rebuild Scenario Keys button

Question 51 of 70

51. Question

Where is the Key Builder Type selected?

In the DupeBlocker Settings tab
In the DupeBlocker Scenario Details for each scenario
In the Key Builder pop-up screen whenever a rebuild is initiated
The Key Builder Type is selected by default based on the number of records in the object the Scenario is based on

Question 52 of 70

52. Question

When multiple rules are specified:

They are AND'd together, so all fields included in the rules will need to match for the scenario to return a match
They can be OR’d by enabling the Rule Logic option
Duplicates will be identified when the match threshold is 90% or more
Duplicates will be identified when the match threshold is 75% or more

Question 53 of 70

53. Question

Jill has set up 2 rules to match Last Name and Email exactly.

She only wants to evaluate records where the email is not blank.

What additional step does she need to take to configure her scenario correctly?

Nothing, by default DupeBlocker will only evaluate records where the fields being matched on are populated
Add a Scenario Object Filter: Email != Blank (leave value empty)
Check the Match Blank option on the email rule
Check the Populated Only option on the email rule

Question 54 of 70

54. Question

In XYZ’s org the Email field is required, but many times users do not have an email for the Lead they are entering so they use placeholders (e.g. [email protected], [email protected], etc.)

XYZ also wants to detect valid duplicates JUST on the Email field.

How can the Scenario be updated to not trigger when the record being inserted/updated contains one of the placeholder emails?

No changes need to be made. By default, DupeBlocker will filter out anything that does not appear to be an actual valid email.
Update the Email Exclusion list in DupeBlocker Settings.
Add an Object Filter where email != [email protected],[email protected] (and include any other non-valid emails that may be entered by users).
There is no way to filter out records with specific Emails.

Question 55 of 70

55. Question

When records are merged from a DupeBlocker Warning which of the following statements is NOT true?

The Warning that the records were merged from will be deleted along with any other Warnings that would only contain a single Potential Duplicate record after the merge is complete.
The merged record (the non-master) will be deleted from all existing Warnings.
The Warning will remain with only a single Potential Duplicate record.
The non-master record is deleted and can be found in the Salesforce recycle bin.

Question 56 of 70

56. Question

If a record is updated such that it no longer meets the scenario criteria, what happens to any associated Warnings?

*Assume any existing warnings only contain two potential duplicate records*

The Warning will automatically be deleted since the records no longer match.
The Warning will remain and will need to be manually deleted as Warnings are not re-evaluated for validity every time a record is updated.
The Warning will remain with only the single Potential Duplicate Record for the other matching record.
The original Warning will be deleted and a new Warning will be created with only a single Potential Duplicate record for the other matching record.

Question 57 of 70

57. Question

Warnings/Potential Duplicates can be monitored from:

(Select all that apply)

The DupeBlocker Warnings related list on the Scenario object
The DupeBlocker Warnings tab
Directly within a record from either the DupeBlocker Potential Duplicates related list or the Inline Duplicates Page
The DupeBlocker DashBoard and related Reports

Question 58 of 70

58. Question

When converting Leads from a Warning, what conversion options are available?

(Select all that apply)

Specifying a Lead Status for the converted Lead
Overwriting the Lead Source on the converted Contact
Creating an Opportunity
Creating a notification Task for the Contact Owner
Overwriting any field on the Contact/Account with data from the Lead record

Question 59 of 70

59. Question

When enabling a custom object, there must be at least one record for the object in Salesforce, otherwise an error will be displayed.

Correct
Incorrect

Question 60 of 70

60. Question

After installing and deploying, all records in Salesforce will be scanned for duplicates.

Correct
Incorrect

Question 61 of 70

61. Question

The DupeBlocker Settings tab must be selected after install to create a DupeBlocker license and load the default scenarios and settings.

Correct
Incorrect

Question 62 of 70

62. Question

Which Salesforce edition requires purchasing the API add on to use DupeBlocker?

Unlimited
Enterprise
Developer
Professional

Question 63 of 70

63. Question

Select the Match on Insert Actions.

(Select all that apply)

Do Not Insert
Do Nothing
Custom Apex Code
Redirect to Existing
Redirect to VisualForce Page

Question 64 of 70

64. Question

DupeBlocker limits the total number of scenario rules across all scenarios that apply to a specific object type to a total of ______.

40
20
30
100

Question 65 of 70

65. Question

John has a Lead to Account scenario set to match the Lead email address to the Account website with the Relaxed Domain mapping type selected.

Which of the following will be detected as duplicates?

(Select all that apply)

[email protected] and www.crmfusion.com/
[email protected] and www.crmfusion.com
[email protected] and https://www.crmfusion.com.uk
[email protected] and www.crmfusion.com

Question 66 of 70

66. Question

When using the Numeric mapping type, what values will (480) 555-1212 match to?

(Select all that apply)

4805551212
480.555.1212
(480) 555-1212
480-555-1212

Question 67 of 70

67. Question

The Fuzzy matching engine will match which of these values?

(Select all that apply)

IBM and International Business Machines
Smith and Smitty
Pippy's Sweet Tarts and Poppy's Sweet Tarts
Tom and Tim

Question 68 of 70

68. Question

The Alpha Clean matching engine will match which of these values?

Stefan, Jones, Halifert, Inc. | Stefan, Jones, Inc.
123 North Main St | 123 N Main St
José | Jose
All answers are correct
None of the answers are correct

Question 69 of 70

69. Question

Select the Match on Update Actions.

(Select all that apply)

Do Not Update
Do Nothing
Custom Apex Code
Auto-Merge
Redirect to VisualForce Page

Question 70 of 70

70. Question

What additional configuration steps are required for DupeBlocker to function properly with Person Accounts? (Select all that apply)

DupeBlocker is not compatible with Person Accounts.
Two formula fields need to be added to properly display the name of Person Accounts being linked to the DupeBlocker Potential Duplicates object.
On the DupeBlocker Scenario Edit screen, the Person Account Scenario box must be checked.
Related list properties on the DupeBlocker Warning Object must be updated to properly display new formula fields added to the DupeBlocker Potential Duplicate object.

DupeBlocker

DupeBlocker

Test Summary

Information

Results

Results

Categories

1. Question

2. Question

3. Question

4. Question

5. Question

6. Question

7. Question

8. Question

9. Question

10. Question

11. Question

12. Question

13. Question

14. Question

15. Question

16. Question

17. Question

18. Question

19. Question

20. Question

21. Question

22. Question

23. Question

24. Question

25. Question

26. Question

27. Question

28. Question

29. Question

30. Question

31. Question

32. Question

33. Question

34. Question

35. Question

36. Question

37. Question

38. Question

39. Question

40. Question

41. Question

42. Question

43. Question

44. Question

45. Question

46. Question

47. Question

48. Question

49. Question

50. Question

51. Question

52. Question

53. Question

54. Question

55. Question

56. Question

57. Question

58. Question

59. Question

60. Question

61. Question

62. Question

63. Question

64. Question

65. Question

66. Question

67. Question

68. Question

69. Question

70. Question