200-901 Infrastructure and Automation Practice Question
A DevOps team wants to version control their network configurations. Which tool should they use?
⚠ Common exam trap
Cisco often tests the distinction between version control tools (Git) and configuration management tools (Puppet, Ansible) or CI/CD tools (Jenkins), leading candidates to confuse the purpose of each tool in the DevOps pipeline.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Git
Git is a distributed version control system that tracks changes in source code and configuration files, making it the ideal tool for version controlling network configurations. Unlike configuration management tools, Git provides commit history, branching, and rollback capabilities specifically designed for version control.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Puppet
Why it's wrong here
Puppet enforces desired state on nodes through manifests and modules, but it does not store revision history or provide branching and merging of configuration files. It is tempting because Puppet code is normally kept in version control, yet Puppet itself is correct for configuration enforcement, not for tracking changes over time.
- ✗
Jenkins
Why it's wrong here
Jenkins orchestrates build, test and deployment pipelines; it holds no repository or commit history for configuration files. It is tempting because pipelines often check configurations out of Git during execution, but Jenkins is correct for continuous integration and delivery automation, not for storing and versioning the configurations themselves.
- ✓
Git
Why this is correct
Git provides distributed version control with commit history, branching and merging, satisfying the team's need to track changes to network configuration files over time. Unlike CI/CD orchestrators or configuration management tools, Git directly addresses versioning itself, letting engineers diff revisions and roll back faulty changes precisely.
- ✗
Docker
Why it's wrong here
Docker builds and runs container images; it has no repository, commit history or branching model for tracking configuration file revisions. It is tempting because Dockerfiles and Compose files are themselves stored in version control, but Docker is correct for packaging and running applications, not for managing configuration history.
Go deeper
Related to this question
About these practice questions
Courseiva writes every 200-901 question from scratch — 975 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 200-901 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-901 exam.