MuleSoft Certified Integration Architect – Level 1 — Question 41

An organization is migrating all its Mule applications to Runtime Fabric (RTF). None of the Mule applications use Mule domain projects.
Currently, all the Mule applications have been manually deployed to a server group among several customer-hosted Mule runtimes. Port conflicts between these
Mule application deployments are currently managed by the DevOps team who carefully manage Mule application properties files.
When the Mule applications are migrated from the current customer-hosted server group to Runtime Fabric (RTF), do the Mule applications need to be rewritten, and what DevOps port configuration responsibilities change or stay the same?

Answer options

• A. NO, the Mule applications do NOT need to be rewritten DevOps MUST STILL manage port conflicts
• B. NO, the Mule applications do NOT need to be rewritten DevOps NO LONGER needs to manage port conflicts between the Mule applications
• C. YES, the Mule applications MUST be rewritten DevOps NO LONGER needs to manage port conflicts between the Mule applications
• D. YES, the Mule applications MUST be rewritten DevOps MUST STILL manage port conflicts

Correct answer: C

Explanation

The correct answer is C because when migrating to Runtime Fabric (RTF), the Mule applications must be rewritten to adapt to the new architecture and deployment model. Additionally, with RTF's inherent management of application properties and networking, the DevOps team will no longer need to handle port conflicts, which is explicitly stated in this option.