8. Utilize Common Version Control Operations with Git 200-901 Practice Questions (Page 5)

Questions 21–25

1. 21application · medium

   A network engineer wants to contribute to an open-source automation project hosted on GitHub. The engineer does not have write access to the original repository but wants to make changes and later submit them for review. What is the recommended first step?

   • AClone the original repository and commit locally only.
   • BFork the repository and clone the fork locally.
   • CRequest write access before cloning.
   • DClone the original repository and push directly.
   Reveal Solution Discussion Select an answer first
2. 22expert · hard

   An engineer is on branch 'main' and runs 'git pull origin main'. The pull succeeds but reports a merge conflict in 'inventory.yml'. The engineer wants to keep the local version of the file and discard the remote changes for this file only. Which sequence of commands should be used?

   • Agit checkout --theirs inventory.yml && git add inventory.yml && git commit -m 'Resolve conflict'
   • Bgit rm inventory.yml && git commit -m 'Remove file'
   • Cgit reset --hard HEAD
   • Dgit checkout --ours inventory.yml && git add inventory.yml && git commit -m 'Resolve conflict'
   Reveal Solution Discussion Select an answer first
4. 23application · medium

   A developer has staged several files and wants to review the exact changes that are staged before creating a commit. Which command shows the staged changes?

   • Agit diff --staged
   • Bgit status
   • Cgit diff
   • Dgit show HEAD
   Reveal Solution Discussion Select an answer first
5. 24application · easy

   An engineer has staged changes to a file but wants to review the exact differences between the staged version and the last commit before committing. Which command shows this?

   • Agit status
   • Bgit diff
   • Cgit diff --cached
   • Dgit diff HEAD
   Reveal Solution Discussion Select an answer first
6. 25expert · hard

   A team uses a shared main branch. A developer created a feature branch, made changes, and then ran git merge main while on the feature branch. The merge resulted in conflicts in a file. The developer wants to keep the feature branch changes for that file but also incorporate the main branch changes in other files. What is the most appropriate action?

   • ARun git checkout --ours on the conflicted file and then commit
   • BRun git merge --abort to cancel the merge
   • CRun git reset --hard HEAD to undo the merge
   • DEdit the conflicted file to combine both changes, then git add and git commit
   Reveal Solution Discussion Select an answer first