version control coursera week 1 quiz answers

Knowledge Check: Introduction to version control

1. Which of the following are the benefits of using Version Control?

Select all that apply.

  • Identity
  • Revert / Rollback
  • Collaboration

2. When multiple developers work on the same file, a merge conflict will never occur.

  • True
  • False

3. Revision History is a record of all changes within a project. It allows you to pinpoint who made the changes, when they were made and what was changed.

  • True
  • False

4. Which of the following are centralised Version Control Systems? Select all that apply.

  • Concurrent Versions System
  • Mercurial
  • Subversion
  • Git

5. Which of the following complements Version Control during software development? Select all that apply.

  • Continuous Integration
  • Continuous Delivery
  • Continuous Deployment

Module Quiz: Software collaboration

6. What is Revision History in Version Control?

  • A record of all changes in a project
  • A record of all users in a project
  • A record of all bugs in a project

7. When using a Distributed Version Control System, a connection to a central server is always required to perform an action.

  • True
  • False

8. A Version Control system allows you to roll back your files back to a specific point in time.

  • True
  • False

9. When using a Centralised Version Control system, for other developers to see your changes you must commit them to a central server.

  • True
  • False

10. Version Control is inefficient when multiple developers work on one project.

  • True
  • False

11. __________________ automatically packages an application and prepares it for deployment.

  • Continuous Deployment
  • Continuous Integration
  • Continuous Delivery

12. Which of the following are distributed Version Control Systems? Select all that apply.

  • Subversion
  • Git
  • Mercurial
  • Concurrent Versions System

13. What are the main benefits of having a staging environment?

  • It provides a safe place to test and verify changes prior to being deployed to a live production environment.
  • A staging environment mimics the production environment which allows for more accurate testing to find any possible issues.
  • It can allow teams to demo or showcase new features in a controlled environment.
  • It allows developers to add new features directly to production.

Leave a Reply