MuleSoft Certified Integration Architect – Level 1 — Question 47

An organization has various integrations implemented as Mule applications. Some of these Mule applications are deployed to customer-hosted Mule runtimes (on- premises) while others execute in the MuleSoft-hosted runtime plane (CloudHub). To perform the integration functionality, these Mule applications connect to various backend systems, with multiple applications typically needing to access the same backend systems.
How can the organization most effectively avoid creating duplicates in each Mule application of the credentials required to access the backend systems?

Answer options

• A. Create a Mule domain project that maintains the credentials as Mule domain-shared resources Deploy the Mule applications to the Mule domain, so the credentials are available to the Mule applications
• B. Configure or create a credentials service that returns the credentials for each backend system, and that is accessible from customer-hosted and MuleSoft- hosted Mule runtimes Have the Mule applications load the properties at startup by invoking that credentials service
• C. Store the credentials in properties files in a shared folder within the organization's data center Have the Mule applications load properties files from this shared location at startup
• D. Segregate the credentials for each backend system into environment-specific properties files Package these properties files in each Mule application, from where they are loaded at startup

Correct answer: B

Explanation

The correct answer, B, is effective because it centralizes credential management in a credentials service, allowing all Mule applications to access the required information without duplication. Option A, while useful, still requires creating a domain project and may not cover all runtime environments as efficiently. Options C and D involve storing credentials in files, which increases the risk of duplication and potential security issues.