MuleSoft Certified Integration Architect – Level 1 — Question 37

A new Mule application under development must implement extensive data transformation logic. Some of the data transformation functionality is already available as external transformation services that are mature and widely used across the organization; the rest is highly specific to the new Mule application.
The organization follows a rigorous testing approach, where every service and application must be extensively acceptance tested before it is allowed to go into production.
What is the best way to implement the data transformation logic for this new Mule application while minimizing the overall testing effort?

Answer options

• A. Implement transformation logic in the new Mule application using DataWeave, replicating the transformation logic of existing transformation services
• B. Implement transformation logic in the new Mule application using DataWeave, invoking existing transformation services when possible
• C. Extend the existing transformation services with new transformation logic and invoke them from the new Mule application
• D. Implement and expose all transformation logic as microservices using DataWeave, so it can be reused by any application component that needs it, including the new Mule application

Correct answer: B

Explanation

The correct answer is B because it allows the new Mule application to leverage existing transformation services, minimizing the amount of new code that needs to be tested. This approach helps to reduce the overall testing effort since the existing services have already been tested and validated. Options A and C involve more duplication or modification of existing services, leading to additional testing, while option D creates more complexity without the need for microservices in this specific scenario.