Exam PL-200 topic 1 question 10 discussion

Duplicate detection on Lead will not trigger on Opportunity creation/update The rule must be created as follow - Base Record Type: Opportunity - Matching Record Type: Lead - Base Record field: Account - Matching Record field: Parent Account for Lead (or another if you use a different one) - Criteria: Exact Match So answer is Opportunity - Account

For me is "Opportunity" and "Account". During the Opportunity creation should activate the Duplicate Detection rule, and check on related Customer (Account) if there are related lead to that Account. Isn't it?

Duplicate detection rule criteria: Base record type Value: Opportunity We want to prevent the creation of a new Opportunity if there are existing Leads for the same customer. Therefore, the base record type is Opportunity. Duplicate detection rule criteria: Base record field Value: Account We need to check if the Account associated with the new Opportunity already has existing Leads. The Account field is the common link between Opportunities and Leads.

Base Record Type: Opportunity This ensures that when an opportunity is being created, the system checks for existing leads for the customer. Base Record Field: Account This field specifies that the rule should look at the customer (Account) to identify duplicates. By matching the Account, the rule can check if there are any existing leads for the same customer before allowing the creation of the new opportunity.

You have to break this question down to understand what is being asked. "You need to ensure that there are no leads for a customer before you create a new opportunity for the customer." This means you are manually creating an Opportunity and want to check back to see if there are any Leads prior to doing so. This has nothing to do with converting a Lead to an Opportunity. When they say "customer" what does that mean in Microsoft words? It means Account. So you need to ensure when an Opportunity is created that there is no Leads associated to the matching Account.

ddu has the right solution and I just tested it. The base entity or table needs to be the one that triggers is. You are trying to create an opportunity so it has to be opportunity. What the solution does is compare the account on the opportunity to the accounts on the leads, if any of the active leads have the same account, then the rule is triggered.

The customer engagement apps (Dynamics 365 Sales, Dynamics 365 Customer Service, Dynamics 365 Field Service, Dynamics 365 Marketing, and Dynamics 365 Project Service Automation), include default duplicate detection rules for accounts, contacts, and leads, but not for other types of records. So the answer for 1st question shall be Lead, does that make sense?

Let's go over the definitions first in Data Management > duplicate detection rules Base record type: record type of the record being evaluated for potential duplicates. Matching record type: record type of the record being evaluated as potential duplicate. Which entity is being evaluated for potential duplicate? Lead. Which entity is being evaluated as a potential duplicate ? Opportunity Which field of the record is being evaluated for duplicate? account (i.e. base record field and matching record field)

when creating a new opportunity, the system checks for any existing leads related to the same customer (originating lead) and prevents the creation of the opportunity if a lead already exists. The answer is: Opportunity - Originating lead

"The Merge option is available only for Account, Lead, and Contact entities. The Merge option will only be enabled if a duplicate record of the same table is selected. Merging duplicate records from different tables is not supported." - correct answer Lead-Account

Opportunity, Account

I've tested it this morning and it is indeed Opportunity and Account, i got the popup when tried to create new Opp with already existing open lead for the same account

Given answer is correct. The fact that an opportunity is created is irrelevant. It doesn't say it needs to be triggered on create, the requirement is that leads should be unique.

The scope for this question to ensure no duplicate opportunity for a customer, hence the trigger should be opportunity and Account

I think the answer is correct, because question duplicate detection rule criteria, so the condition should be Lead- Account

Opportunity, Account

Opportunity - Account