MULESOFT-INTEGRATION-ARCHITECT-I practice question 4 of 10

An organization has various integrations implemented as Mule applications. Some of these Mule applications are deployed to custom hosted Mule…

Full set: 273 questions
An organization has various integrations implemented as Mule applications. Some of these Mule applications are deployed to custom hosted Mule runtimes (on-premises) while others execute in the MuleSoft-hosted runtime plane (CloudHub). To perform the Integra functionality, these Mule applications connect to various backend systems, with multiple applications typically needing to access the 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: 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
C: 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
D: 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 toad the properties at startup by invoking that credentials service Correct answer
Correct Answer:
D. 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 toad the properties at startup by invoking that credentials service
Explanation

The organization requires a solution that centralizes credentials for Mule applications deployed in both customer-hosted (on-premises) and MuleSoft-hosted (CloudHub) environments. A Mule domain project (A) is not supported in CloudHub. Storing files on a shared folder (B) is not accessible from CloudHub workers. Packaging properties files (C) is the duplication problem to be avoided. A centralized credentials service, accessible via an API, is the only option that provides a single source of truth for credentials that can be securely accessed from any deployment environment, effectively avoiding duplication and improving security posture.

Why Incorrect

A: Mule domain projects are not supported in CloudHub, making this solution unsuitable for the hybrid deployment model described. B: CloudHub applications cannot access an organization's internal shared network folders, so this method would only work for on-premises deployments. C: This approach represents the exact problem of credential duplication and management overhead that the organization wants to avoid.

References

1. MuleSoft Documentation, "Securing Application Properties". This document discusses various methods for securing properties, including using a secure properties file and integrating with third-party secrets management tools like HashiCorp Vault, which aligns with the concept of a credentials service. (Reference: MuleSoft Docs -> Runtime Manager -> Secure Application Properties)

2. MuleSoft Documentation, "Mule Domain Projects". This page states, "You can’t deploy Mule domain projects to CloudHub." This confirms why option A is incorrect. (Reference: MuleSoft Docs -> Anypoint Studio -> Mule Domain Projects)

Scroll to Top