7. Explain the Advantages of Version Control 200-901 Practice Questions (Page 1)

Questions 1–5

1. 1expert · hard

   A network team is using Git for their automation scripts. They have a main branch that is protected, and all changes must go through a pull request. An engineer has created a feature branch, made several commits, and is ready to merge. The team wants to keep the main branch history clean and easy to review. Which merge strategy should they use?

   • AMerge with a merge commit to preserve all individual commits.
   • BCherry-pick each commit individually to main.
   • CSquash and merge to combine all feature commits into one commit on main.
   • DRebase and merge to replay commits without a merge commit.
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   Which practice is considered a best practice when using version control?

   • ACommitting often with clear, descriptive messages that describe the change
   • BAvoiding branches to keep the history linear
   • CWriting vague commit messages to avoid revealing details
   • DCommitting large batches of unrelated changes together to save time
   Reveal Solution Discussion Select an answer first
4. 3application · easy

   A network team is evaluating version control systems. They need a system where developers can work independently and have a full local copy of the project history, even if the central server is unavailable. Which type of version control system meets this requirement?

   • AFile-based version control like copying files to a shared drive.
   • BDatabase-based version control that stores only the latest version.
   • CDistributed version control system (DVCS) like Git.
   • DCentralized version control system (CVCS) like Subversion.
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   A network automation team uses Git for their Ansible playbooks. Two engineers are simultaneously modifying the same playbook file on separate branches. After both branches are merged, a conflict is reported. What is the most appropriate way to resolve this conflict?

   • ADelete the file from the repository and re-commit it from the latest branch.
   • BEdit the file to manually combine the changes, then commit the resolved file with a clear message.
   • CForce-push the current branch to overwrite the remote repository.
   • DRevert the merge and ask one engineer to redo their changes on top of the other's branch.
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A network automation team maintains a shared repository of Ansible playbooks. Two engineers are simultaneously updating the same playbook: one is adding a new VLAN configuration task, and the other is refactoring variable names. They both commit to the same feature branch. After the second engineer pushes, the remote repository reports a merge conflict. What should the engineers do to resolve this situation with minimal disruption?

   • AHave the second engineer pull the latest changes, resolve the conflict locally, then commit and push the merged result.
   • BRevert the second engineer's commit locally and then re-apply the changes after the first engineer's commit is pushed.
   • CDelete the remote branch and recreate it from the second engineer's local branch to avoid the conflict.
   • DForce-push the second engineer's branch to overwrite the remote history and discard the first engineer's changes.
   Reveal Solution Discussion Select an answer first