Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Exam MuleSoft Integration Architect I Topic 6 Question 14 Discussion

Actual exam question for Salesforce's MuleSoft Integration Architect I exam
Question #: 14
Topic #: 6
[All MuleSoft Integration Architect I Questions]

What is the MuleSoft-recommended best practice to share the connector and configuration information among the APIs?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Tammara at Sep 09, 2024, 07:03 PM

Limited Time Offer

25%

Off

Get Premium MuleSoft Integration Architect I Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Stefania
2 months ago
Haha, option C is just adding an unnecessary layer of complexity. Who wants to refactor all their APIs just to share a database connection? That's like trying to swim upstream with a bowling ball.
upvoted 0 times
Giuseppe
1 months ago
D) Create an API proxy for each System API and share the Database connector configuration with all the API proxies via an automated policy
upvoted 0 times
...
Jess
1 months ago
B) Build a separate Mule domain project for each API, and configure each of them to use a file on a shared file store to load the configuration information dynamically
upvoted 0 times
...
Craig
1 months ago
A) Build a Mule domain project, add the Database connector and configuration to it, and reference this one domain project from each System API
upvoted 0 times
...
...
Darci
2 months ago
I think creating an API proxy for each System API is the way to go, it provides more flexibility.
upvoted 0 times
...
Filiberto
2 months ago
I'm not sure, I think building separate domain projects for each API could also work.
upvoted 0 times
...
Leonida
3 months ago
I agree with Derrick, it makes sense to centralize the connector and configuration information.
upvoted 0 times
...
Antione
3 months ago
Option D with API proxies could also work, but it might be overkill for a simple database configuration scenario. A domain project is probably the simplest MuleSoft-recommended approach.
upvoted 0 times
Rebecka
2 months ago
Option D with API proxies could also work, but it might be overkill for a simple database configuration scenario. A domain project is probably the simplest MuleSoft-recommended approach.
upvoted 0 times
...
Barb
2 months ago
B) Build a separate Mule domain project for each API, and configure each of them to use a file on a shared file store to load the configuration information dynamically
upvoted 0 times
...
Joesph
2 months ago
A) Build a Mule domain project, add the Database connector and configuration to it, and reference this one domain project from each System API
upvoted 0 times
...
...
Hyun
3 months ago
I agree with Celestina. Option A is the cleanest and most efficient solution. Reusing the same database configuration across multiple APIs is a great way to promote consistency.
upvoted 0 times
...
Celestina
3 months ago
Option A seems like the most straightforward way to share configuration across APIs. Building a domain project is a best practice recommended by MuleSoft.
upvoted 0 times
Miles
2 months ago
I agree, building a domain project is a best practice recommended by MuleSoft.
upvoted 0 times
...
Marsha
2 months ago
Option A seems like the most straightforward way to share configuration across APIs.
upvoted 0 times
...
...
Derrick
3 months ago
I think the best practice is to build a Mule domain project and reference it from each System API.
upvoted 0 times
...

Save Cancel