Exam MB-230 topic 1 question 31 discussion

No Similarity rules are not Duplicate detection rules! They are used to search for similar cases. https://docs.microsoft.com To my mind the answers are B and C. The C because you have to have enabled privilege. E is wrong because in the documentation it is said: For a field to be eligible for exact matching, it must meet the following criteria: • It can't be a Primary Key. • It can't be these types: String, Memo, Picklist, Boolean, Whole Number, Two Options, Date and Time, or Floating Point Number. • It can be these types: Lookup, OptionSet, Customer, Owner, Status, State, Status Reason. In the solution Modified On is Date and Time, so it cannot be enabled for Similarity rules. /en-us/dynamics365/customer-service/suggest-similar-cases-for-a-case

1. Similarity Rule is now Duplication Rule. And a duplication rule cannot be activated/deactivated but published/unpublished, so D is the first correct answer. 2. If the modified-on field is not set to searchable, duplication rule cannot search for modified-on field on any records, the next correct answer is E.

Based on this article i don't see they mention: power automate, Modifiedon, publish similarity rule.

A. A Power Automate flow was not created. --> no idea how this could relate in the scenario here B. The similarity rule is deactivated. -> yes you should activate it C. The security role is not set to run the similarity rule. -> i don't see any way how to add security roles. and i don't see how this should make sense, you add security to teams or users D. The similarity rule was not published. -> you activate this rule, not publish it E. The Modified On field is not set to searchable in the customization of the case entity in the solution. -> ootb set searchable. i would never ever make duplicate detection on a date and time field as this would mean that it has been created in the very second 2 times. a humanoid could never do such thing. as soon as a humanoid creates duplicate records, there would be at least seconds if not minutes different in created on= first modified on date and time (seconds!) and therefore, it would not be a duplicate. the scenario set out is very strange

Seems only B is correct, Modified On cannot do exact match field, so the question is not updated / wrong.

Given answers BE are correct. https://www.inogic.com/blog/2020/09/how-to-use-advanced-similarity-rules-to-view-similar-case-suggestions/

Only B is correct : A. A Power Automate flow was not created. : we don't have any flow to create B. The similarity rule is deactivated. : correct C. The security role is not set to run the similarity rule. : we can not found this privilege in security role D. The similarity rule was not published. : cannot publish similitary rule, we can just activate or descativate E. The Modified On field is not set to searchable in the customization of the case entity in the solution. : we can not create a match field with type Date and time field

This question has no sense. 1. Modified On is searchable by default in Case entity 2. Modified On is not available as Field when you use Exact Match 3. A SR cannot be published

I think the answer is B and D