Discuss Salesforce Salesforce Certified MuleSoft Hyperautomation Developer (Mule-Dev-202) Exam Topic 1 Question 9

A non-technical employee from AnyAirlines creates a hyperautomation solution. The solution needs to meet the following criteria:

The process needs to begin when a record is created in Salesforce.

Then, it needs to pass data to a pre-existing RPA process which includes a User Task for data integrity purposes.

The output of the RPA process needs to be used to create a record in NetSuite.

According to best practices, how should this automated process be structured?

A1. A MuleSoft Composer flow triggers on the creation of the record and calls the RPA process.
2. Then, the same flow uses the response to create a record in NetSuite.
B 1. A Salesforce flow triggers on the creation of the record and calls too RPA process.
2. Then, the same flow uses the response to create a record in NetSuite.

C1. A MuleSoft Composer flow triggers on the creation of the record and calls the RPA process.
2. Then, a second MuleSoft Composer flow triggers when the RPA process is completed and creates a record in NetSuite.

D1. A Salesforce flow triggers on the creation of the record and makes an outbound request to a MuleSoft Composer flow.
2. Then, the same MuleSoft Composer flow calls the RPA process and uses the result to create a record in NetSuite.

Suggested Answer: A

To structure the automated process to meet the given criteria, the following approach is recommended:

MuleSoft Composer Flow Triggers on Record Creation:

Use MuleSoft Composer to create a flow that is triggered when a new record is created in Salesforce. This is done by setting up a trigger event in MuleSoft Composer that listens for new record creation events in Salesforce.

Call the RPA Process:

Once the flow is triggered, it should call the pre-existing RPA process. MuleSoft Composer can invoke MuleSoft RPA bots, and you can pass the necessary data from the Salesforce record to the RPA process.

The RPA process will include the User Task for data integrity purposes.

Use the RPA Process Output to Create a Record in NetSuite:

After the RPA process completes, the MuleSoft Composer flow can capture the output from the RPA process.

The same MuleSoft Composer flow will then use this output to create a record in NetSuite, ensuring a seamless data transfer and process automation.

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

45 comments · newest first

Rosio 11 months ago

D sounds complicated, not sure it’s the best choice.

Mari 11 months ago

Wait, can a non-tech person really pull this off?

Yesenia 12 months ago

C is interesting, but why use two flows?

Vanda 12 months ago

I think B is better for keeping it all in Salesforce.

Gail 1 year ago

Option A seems the most straightforward.

Alida 1 year ago

I'm a bit confused about whether using two separate flows is a best practice. I thought keeping it all in one flow was generally preferred for simplicity.

Norah 1 year ago

I practiced a similar question where the flow structure was crucial. I feel like option D might be the best since it clearly separates the tasks.

Venita 1 year ago

I think a Salesforce flow might be more straightforward since it directly triggers on record creation, but I can't recall if it can handle the RPA call effectively.

Rachael 1 year ago

I remember we discussed how MuleSoft Composer can integrate with various systems, but I'm not sure if it should be the first trigger here.

Silvana 1 year ago

This is a great example of a real-world integration challenge. I feel pretty confident I can work through this step-by-step and come up with a solid solution that meets all the requirements. The key will be identifying the right integration patterns and tools to tie everything together efficiently.

Kiley 1 year ago

Based on the criteria, I'm leaning towards option C. Having a separate MuleSoft flow to handle the RPA integration and then trigger the NetSuite record creation seems like it would provide the most flexibility and maintainability. But I'll double-check the other options just to be sure.

Leatha 1 year ago

I'm a little confused about the best practice part of the question. Is there a specific recommended architecture or design pattern we should be following here? I want to make sure I don't miss any important considerations.

Zena 1 year ago

Okay, let me think this through step-by-step. We need to trigger something when a record is created in Salesforce, then pass that data to an existing RPA process, and finally use the output to create a record in NetSuite. I think the key is figuring out the best way to orchestrate all of those moving parts.

Valentin 1 year ago

This seems like a pretty straightforward integration problem, but I want to make sure I understand the requirements clearly before I start planning my approach.

Dominga 1 year ago

Okay, let me see. I think the WebType ACL feature is what allows the ASA to handle non-standard applications and web resources on a clientless SSL VPN. But I'm not 100% confident on that.

Margurite 1 year ago

I think option B has the right sequence, but I'm a bit confused about whether recovery should come before closure or after.

Justine 2 years ago

That's a valid point, Junita. Both options C and D have their merits. It ultimately depends on the specific requirements and capabilities of the organization.

Junita 2 years ago

I prefer option D because it involves Salesforce triggering the process and then using MuleSoft Composer for the rest. It seems more organized to me.

Mammie 2 years ago

I agree with Justine. Using MuleSoft Composer for both steps ensures a seamless integration and efficient automation process.

Nakisha 2 years ago

As a wise man once said, 'Keep it simple, stupid.' Option C checks all the boxes and looks the most straightforward to implement. Plus, it'll be easy to debug if something goes wrong.

Corrinne 2 years ago

↳ replying to Nakisha

Yeah, simplicity is key. Option C makes the most sense for this hyperautomation solution.

Melynda 2 years ago

↳ replying to Nakisha

I think option C is the way to go as well. It's important to keep things straightforward for easier troubleshooting.

Thurman 2 years ago

↳ replying to Nakisha

I agree, option C seems like the best choice. It keeps the process simple and easy to follow.

Matthew 2 years ago

Hah, a non-technical employee creating a hyperautomation solution? Sounds like a recipe for some entertaining troubleshooting sessions. I'd go with option C just to keep things nice and tidy.

Winfred 2 years ago

↳ replying to Matthew

Option C it is then, let's hope the non-technical employee can handle it smoothly.

Jodi 2 years ago

↳ replying to Matthew

Definitely, it's important to keep the process structured and easy to troubleshoot.

Elliot 2 years ago

↳ replying to Matthew

I agree, having a separate flow for the RPA process and NetSuite integration can help with organization.

Fletcher 2 years ago

↳ replying to Matthew

Option C seems like the best choice for this scenario.

Justine 2 years ago

I think option C is the best choice because it uses MuleSoft Composer for both triggering the RPA process and creating a record in NetSuite.

Laurel 2 years ago

I see your point, Rashad. Option D does seem efficient. But I still think option C provides better clarity and organization in the automation process.

Ammie 2 years ago

Well, this is an interesting one! Option B looks good, but I'm a bit worried about the potential performance impact of having a single Salesforce flow handling both the RPA call and the NetSuite record creation.

My 2 years ago

↳ replying to Ammie

Maybe we should consider Option C instead, with separate MuleSoft Composer flows for each step to improve performance.

Adell 2 years ago

↳ replying to Ammie

Option B does seem like a good choice, but I see your point about the performance impact.

Rashad 2 years ago

I prefer option D because it involves Salesforce triggering the process and then using MuleSoft Composer for the rest. It seems more streamlined to me.

Gilberto 2 years ago

I'm leaning towards option D. Using MuleSoft as the orchestrator between Salesforce and the RPA process seems like a solid architectural choice.

Whitley 2 years ago

↳ replying to Gilberto

Yes, using MuleSoft to connect Salesforce and the RPA process in option D seems like a strong architectural decision.

Carman 2 years ago

↳ replying to Gilberto

I agree, having MuleSoft as the orchestrator can streamline the process effectively.

Hollis 2 years ago

↳ replying to Gilberto

Option D sounds like a good choice. MuleSoft can help coordinate everything smoothly.

Octavio 2 years ago

I agree with Judy. Having two separate flows in MuleSoft Composer ensures a clear separation of tasks and makes the process more manageable.

Mozell 2 years ago

Option C seems the most straightforward approach. Separating the Salesforce flow and the MuleSoft flow makes the process more modular and easier to maintain.

Alyce 2 years ago

↳ replying to Mozell

Definitely, keeping the flows separate allows for better organization and maintenance in the long run.

Emiko 2 years ago

↳ replying to Mozell

Option C also ensures that the process is more modular and can be easily scaled if needed.

Yuette 2 years ago

↳ replying to Mozell

Having separate flows for Salesforce and MuleSoft does make it easier to manage and troubleshoot.

Noel 2 years ago

↳ replying to Mozell

I agree, option C seems like the best choice for this hyperautomation solution.

Judy 2 years ago

I think option C is the best choice because it uses MuleSoft Composer for both triggering the RPA process and creating a record in NetSuite.

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