What is the best way to use an organization’s source-code management (SCM) system in this context?

Anypoint Exchange is required to maintain the source code of some of the assets committed to it, such as Connectors, Templates, and API specifications.

What is the best way to use an organization’s source-code management (SCM) system in this context?
A . Organizations should continue to use an SCM system of their choice, in addition to keeping source
code for these asset types in Anypoint Exchange, thereby enabling parallel development, branching, and merging
B . Organizations need to use Anypoint Exchange as the main SCM system to centralize versioning and avoid code duplication
C . Organizations can continue to use an SCM system of their choice for branching and merging, as long as they follow the branching and merging strategy enforced by Anypoint Exchange
D . Organizations need to point Anypoint Exchange to their SCM system so Anypoint Exchange can pull source code when requested by developers and provide it to Anypoint Studio

View Answer

Answer: B

Explanation:

* Organization should continue to use SCM system of their choice, in addition to keeping source code for these asset types in Anypoint Exchange, thereby enabling parallel development, branching.

* Reason is that Anypoint exchange is not full fledged version repositories like GitHub.

* But at same time it is tightly coupled with Mule assets