Question
You need to ensure that there are no leads for a customer before you create a new opportunity for the customer.
How can you use duplicate detection rules to achieve this goal? To answer, select the appropriate options in the answer area.
NOTE:
Each correct selection is worth one point.
Hot Area:
Explanation
Base record type: Opportunity — In a Dataverse duplicate detection rule the base record type is the table of the record being created or checked at that moment, and the matching record type is the table you compare it against. Because the check must fire when a new opportunity is created (looking for existing leads for that customer), Opportunity is the base and Lead is the matching record type; choosing Lead or Account as the base would run the check when a lead or account is saved, not when the opportunity is created.
Base record field: Account — The comparison has to be made on the field that identifies the customer, and on the Opportunity table that is the Account (customer) lookup, which is matched against the corresponding company/account value on the Lead records. Topic is only the free-text name of the opportunity and would not identify the customer, and Originating Lead only points at the single lead an opportunity was converted from, so it would never surface other existing leads for that customer.
