200-901 · Question #489
A customer is building a new DevOps business. The customer plans to deploy a modern version control system that supports multiple branches. Then the customer will aim to integrate into a Cl/CD…
The correct answer is C. GitHub. GitHub (or Git-based version control) must come first because version control is the foundation of any CI/CD pipeline. You cannot build a CI/CD pipeline without a source repository to trigger it. GitHub natively supports multiple branches (feature branches, main, release, etc.)…
Question
A customer is building a new DevOps business. The customer plans to deploy a modern version control system that supports multiple branches. Then the customer will aim to integrate into a Cl/CD pipeline for automated provisioning and agile development. What should the customer use first for the version control system?
Options
- ACisco ACI
- BJenkins
- CGitHub
- DAnsible
How the community answered
(32 responses)- A6% (2)
- C91% (29)
- D3% (1)
Explanation
GitHub (or Git-based version control) must come first because version control is the foundation of any CI/CD pipeline. You cannot build a CI/CD pipeline without a source repository to trigger it. GitHub natively supports multiple branches (feature branches, main, release, etc.) and integrates directly with CI/CD tools. Jenkins (B) is the CI/CD automation server that would be integrated after the VCS is established. Ansible (D) is a configuration management and automation tool used later in the pipeline for provisioning. Cisco ACI (A) is a Software-Defined Networking solution for data center networking, unrelated to version control or CI/CD pipelines.
Topics
Community Discussion
No community discussion yet for this question.