Exam PL-600 topic 2 question 13 discussion

I think correct answer is A, C, D by exclusion. DataFlow, workfow and Power Automate can apply business logic and trasformation. Instead Business Rule and Duplicate Detection Rule can't. The last answer can block record creation but not change values....

I'd go ABD as well, although C&D seem interchangeable, it seems more likely the answer would be D just due to recency bias.

I agree with AI.

the question is what can create data inconsistencies between two systems? i would rule out Business Rules because they work onload of a form and does not directly modify the data. if you had duplicate detection (and prevention to create duplicates) in one system and while in the other it allows duplicates this could be another source of inconsistencies. However, the 3 problems do NOT relate to this problem. therefore i rule out B and E, remaining the solution A, C, D. though i think it is an odd question after all. classic and power automate could make issues because they do not queue requests in a sequential order.

ADE. Classic workflows are used to automate business processes, including the updating of records in the Power Platform. However, they are less likely to cause the observed differences, as they have been superseded by Power Automate cloud flows

For me the answer is ADE. Classic workflows are used to automate business processes, including the updating of records in the Power Platform. However, they are less likely to cause the observed differences, as they have been superseded by Power Automate cloud flows

A: A dataflow can certainly cause the problems described. Note: "Connects to a Power Platform environment". It doesn't necessarily say that there is an application in this environment. It could be used for Power BI reporting and the data is being pulled into it for that purpose. Otherwise, using a Dataflow for updating a lead table (especially if it were Dynamics) doesn't sound like a good idea to me. D: Power Automate Flow can definitely be used for integration purposes and cause these problems. B: Business Rule can change the owner whilst a legacy flow cannot. Topic and telephone number issue are very unlikely to be caused by a legacy flow or business rule. So, I'm opting for B. E: Duplicate data rules seems very unlikely.

All have actions on data

Classic workflow has been replaced with Power automate flow. https://docs.microsoft.com/en-us/power-automate/replace-workflows-with-flows

ACD is correct answer. No any point in question talks about data duplication and Business Rules dont fit here as no point talks about fields visibility or any other cosmetic impacts.

I vote for ACD

BCD is correct answer

A D E Why A? - The owner data in the lead table and the third-party application do not match. This seems like an incorrect mapping in the Data flow. Why D? - There are differences in how telephone numbers are formatted. This seems like Automated flow that changes the format of a number, could also be done via data flows... Why E? - The Topic column has more information than the related record from the marketing application. "The Merge option is available only for Account, Lead, and Contact entities." https://docs.microsoft.com/en-us/power-platform/admin/detect-duplicate-records

I think it is BDE.

Explanation doesn't match the "Correct Answer" letters. If you go by the explanation, then the answer should be ABE. They're saying that C = Duplicate detection in the explanation.

I wouldn't use a Dataflow for integration nor should you so that leaves B (if it fires at entity level) , C, D ... E is not relevant.

I'd choose ABD