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?
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. Anypoint Exchange complements existing SCM systems rather than replacing them, allowing for efficient source code management alongside development workflows.
i think answer should be D
it should be D
D. 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
Should be D. Cannot be B because question is what is the best way of using organizations SCM.
D is the right one.
it should be C
D. 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
it should be D
Anypoint exchange is not meant to replace full-fledged SCM like GitHub, GitLab as it doesn't support all file format, lack features and you can use it with tools like tortoise. So its better to have SCM system and Anypoint exchange together. D is the right answer according to me.