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

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

Question #: 33
Topic #: 8

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

AnyAirlines wants to create a new marketing campaign that sends customers special offers every month based on their accrued loyalty points. There is an existing integration for customer data using MuleSoft's API-led three-tier strategy. Loyalty information exists in an external system that can be accessed via an HTTP endpoint provided by the system, but has no current integration. The external ID used will be email address.

The desired output is a CSV file containing customers that includes only the top 10 percent of loyalty point holders.

What is the most efficient way to meet this requirement?

A1. Have the MuleSoft team develop a new integration that includes a System API to the Loyalty system and uses the existing Customer System API.
2. Create a Process API to output the final results.
3. Create an Experience API for the business consumers to initiate the integration.

B1. Create a MuleSoft Composer flow that utilizes the current Customer integration to select all customers.
2. Create an additional MuleSoft Composer flow that retrieves all the Loyalty information.
3. Create a MuleSoft Composer flow that combines the two previous results and outputs the top 10 percent to a CSV file.

C1. Have the MuleSoft team develop a new integration that includes a new System API to both the Customer and Loyally systems.
2. Create a Process API to output the final results.
3. Create an Experience API for the business consumers to initiate the integration.

D1. Create a Salesforce Flow that retrieves the Contact data.
2. Create a Salesforce Flow that retrieves the Loyalty data.
3. Create a Flow Orchestration that uses the two flows and outputs the result to a CSV file.

Show Suggested Answer

Suggested Answer: A

Develop System API for Loyalty System: The first step is to develop a new System API that integrates with the Loyalty system. This API will handle communication with the external system via the provided HTTP endpoint.

Utilize Existing Customer System API: Use the existing System API for customer data to retrieve necessary customer information. Combining these APIs ensures a modular approach and reuse of existing assets.

Create Process API: Develop a Process API that combines data from both the Customer and Loyalty System APIs. This API will process the data, apply business logic to filter the top 10 percent of loyalty point holders, and format the results.

Create Experience API: Develop an Experience API to serve the business consumers. This API will provide a user-friendly interface for initiating the integration and retrieving the results as a CSV file.

by Christiane at Nov 21, 2025, 11:46 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

Jerlene

3 days ago

Option B is too complicated for just a CSV output.

upvoted 0 times

...

Tawanna

8 days ago

Wait, can we really trust the external system's data?

upvoted 0 times

...

Cherry

27 days ago

I agree, leveraging the current System API is smart!

upvoted 0 times

...

Francoise

1 month ago

Option A seems the most efficient with the existing APIs.

upvoted 0 times

...

Deeanna

1 month ago

Option A looks good, but I'm not a fan of the Experience API. Seems like an unnecessary layer of complexity.

upvoted 0 times

...

Irma

1 month ago

Haha, Option D with Salesforce Flows? That's like trying to fit a square peg in a round hole. MuleSoft is clearly the better choice here.

upvoted 0 times

...

Javier

2 months ago

Option C is overkill. Why create a new System API for both systems when you can just add the Loyalty integration separately?

upvoted 0 times

...

Peter

2 months ago

I agree, Option B is the way to go. Keeping the integration modular and reusable is key for future scalability.

upvoted 0 times

...

Broderick

2 months ago

Option B seems the most efficient and straightforward approach. Leveraging the existing Customer integration and adding a new Loyalty integration is a clean way to meet the requirement.

upvoted 0 times

...

Ronny

2 months ago

I think option C might be overkill since it suggests creating a new System API for both systems, which seems unnecessary if we already have one for customers.

upvoted 0 times

...

Roslyn

2 months ago

I'm not entirely sure, but I feel like using MuleSoft Composer in option B could be simpler for quick integrations, right?

upvoted 0 times

...

Vince

2 months ago

I'm a little unsure about the Salesforce Flow option. I don't have much experience with that, so I'll need to do some research to see if that's a viable approach here.

upvoted 0 times

...

Marge

3 months ago

I'm feeling pretty confident about this one. Option B looks like the most efficient approach, allowing me to reuse the existing Customer integration and then just add the Loyalty piece.

upvoted 0 times

...

Shenika

3 months ago

Okay, I think I've got a good handle on this. The key is to leverage the existing Customer integration and then pull in the Loyalty data separately before combining the results.

upvoted 0 times

...

Jules

3 months ago

I prefer option B. Composer flows are easier to manage.

upvoted 0 times

...

Kayleigh

3 months ago

I remember studying the API-led approach, and I think option A makes sense since it leverages the existing Customer System API.

upvoted 0 times

...

Cherilyn

3 months ago

I think option A is the best. It uses existing APIs efficiently.

upvoted 0 times

...

Bernardine

4 months ago

I practiced a similar question about integrating different systems, and I feel like option D with Salesforce Flows could work, but I'm not sure if it's the best fit for this scenario.

upvoted 0 times

...

Casie

4 months ago

I’m leaning towards D. Salesforce flows are familiar to many.

upvoted 0 times

...

Olen

4 months ago

Hmm, I'm a bit confused about the different API options here. I'll need to review the MuleSoft documentation to understand the differences between System, Process, and Experience APIs.

upvoted 0 times

...

Hyman

4 months ago

This looks like a pretty straightforward integration problem, but I'll need to think through the details carefully to make sure I don't miss anything.

upvoted 0 times

...