PL-600 Exam - Question 138

Question

HOTSPOT -You are conducting performance testing for a Microsoft Power Platform solution. The solution uses Power Automate cloud flows to query and synchronize data across 10 different tables based on various criteria. You make the following observations:✑ Internet speed during testing is fast (500 Mbps). ✑ There are 50 Dynamics real-time workflows in use. ✑ There are 63 Dynamics asynchronous workflows in use. ✑ There are 76 Power Automate cloud flows in use. You identify the following performance issues:✑ Data changes are slow to save. ✑ Background processes often take hours to complete. You need to recommend steps to resolve the performance issues. What should you recommend? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Hot Area:.

Examice · Accepted Answer

Box 1: Reduce usage of near real-time workflows

A real-time workflow can be converted to asynchronous workflow and back to real-time.

Box 2: Convert all Dynamics 365 workflows to Power Automate cloud flows.

Workflows are limited to Microsoft Dynamics 365/CRM application only.

Power Automate can span across multiple web-based services or applications at the same time.

Dynamics 365 CRM Workflows can be converted to Power Automate flows.

Reference:

https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/create-real-time-workflows https://rajeevpentyala.com/2019/12/11/d365-switching-from-workflow-to-microsoft-power-automate-flow/

Icky · Answer

I think its A and C (or 1 and 3). Be careful of these non-microsoft references. Some one writes a blog, doesn't meant its correct.

ftagliapietra · Answer

first question is A and second C

SaschaB · Answer

I'd go with 1 and 3 aswell.

The first question is a little ambiguous and could be 1 or 2. Switching to cloud flows and recuding load on your system can reduce process time. But assuming the Dataverse is in cloud already that won't do much. So 1 it is.

For the second question we need to reduce the runtime. That won't happen if we don't take out complexity or optimize the logic. No other option than 3 does that.

petertwilliams · Answer

1st part: I think "Reduce usage of near real-time workflows" as that will certainly slow down a save operation.
2nd part: Review and revise filters in cloud flow queries and conditional logic.
When I review flows from novices, this is an issue I notice - along with the total lack of use of "Data Operations" actions.
Also, my personal experience is that - at this time of writing - that legacy Dynamics 365 workflows execute quicker.

MrEz · Answer

1) A
2) C
turn 'all dynamics 365 workflows' cannot be right, for both answers. If ever you have at least 1 workflow that needs to be run (near) real-time (sync), you cannot / should not make a power automate, because power automate is always async.

for 2) i was wondering if the last part 'and conditional logic' is strictly tied to 'cloud flows' or if it is even open to d365 workflows because of the 'and'? Anyway, I have seen many times devs to action on inactive data and limiting to status=active helps a lot to reduce capacity usage.

VJ345 · Answer

Correct

Ninashnash · Answer

First answer should be 3.
Why?
The first issue is "Data changes are slow to save". 
Key data in question that is relevant to this issue is: The solution uses "Power Automate cloud flows" to "query and synchronize" data across 10 different tables based on "various criteria" .
To address this issue, option 3 , "review and revise filter in cloud flow... must be selected . "query and synchronize" is clearly relevant to filter and save.

javos21 · Answer

Has to be 1 and 3. If background processes are taking long, why convert everything to cloud flows which are async. Thats adding more background processes

PL-600 Exam - Question 138

Discussion