Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

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

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

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.

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

Get Premium Salesforce Certified MuleSoft Hyperautomation Developer (Mule-Dev-202) Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
39 comments · newest first
FR
Freida 11 months ago
Option E could work too, but it feels a bit hacky.
CA
Carin 11 months ago
Wait, can we really have a flow that takes that long?
HA
Han 12 months ago
But waiting 24 hours? That seems excessive.
TA
Tasia 12 months ago
Agree, C makes the most sense for efficiency.
SE
Serita 1 year ago
I think option C is the best way to handle it.
FE
Felicitas 1 year 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.
DA
Daniel 1 year 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.
CR
Cruz 1 year 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.
BU
Buck 1 year 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.
JA
Jacqueline 1 year 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.
JO
Johnetta 1 year 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.
LA
Lanie 1 year 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.
MA
Markus 1 year 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.
AR
Arthur 1 year 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.
DO
Dorinda 1 year 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.
VE
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?
TA
Tabetha 2 years ago
↳ replying to Verda
I bet the RPA process is powered by a team of mules running on a treadmill. 'Mule-Soft' Composer, am I right?
AN
Angelo 2 years ago
↳ replying to Verda
B) Wait for the RPA process to complete and invoke a second MuleSoft Composer flow via REST API.
HA
Haydee 2 years ago
↳ replying to Verda
A) Using best practices, how should the results be consumed by MuleSoft Composer?
YV
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.
KA
Katina 2 years ago
Hmm, E looks interesting. Checking on a schedule could be a good way to handle the long-running task without blocking the main flow.
BR
Brynn 2 years ago
↳ replying to Katina
Royal: Definitely. Creating a second flow that runs on a schedule to check the status of the RPA process is a smart way to handle it.
JO
Joni 2 years ago
↳ replying to Katina
Waiting for the RPA process to complete and using the results in the same flow could cause delays. E seems like a more efficient approach.
RO
Royal 2 years ago
↳ replying to Katina
I agree. It's important to have a way to check if the RPA process is complete without waiting indefinitely.
YU
Yuki 2 years ago
↳ replying to Katina
E looks like a good option. It's a way to handle the long-running task without blocking the main flow.
EL
Eleni 2 years ago
D is the way to go. Why create a whole new flow when you can just use the results in the same one? Efficiency is key!
ME
Merilyn 2 years ago
↳ replying to Eleni
Kanisha: Exactly, keeping it simple is the way to go.
KA
Kanisha 2 years ago
↳ replying to Eleni
Definitely, no need to create unnecessary complexity with a new flow.
MA
Marla 2 years ago
↳ replying to Eleni
I agree, using the results in the same flow is more efficient.
DA
Dallas 2 years ago
↳ replying to Eleni
Rosamond: Exactly, keeping it simple is always the best approach.
RO
Rosamond 2 years ago
↳ replying to Eleni
Definitely, no need to create unnecessary complexity with a new flow.
JO
Joana 2 years ago
↳ replying to Eleni
I agree, using the results in the same flow is more efficient.
DE
Denise 2 years ago
Option C seems like the best approach. Separating the flows makes it more modular and easier to maintain.
LY
Lyda 2 years ago
↳ replying to Denise
Option C does seem like a good choice for this scenario.
BO
Bobbye 2 years ago
↳ replying to Denise
I agree, having separate flows for different tasks is definitely more organized.
BR
Brett 2 years ago
I prefer option E, as it allows for better monitoring and control.
JI
Jina 2 years ago
But with option D, we might have to wait unnecessarily in the same flow.
ED
Edwin 2 years ago
I disagree, I believe option D is more efficient.
JI
Jina 2 years ago
I think option C is the best approach.
0/2000 characters

Save Cancel