The correct answer is D. Automation Decision Services is designed around Git-based collaboration for decision automations and decision services. Each decision automation can be connected to a remote Git repository, allowing team members to work collaboratively, isolate changes in branches, and share decision-service artifacts through a governed repository model. This supports modern change management because decision services are versioned, branched, reviewed, shared, and synchronized through Git rather than through legacy source-control technologies. CVS and Subversion are not the repository integration model used by ADS in Cloud Pak for Business Automation. A local Git repository alone is also insufficient because the integration requirement is collaboration with a remote repository configured through the platform's Git provider mechanism. In architecture terms, the Git provider becomes the persistence and collaboration backbone for decision automation assets, while Decision Designer provides the authoring experience. The repository connection also supports team development, publication, backup, and controlled promotion of decision-service changes. References/topics: Automation Decision Services, Decision automations, Git provider configuration, Remote Git repository, Branching and sharing decision services.