MENU
What is the MuleSoft-recommended best practice to share the connector and configuration information among the APIs?
Suggested Answer: A
Get Premium Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
37 comments · newest first
ER
Erasmo
11 months ago
Surprised that A is the recommended practice!
EL
Eliz
11 months ago
D seems like overkill for just sharing a config.
AG
Agustin
11 months ago
Wait, why would we refactor everything for C? Sounds unnecessary.
RA
Raina
11 months ago
I think B could work too, but seems more complex.
PA
Page
12 months ago
A is definitely the way to go!
BI
Billi
12 months ago
I’m leaning towards the domain project option, but I vaguely remember something about refactoring APIs to connect through another System API.
IE
Iesha
12 months ago
I feel like creating an API proxy could be a good option, but I can't recall if it’s the recommended approach for sharing configurations.
JE
Jean
1 year ago
I remember practicing a question about using a shared file store for configurations, but it feels like that might complicate things too much.
CH
Chauncey
1 year ago
I think the best practice is to build a Mule domain project and reference it from each System API, but I'm not entirely sure if that's the only way.
MA
Marti
1 year ago
I'm a little confused by the different options here. I'll need to think through the pros and cons of each approach to determine the best recommendation. Maybe I'll jot down some notes to help me work through this step-by-step.
GO
Goldie
1 year ago
Option A sounds like the way to go. Building a shared domain project and referencing it from each API seems like a clean and efficient solution. I feel pretty confident about this one.
JE
Jesse
1 year ago
Hmm, I'm a bit unsure about this one. The question mentions "MuleSoft-recommended best practice", so I'll need to double-check the documentation to make sure I understand the proper approach. I don't want to risk getting this wrong on the exam.
PE
Pedro
1 year ago
I think the best approach here is to use a Mule domain project to share the connector and configuration information. That way, I can reference the same domain project from each of my System APIs, which should make it easier to manage and update the configuration.
MO
Mona
1 year ago
The recruitment of additional employees seems like a straightforward solution, but I'm not sure if that's the most suitable measure in this case. I'll need to consider the other options as well.
DE
Denna
1 year ago
Hmm, I'm a bit confused on this one. I think it might be a Look-up Relationship, but I'm not 100% sure.
LE
Leila
1 year ago
I remember we talked about different power bases, and coercive power seems more about punishment than authority.
LO
Lonny
2 years ago
Haha, I wonder if the exam question is trying to trip us up with all these options. Looks like I'll have to really think through the pros and cons of each approach.
MA
Matt
2 years ago
Using an API proxy with a shared configuration sounds like a great way to manage the connector details. This would give me a lot of flexibility in terms of updating the configuration without impacting the APIs.
RA
Rashad
2 years 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
SU
Suzan
2 years 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
SA
Samira
2 years ago
Creating a central System API to access the database is an interesting approach, but it adds an extra layer of complexity. I'm not sure if this is the best solution for my use case.
ST
Stephaine
2 years ago
Creating a central System API to access the database is an interesting approach, but it adds an extra layer of complexity. I'm not sure if this is the best solution for my use case.
EN
Enola
2 years 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
LA
Lanie
2 years 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
LE
Leonard
2 years ago
I agree with Edwin, it helps in centralizing the connector and configuration information.
YA
Yan
2 years ago
I like the idea of using a shared file store to load the configuration dynamically. This way, I can easily update the configuration without having to rebuild each API.
TE
Teddy
2 years 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
MI
Micaela
2 years ago
B) That sounds like a good approach. It would definitely make updating configurations easier.
JO
Jose
2 years 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
TW
Twana
2 years ago
Option A seems like a good idea, as it allows me to reuse the same connector configuration across multiple APIs. This way, I don't have to manage multiple configurations, which could be error-prone.
VI
Vicente
2 years ago
Definitely, it simplifies the management of configurations for multiple APIs.
JE
Jesusita
2 years ago
I agree, using a Mule domain project for the connector and configuration is efficient.
KR
Kristian
2 years ago
Option A seems like a good idea, as it allows me to reuse the same connector configuration across multiple APIs. This way, I don't have to manage multiple configurations, which could be error-prone.
JA
Jacob
2 years ago
Definitely, it helps in maintaining consistency and reduces the chances of errors.
MA
Mariko
2 years 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
GR
Gregoria
2 years ago
I agree, using a Mule domain project for the connector and configuration is efficient.
ED
Edwin
2 years ago
I think the best practice is to build a Mule domain project and reference it from each System API.