Salesforce Exam Salesforce MuleSoft Developer II Topic 1 Question 11 Discussion

Actual exam question for Salesforce's Salesforce MuleSoft Developer II exam

Question #: 11
Topic #: 1

[All Salesforce MuleSoft Developer II Questions]

An organization uses CloudHub to deploy all of its applications.

How can a common-global-handler flow be configured so that it can be reused across all of the organization's deployed applications?

Create a Mule plugin project

Create a common-global-error-handler flow inside the plugin project.

Use this plugin as a dependency in all Mute applications.

Import that configuration file in Mute applications.

Create a common-global-error-handler flow in all Mule Applications Refer to it flow-ref wherever needed.

CCreate a Mule Plugin project
Create a common-global-error-handler flow inside the plugin project.
Use this plugin as a dependency in all Mule applications
D.
Create a Mule daman project.
Create a common-global-error-handler flow inside the domain project.
Use this domain project as a dependency.

Show Suggested Answer

Suggested Answer: C

To configure a common-global-handler flow that can be reused across all of the organization's deployed applications, the developer should create a Mule Plugin project, create a common-global-error-handler flow inside the plugin project, and use this plugin as a dependency in all Mule applications. This way, the developer can import the common-global-error-handler flow in any application that needs it and avoid duplicating the error handling logic. Reference: https://docs.mulesoft.com/mule-runtime/4.3/error-handling#global-error-handler

by Soledad at Jul 13, 2024, 02:51 PM

Limited Time Offer

25%

Off

Get Premium Salesforce MuleSoft Developer II Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Gertude

3 months ago

Haha, imagine if the answer was 'Create a Mule Hamster project and use that as a dependency.' Now that would be a real curveball!

upvoted 0 times

...

Jamal

3 months ago

Option A looks good, but I'm a bit worried about the 'Mule plugin' part. Isn't that for more advanced use cases? Hmm, I'll have to think about this one.

upvoted 0 times

Silva

2 months ago

I see, I'll have to think about whether the benefits outweigh the complexity. Thanks for the explanation!

upvoted 0 times

...

Carrol

3 months ago

Yes, creating a Mule plugin project can be a bit advanced, but it allows for reusing the common-global-error-handler flow across all applications.

upvoted 0 times

...

Lilli

3 months ago

Option A looks good, but I'm a bit worried about the 'Mule plugin' part. Isn't that for more advanced use cases?

upvoted 0 times

...

Lottie

3 months ago

Nah, I don't like option B. Referencing the error handler flow-ref in each app seems like a maintenance nightmare waiting to happen.

upvoted 0 times

...

Jacob

3 months ago

I think option C is the most organized approach, using a plugin project for reusability.

upvoted 0 times

...

Levi

3 months ago

I prefer option B, it's simpler to just create the flow in each application.

upvoted 0 times

...

Mitsue

3 months ago

Option D seems a bit overkill to me. Creating a whole Mule domain project just for a common error handler feels like too much overhead.

upvoted 0 times

Troy

3 months ago

Yeah, Option D does seem like overkill. It's better to keep things simple and efficient.

upvoted 0 times

...

Trinidad

3 months ago

Option B might work for smaller projects, but for a larger organization, Option A is definitely the way to go.

upvoted 0 times

...

Joni

3 months ago

I agree, using a Mule plugin project makes it easier to manage and maintain the common error handler.

upvoted 0 times

...

Isreal

3 months ago

Option A seems like the best approach. It keeps things organized and reusable.

upvoted 0 times

...

Ronny

4 months ago

Hmm, I think option C is the way to go. Creating a Mule plugin project and using it as a dependency seems like the most efficient and reusable approach.

upvoted 0 times