Examice

Exam MCIA - Level 1 All QuestionsBrowse all questions from this exam

Question 51

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?

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

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

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

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

To avoid creating duplicates of the credentials required to access backend systems across various Mule applications, the most effective approach is to configure or create a credentials service that returns the credentials for each backend system. This service should be accessible from both customer-hosted and MuleSoft-hosted Mule runtimes. By having the Mule applications load the properties at startup by invoking this credentials service, the organization can centrally manage and securely distribute credentials without duplicating them in each Mule application.

Discussion

AlandtOption: B

ChatGPT: The most effective approach to avoid creating duplicates of the credentials required to access the backend systems across various Mule applications is: 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.

gilofernandesOption: D

A - Mule domains project is only possible on customer-hosted Mule runtimes B - Not a OOB feature C - shared folders are not accessible in CloudHub mule applications D is the correct answer

madgeezerOption: B

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

Outdoor25Option: B

B is correct.

Outdoor25

On second thought, it should be A. I dont think loading property via call to service is possible in Mulesoft.

madgeezer

Mule Domain is only supported on premise and not on CloudHub

lzrvs

It is possible, but not OOTB. Requires creating a Custom Property Provider that adheres the API defined here: https://docs.mulesoft.com/mule-runtime/4.4/custom-configuration-properties-provider