What type of Anypoint Exchange artifact(s) should be added to Anypoint Exchange to publish the project skeleton?

A team would like to create a project skeleton that developers can use as a starting point when creating API Implementations with Anypoint Studio. This skeleton should help drive consistent use of best practices within the team.

What type of Anypoint Exchange artifact(s) should be added to Anypoint Exchange to publish the project skeleton?
A . A custom asset with the default API implementation
B . A RAML archetype and reusable trait definitions to be reused across API implementations
C . An example of an API implementation following best practices
D . a Mule application template with the key components and minimal integration logic

Answer: D

Explanation:

* Sharing Mule applications as templates is a great way to share your work with other people who are in your organization in Anypoint Platform. When they need to build a similar application they can create the mule application using the template project from Anypoint studio.

* Anypoint Templates are designed to make it easier and faster to go from a blank canvas to a production application. They’re bit for bit Mule applications requiring only Anypoint Studio to build and design, and are deployable both on-premises and in the cloud.

* Anypoint Templates are based on five common data Integration patterns and can be customized and extended to fit your integration needs. So even if your use case involves different endpoints or connectors than those included in the template, they still offer a great starting point.

Some of the best practices while creating the template project: – Define the common error handler as part of template project, either using pom dependency or mule config file – Define common logger/audit framework as part of the template project – Define the env specific properties and secure properties file as per the requirement – Define global.xml for global configuration – Define the config file for connector configuration like Http,Salesforce,File,FTP etc – Create separate folders to create DWL,Properties,SSL certificates etc – Add the dependency and configure the pom.xml as per the business need – Configure the mule-artifact.json as per the business need