Salesforce Certified MuleSoft Hyperautomation Developer (Mule-Dev-202) Exam - Topic 4 Question 4 Discussion

Actual exam question for Salesforce's Salesforce Certified MuleSoft Hyperautomation Developer (Mule-Dev-202) exam

Question #: 4
Topic #: 4

[All Salesforce Certified MuleSoft Hyperautomation Developer (Mule-Dev-202) Questions]

An RPA process is invoked by a MuleSoft Composer flow. The RPA process has a User Task that can take up to 24 hours to complete.

AUsing best practices, how should the results be consumed by MuleSoft Composer?

BWait for the RPA process to complete and invoke a second MuleSoft Composer flow via REST API.

CCreate a second MuleSoft Composer flow that starts when the RPA process is complete.

DWait for the RPA process to complete and use the results in the same MuleSoft Composer flow.

ECreate a second MuleSoft Composer flow that runs on a schedule and checks if the RPA process is complete.

Show Suggested Answer

Suggested Answer: C

When an RPA process involves a User Task that can take a significant amount of time (up to 24 hours) to complete, it is best to use a follow-up mechanism to handle the results once the process is finished:

Second MuleSoft Composer Flow:

Create a second MuleSoft Composer flow that is triggered when the RPA process completes. This ensures that the first flow is not held up while waiting for the long-running RPA process to finish.

The second flow can start based on an event, such as the completion status of the RPA process, ensuring timely and efficient processing of the results.

Trigger Mechanism:

Configure the RPA process to notify MuleSoft Composer when it is complete, possibly using a REST API or another integration method.

Best Practices:

This approach adheres to best practices by keeping flows modular and focused on specific tasks, making them easier to manage and troubleshoot.

MuleSoft Composer Documentation

MuleSoft RPA Documentation

by Marjory at Jul 02, 2024, 09:20 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified MuleSoft Hyperautomation Developer (Mule-Dev-202) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Freida

3 months ago

Option E could work too, but it feels a bit hacky.

upvoted 0 times

...

Carin

3 months ago

Wait, can we really have a flow that takes that long?

upvoted 0 times

...

Han

3 months ago

But waiting 24 hours? That seems excessive.

upvoted 0 times

...

Tasia

4 months ago

Agree, C makes the most sense for efficiency.

upvoted 0 times

...

Serita

4 months ago

I think option C is the best way to handle it.

upvoted 0 times

...

Felicitas

4 months ago

I recall that waiting for a process to finish isn't ideal, so option B seems risky. I wonder if option D could be a viable alternative too.

upvoted 0 times

...

Daniel

4 months ago

I think we practiced a similar question where we had to avoid blocking flows. I might lean towards option C, but I'm not completely confident.

upvoted 0 times

...

Cruz

4 months ago

I'm not entirely sure, but I feel like option E could work since it checks periodically for completion. It seems like a safer approach.

upvoted 0 times

...

Buck

5 months ago

I remember we discussed how waiting for long processes can lead to timeouts, so I think option C might be the best practice here.

upvoted 0 times

...

Jacqueline

5 months ago

Whoa, 24 hours for the RPA process? That's a long time. I'll need to be careful to avoid any timeouts or issues with the MuleSoft integration. I'll review the options closely and choose the one that seems most robust.

upvoted 0 times

...

Johnetta

5 months ago

This is a good test of my understanding of best practices for integrating long-running processes. I'm feeling confident I can work through this and identify the most efficient solution.

upvoted 0 times

...

Lanie

5 months ago

Okay, I think I've got a strategy for this. The key is to avoid blocking the MuleSoft Composer flow while the RPA process is running. I'll likely go with option C and create a separate flow to handle the RPA completion.

upvoted 0 times

...

Markus

5 months ago

Hmm, I'm a bit confused on the best approach here. Should I wait for the RPA process to complete or try to handle it asynchronously? I'll need to review the options carefully.

upvoted 0 times

...

Arthur

5 months ago

This seems like a tricky one. I'll need to think through the best way to handle the long-running RPA process and how to integrate it with the MuleSoft Composer flow.

upvoted 0 times

...

Dorinda

5 months ago

Okay, let's see. The options range from 40 to 256 bits, which covers a pretty wide spectrum of encryption strengths. I'll need to recall my knowledge of common encryption standards to narrow this down.

upvoted 0 times

...

Verda

2 years ago

I bet the RPA process is powered by a team of mules running on a treadmill. 'Mule-Soft' Composer, am I right?

upvoted 0 times

Tabetha

2 years ago

I bet the RPA process is powered by a team of mules running on a treadmill. 'Mule-Soft' Composer, am I right?

upvoted 0 times

...

Angelo

2 years ago

B) Wait for the RPA process to complete and invoke a second MuleSoft Composer flow via REST API.

upvoted 0 times

...

Haydee

2 years ago

A) Using best practices, how should the results be consumed by MuleSoft Composer?

upvoted 0 times

...

Yvonne

2 years ago

B is the classic choice, but I like the idea of C. Keeps things nicely decoupled and event-driven. Plus, it's more fun to say 'MuleSoft Composer' out loud.

upvoted 0 times

...