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

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.

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.

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)