Version Control Coursera Quiz Answers

Get All Weeks Version Control Coursera Quiz Answers

The Version Control with Git course provides you with a solid, hands-on foundation for understanding the Git version control system. Git is open-source software originally created by Linus Torvalds. Git manages team files for large and small projects. This allows the team to continuously improve its product. It is used by most major technology companies and is assumed knowledge for many modern programming and IT jobs.

It is a core component of DevOps, continuous delivery pipelines, and cloud-native computing. You could also use Git to manage the many continuously improving revisions of that book that you are writing.

In this course, you will not learn everything there is to know about Git, but you will build a strong conceptual understanding of the technology, and afterward will be able to confidently dig deeper on any topic that interests you. This course assumes no previous knowledge of Git, but if you do have experience with it, you may find this course to be both useful and challenging. This is especially true if you currently “know just enough Git to be dangerous”.

Enroll on Coursera

Version Control Coursera Quiz Answers

Week 1 Quiz Answers

Quiz 1: Module 1 Assessment

Q1. Which one of these statements about Git is true?

  • Each version of the project is called a branch.
  • Git helps manage the history of the project.
  • A commit containing one small change to a project is not practical.

Q2. Which one of these statements about branches is true?

  • The default branch is named “master”.
  • A branch contains a small part of the project.
  • By default, a commit does not belong to a branch.

Q3. What is a request to merge your branch into another branch called?

  • Code review
  • Automated test
  • Pull request

Q4. If a remote repository is offline, which one of the following is true?

  • You can continue to work, but only with the current version of the project.
  • You must wait for the remote repository to become available.
  • You can continue to work with the local repository.

Q5. Which one of the following is true?

  • Git implements distributed version control.
  • Git does not scale to large projects.
  • Git is owned by a single company.

Q6. Which one of these statements about commits is true?

  • A commit is a snapshot of the project.
  • A commit contains only the changes to the project since the previous commit.
  • Only the most recent commit is saved in the repository.

Q7. Which location contains the list of files that will be included in the next commit?

  • Staging area
  • Working tree
  • Remote repository
  • Branch

Q8. Which location contains the commit history of a project?

  • Branch
  • Staging area
  • Remote repository
  • Working tree

Q9. When a file is first placed in the working tree, what is its status?

  • Modified
  • Untracked
  • Committed
  • Staged

Q10. What must you do to add a new file to the next commit?

  • Check out the file.
  • Add the file to the staging area.
  • Push the file.
  • Tag the file.

Q11. If you create a local repository in a folder with existing files, what will be the status of the files?

  • Untracked
  • Staged
  • Modified
  • Committed

Q12. Immediately after you commit, where is the commit located?

  • Neither repository
  • Remote repository
  • Local repository
  • Local repository and remote repository

Q13. Which one of these statements about remote repositories is true?

  • You must have one remote repository for each local repository.
  • A remote repository usually has a staging area.
  • By convention, remote repository names end in “.git”.
  • A remote repository usually has a working tree.

Q14. What is a local copy of a remote repository called?

  • Origin
  • Branch
  • Clone
  • Master

Q15. After you clone a repository, which one of the following is true?

  • The remote repository information is available in the local repository.
  • New commits to the local repository will automatically be pushed to the remote repository.
  • Only the most recent commit is available locally.
  • New commits on the remote repository will automatically be added to the local repository.

Q16. What is origin?

  • An alias for the remote repository’s URL.
  • The default branch name.
  • The first version of a file in the repository.
  • The first commit of the repository.

Q17. What must you do to add a local commit to the remote repository?

  • Push
  • Pull
  • Merge
  • Stage

Week 2 Quiz Answers

Quiz 1: Module 2 Assessment

Q1. In Git, what is modeled as a directed acyclic graph?

  • The working tree.
  • The commit history.
  • The staging area.

Q2. How are Git commits connected?

  • A commit object contains the SHA-1 of its child or children.
  • The staging area lists the connections.
  • A commit references its parent(s).

Q3. What is a Git ID?

  • The name of a Git object.
  • The user’s name and email address.
  • The ID of the local repository.

Q4. If a large file changes by one character, what would you expect to happen to its corresponding SHA-1 value?

  • It would change drastically.
  • It would slightly change.
  • It would not change.

Q5. What do branch labels point to?

  • The initial commit of a branch.
  • Every commit of a branch.
  • The most recent commit of a branch.

Q6. How many HEAD references are in a local repository?

  • One.
  • One for each branch label.
  • One for each commit.

Q7. Which one of these statements is correct?

  • A tag always points to a specific commit.
  • The HEAD reference always points to a tag.
  • A tag is another name for a branch label.

Q8. What happens when a branch is created?

  • The HEAD reference changes.
  • A branch label is created.
  • Commits are copied.

Q9. Which one of these statements is correct?

  • Checkout prevents others from changing a branch.
  • Checkout retrieves content from the remote repository.
  • Checkout updates the working tree and HEAD reference.

Q10. What does a detached HEAD mean?

  • The HEAD reference points directly to a commit SHA-1.
  • The HEAD reference points to a branch label.
  • The HEAD reference does not point to anything.

Q11. What does “deleting a branch” immediately do?

  • Deletes all of the commits of the branch.
  • Deletes a branch label.
  • Deletes only the commits that are unique to the branch.

Q12. Which one of the following statements is true?

  • A merge always creates a new commit.
  • A commit can only belong to one branch at a time.
  • Merging combines the work of branches.

Q13. Which one of the following statements about fast-forward merges is true?

  • The merge moves a branch label.
  • The merge may change some commits.
  • The merge may result in a merge conflict.

Q14. If Git informs you that a fast-forward merge is not possible, which one of these statements is most likely to be true?

  • A commit was made on the base branch after the topic branch was created.
  • The checked out commit has multiple parents.
  • The merge has merge conflicts that must be resolved first.

Q15. Which one of these statements about a merge involving a merge commit is true?

  • A merge commit results in a linear commit history.
  • The merge is aborted if there are merge conflicts.
  • Git places the result of the merge into a new commit.

Week 3 Quiz Answers

Quiz 1: Module 3 Assessment

Q1. Which one of the following statements about merge conflicts is true?

  • Merge conflicts can not occur in Git.
  • Merge conflicts can be fast-forward merged.
  • Merge conflicts occur when a person needs to make a decision.

Q2. Assume that you have a topic branch merging into a base branch. Which one of the following is involved in resolving a merge conflict?

  • Checking out the topic branch.
  • Adding file(s) to the staging area.
  • Pushing to the remote repository.

Q3. Assume that you have a topic branch merging into a base branch. Which one of these situations is most likely to create a merge conflict?

  • In README.md, the topic branch modifies the header and the base branch modifies the footer.
  • Both branches update the header in README.md.
  • The topic branch modifies fileA.txt. The base branch modifies README.md.

Q4. Which one of the following statements is true?

  • A tracking branch label sometimes points to the same SHA-1 as the remote branch label.
  • A tracking branch label always points to the same SHA-1 as the remote branch label.
  • A tracking branch label never points to the same SHA-1 as the remote branch label.

Q5. Which one of the following is most likely to have tracking branches?

  • A remote repository.
  • The staging area.
  • A local repository.

Q6. Immediately after you clone a repository, which one of these statements is most likely to be true?

  • The tracking branch label and local branch label point to the same commit.
  • There are no tracking branches.
  • The local branch tip will be ahead of the tracking branch tip.

Q7. If you perform a fetch and new objects are retrieved, which one of these is most likely to be true?

  • The local branch and tracking branch will contain the exact same commits.
  • The tracking branch label will point to a new commit.
  • The local branch label and tracking branch label will point to the same commit.

Q8. Which one of these statements is true?

  • Pull does not update the local branch tip.
  • Fetch does not update the local branch tip.
  • Fetch may result in a merge conflict.

Q9. Which one of these statements is true?

  • Pull combines fetch and push.
  • Pull combines fetch and merge.
  • Push combines fetch and merge.

Q10. A pull may result in which one of the following?

  • A merge commit on the remote repository.
  • A fast-forward merge.
  • A new checked out branch.

Q11. When should you avoid rebasing a branch?

  • If you have shared the branch.
  • If a merge conflict occurs.
  • Always.

Q12. Which one of the following statements is true?

  • A rebase never results in a merge conflict.
  • A rebase may result in a merge conflict.
  • A rebase always results in a merge conflict.

Q13. Which one of the following statements is true?

  • A rebase may rewrite the commit history.
  • A rebase always rewrites the commit history.
  • A rebase never rewrites the commit history.

Q14. Which one of the following statements is true?

  • Rebasing a topic branch involves checking out the base branch.
  • A rebase always creates a merge commit.
  • A rebase may result in a merge conflict.

Q15. Which one of the following statements is true?

  • An interactive rebase may involve a single branch.
  • An interactive rebase must involve two or more branches.
  • An interactive rebase never removes existing commits.

Week 4 Quiz Answers

Quiz 1: Module 4 Assessment

Q1. Which one of these is the main goal of a pull request?

  • Obtain a clone of a repository.
  • Create a branch.
  • Merge a branch into a project.

Q2. Which one of these statements is true?

  • A pull request can be made only when a branch is being merged.
  • A pull request can act as a form of review and approval.
  • A pull request must be made from a forked repository.

Q3. Which one of these statements is true?

  • A pull request merge can not be fast-forwarded.
  • Merging a pull request may result in a merge conflict.
  • Merging a pull request always creates a merge commit.

Q4. Which one of these statements is true?

  • A pull request must include a forked repository.
  • Pull requests can not be modified.
  • Pull requests can facilitate team discussion.

Q5. When can you open a pull request?

  • When you want feedback on your work.
  • Only when the branch is ready to be merged.
  • Only when the branch is created.

Q6. Which one of these is true about squash merges?

  • A squash merge creates a merge commit.
  • A squash merge can result in deleted commits.
  • A squash merge can not be done when merging a pull request.

Q7. Which one of these statements is true?

  • A fork is a remote repository.
  • A fork is an upstream repository.
  • A fork is considered the source of truth.

Q8. Which one of statements about forks is true?

  • The upstream repository may have access to the fork.
  • The upstream respository never has access to the fork.
  • The upstream repository always has access to the fork.

Q9. After forking a repository, which one of these statements is true?

  • The commit histories of the two repositories may begin to differ.
  • The two repositories will automatically remain synchronized.
  • The two repositories can not be synchronized.

Q10. Which one of these statements is true?

  • Cloning a forked repository creates a local repository.
  • There is no reason to clone a forked repository.
  • A fork and a clone are the same thing.

Q11. Assume that you have a forked repository and an upstream repository. Who selects the merge strategy if a pull request is merged?

  • The person merging the pull request.
  • The requester.
  • The creator of the topic branch.

Q12. Which one of these statements about centralized workflows is true?

  • Using a centralized workflow is discouraged.
  • There is usually a single branch on the remote repository.
  • Pull requests are common in centralized workflows.

Q13. Which one of these statements about feature branch workflows is true?

  • Pull requests are not possible in feature branch workflows.
  • Most work is done on a feature branch.
  • Using a feature branch workflow is discouraged.

Q14. Which one of these statements about forking workflows is true?

  • A forking workflow involves multiple remote repositories.
  • The forked repository must have write access to the upstream repository.
  • Using a forking workflow is discouraged.

Q15. Which one of these statements about Gitflow workflows is true?

  • Gitflow workflows can accomodate hotfixes.
  • Gitflow workflows contain no long-running branches.
  • Gitflow workflows work best with small projects.

Version Control Course Review

In our experience, we suggest you enroll in Version Control courses and gain some new skills from Professionals completely free and we assure you will be worth it.

Version Control for free, if you are stuck anywhere between a quiz or a graded assessment quiz, just visit Networking Funda to get Version Control Coursera Quiz Answers.

Conclusion:

I hope this Version Control Coursera Quiz Answer would be useful for you to learn something new from this Course. If it helped you then don’t forget to bookmark our site for more Quiz Answers.

This course is intended for audiences of all experiences who are interested in learning about new skills in a business context; there are no prerequisite courses.

Keep Learning!

Get All Course Quiz Answers of Meta Front-End Developer Professional Certificate

Introduction to Front-End Development Quiz Answers

Programming with JavaScript Coursera Quiz Answers

Version Control Coursera Quiz Answers

HTML and CSS in depth Coursera Quiz Answers

React Basics Coursera Quiz Answers

Advanced React Coursera Quiz Answers

Principles of UI/UX Design Coursera Quiz Answers

Leave a Reply

Your email address will not be published.

error: Content is protected !!