Microsoft PL-500 Exam - Topic 3 Question 64 Discussion

Actual exam question for Microsoft's PL-500 exam

Question #: 64
Topic #: 3

You need to resolve the issue reported with the RailStatusUpdater flow.

What are two possible ways to achieve the goal? Each correct answer presents a complete solution.

NOTE: Each correct selection is worth one point.

APut the desktop flow action into a Do until loop. Run until the desktop flow is successful.

BCall a separate child cloud flow to perform the desktop flow a second time.

CCreate a duplicate action for the desktop flow and configure the duplicate action to run if the first desktop flow action fails.

DCreate a duplicate action for the desktop flow to run after the first desktop flow.

Show Suggested Answer

Suggested Answer: A, C

According to the scenario, the RailStatusUpdater flow sometimes fails because of network issues that prevent it from running a desktop flow on a machine. To resolve this issue, you can use one of these two methods:

Put the desktop flow action into a Do until loop that runs until the desktop flow is successful. This way, the cloud flow will retry running the desktop flow until it succeeds or reaches a maximum number of attempts.

Create a duplicate action for the desktop flow and configure the duplicate action to run if the first desktop flow action fails. This way, the cloud flow will have a second chance to run the desktop flow if the first attempt fails.

by Hoa at May 05, 2025, 08:03 AM

Limited Time Offer

25%

Off

Get Premium PL-500 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Nakita

5 months ago

D seems unnecessary, why run it again if the first one fails?

upvoted 0 times

...

Brock

5 months ago

I think B could work too, calling a child flow is smart.

upvoted 0 times

...

Keneth

5 months ago

C sounds good, but isn't duplicating actions a bit risky?

upvoted 0 times

...

Tammara

6 months ago

Wait, can we really just loop it? That feels off.

upvoted 0 times

...

Zona

6 months ago

A is a solid choice, looping until success makes sense.

upvoted 0 times

...

Precious

6 months ago

I feel like option D is just running the same flow again without addressing the failure. It doesn't seem efficient to me.

upvoted 0 times

...

Emilio

6 months ago

Option C seems like it could work too, but I’m a bit confused about whether duplicating the action is really necessary.

upvoted 0 times

...

Howard

7 months ago

I remember discussing child flows in class, so option B might be a good approach. It seems like a solid way to handle retries.

upvoted 0 times

...

Nieves

7 months ago

I think option A sounds familiar, like we practiced a similar scenario where we used a loop to ensure success. But I'm not entirely sure if it's the best choice here.

upvoted 0 times

...

Jettie

7 months ago

I'm leaning towards option C - creating a duplicate action for the desktop flow and configuring it to run if the first one fails. That seems like a solid way to handle the issue without having to rely on a loop or a separate child flow. I think I'll go with that one.

upvoted 0 times

...

Donte

7 months ago

Option B, calling a separate child cloud flow to perform the desktop flow a second time, seems like an interesting approach. I'm curious to learn more about how that would work in practice. I might give that one a try and see if I can make it work.

upvoted 0 times

...

Kristel

7 months ago

Hmm, I'm a bit unsure about this one. I'm trying to decide between A and C. I think creating a duplicate action for the desktop flow and configuring it to run if the first one fails could also be a good approach. I'll have to think it through a bit more.

upvoted 0 times

...

Elizabeth

7 months ago

This seems like a straightforward question. I'd go with option A - putting the desktop flow action into a Do until loop and running it until it's successful. That should help resolve the issue.

upvoted 0 times

...

Tamesha

11 months ago

I'm just glad they didn't ask us to debug the RailStatusUpdater flow itself. That would have been a real train wreck!

upvoted 0 times

...

Inocencia

11 months ago

Ah, the age-old question of how to handle desktop flow failures. I say, if in doubt, add more flows! The more the merrier, I always say.

upvoted 0 times

Harrison

10 months ago

B) Call a separate child cloud flow to perform the desktop flow a second time.

upvoted 0 times

...

Kristofer

10 months ago

A) Put the desktop flow action into a Do until loop. Run until the desktop flow is successful.

upvoted 0 times

...

Casey

11 months ago

A seems a bit too simple. A do-until loop might work, but it feels like a bandaid solution. I'd prefer a more robust approach like B or C.

upvoted 0 times

...

Truman

11 months ago

D is a good choice too. Running the desktop flow twice can help ensure the issue is resolved, especially if the first attempt fails.

upvoted 0 times

Maxima

10 months ago

D is a good choice too. Running the desktop flow twice can help ensure the issue is resolved, especially if the first attempt fails.

upvoted 0 times

...

Elinore

10 months ago

D) Create a duplicate action for the desktop flow to run after the first desktop flow.

upvoted 0 times

...

Terrilyn

10 months ago

B) Call a separate child cloud flow to perform the desktop flow a second time.

upvoted 0 times

...

Johanna

11 months ago

A) Put the desktop flow action into a Do until loop. Run until the desktop flow is successful.

upvoted 0 times

...

Belen

12 months ago

That's a valid point, Maynard. Having a duplicate action as a fail-safe could definitely help in resolving the issue with the RailStatusUpdater flow.

upvoted 0 times

...

Maynard

12 months ago

I disagree, I believe option C is better. Creating a duplicate action for the desktop flow and configuring it to run if the first one fails provides a backup plan.

upvoted 0 times

...

Belen

1 year ago

I think option A is a good idea. Putting the desktop flow action into a Do until loop seems like a logical solution.

upvoted 0 times

...

Jess

1 year ago

I think B and C are the best options. Calling a separate child cloud flow or creating a duplicate action for the desktop flow gives us more control over the flow execution.

upvoted 0 times