Q: 9
You are creating a cloud flow that will use two Update Row actions to interact with Microsoft
Dataverse. Neither of these actions are dependent on each other.
You must minimize the amount of processing time required to complete the flow.
You need to implement the actions in the cloud flow.
Solution: Create a switch condition.
Does the solution meet the goal?
Options
Discussion
It’s B, pretty typical Microsoft trick question. Switch just decides conditional logic, won’t make the two updates run faster since they’re not parallel. You’d want parallel branches for that. I’ve seen similar gotchas on practice sets too but feel free to disagree if you see otherwise.
Option B If both updates need to run and not just one based on a condition, switch isn't the right fit here.
Switch is tempting but that just controls logic flow, not speed. B. The usual trap here is thinking switch adds parallelism.
Seen this type before on official practice materials, pretty sure it's B. Using a switch is for branching, but here parallel branches would save more time when both updates are independent.
Doesn't really meet the goal, so B. Switch is for branching, not parallel execution. To actually minimize processing time you’d want parallel branches. Open if anyone sees it differently but pretty sure B.
B tbh, switch is for branching logic not speed. Parallel branches are what minimizes processing time, not a switch condition.
I don’t think A works, switch is for decisions not running tasks in parallel. B.
Maybe B, since switch is a trap here. It won't parallelize the actions, parallel branch would minimize time.
A switch condition won’t make them run in parallel so B is right. Parallel branches would actually reduce the total processing time.
Not sure why everyone picks B, but I actually think it's A. Switch lets you handle both actions in one condition, right?
Be respectful. No spam.
