Source Control CV0-004 Practice Questions (Page 1)

Questions 1–5

1. 1expert · hard

   A company is migrating from a centralized version control system to Git. They have a large codebase and many developers. They want to minimize the impact on the developers' workflow while ensuring that the migration is successful. What is the most important consideration?

   • APlan the migration carefully, including converting the existing repository history and training developers on Git workflows.
   • BEnsure that all developers have Git installed and are familiar with the basic Git commands.
   • CMigrate all branches and tags to the new Git repository.
   • DChoose a Git hosting service that supports the same access control features as the old system.
   Reveal Solution Discussion Select an answer first
2. 2expert · hard

   A team uses a Git repository with a main branch. They have a feature branch that has been open for a long time and has many commits. They want to integrate the feature into main, but they are concerned about the large number of commits cluttering the main branch history. What is the most appropriate approach?

   • AUse a squash merge to combine all the feature branch commits into a single commit on main.
   • BDelete the feature branch and recreate it from main, then reapply the changes.
   • CUse a regular merge to preserve the feature branch history.
   • DRebase the feature branch onto main and then merge it.
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   What is the first step a developer should take to resolve a merge conflict?

   • AEdit the conflicting file to choose the correct changes, then commit the resolution
   • BDelete the conflicting file and recreate it from scratch
   • CRun `git reset --hard` to discard all changes and start over
   • DRun `git merge --abort` to cancel the merge and lose all changes
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   What is the primary goal of a collaboration workflow in source control?

   • ATo prevent any developer from making changes to the code
   • BTo automatically fix all merge conflicts without human intervention
   • CTo store the code in a single file for simplicity
   • DTo ensure that multiple developers can work on the same codebase without interfering with each other
   Reveal Solution Discussion Select an answer first
6. 5expert · hard

   Two developers are working on the same file in different branches. Developer A modifies a function and commits. Developer B also modifies the same function in a different way and commits. When Developer B tries to merge their branch into the main branch, a conflict occurs. What is the most appropriate way for Developer B to resolve this conflict?

   • AUse 'git checkout --theirs' to keep Developer B's version and discard the main branch changes.
   • BAbort the merge and ask Developer A to revert their changes.
   • CManually edit the file to combine the changes from both developers, then commit the merge.
   • DUse 'git checkout --ours' to keep the main branch version and discard Developer B's changes.
   Reveal Solution Discussion Select an answer first