CDM Version Control & Collaboration 2

Question 1

In a Git workflow, what is the role of a 'code owner' file (e.g., CODEOWNERS)?

Accepted Answer

It automatically assigns reviewers based on file paths when a pull request is opened

Answer

It lists developers with admin privileges to the repository

Answer

It defines which files are excluded from version control

Answer

It specifies the license owner for the codebase

Question 2

What is semantic versioning (SemVer) and which format does it follow?

Accepted Answer

A three-part versioning scheme; format MAJOR.MINOR.PATCH

Answer

A tagging system using dates; format YYYY-MM-DD

Answer

A two-part versioning scheme; format MAJOR.MINOR

Answer

A hash-based versioning system; format SHA-HASH

Question 3

Which Git feature allows developers to save uncommitted changes temporarily without creating a commit?

Accepted Answer

git stash

Answer

git archive

Answer

git tag

Answer

git bisect

Question 4

What is a 'fork' in the context of Git collaboration platforms like GitHub?

Accepted Answer

A copy of a repository in your own account, used to propose changes via pull requests

Answer

A branch created from a tag

Answer

A rollback of the repository to a previous state

Answer

A mirror of the repository on a different hosting platform

Question 5

What does 'git bisect' help a developer accomplish?

Accepted Answer

Identify the specific commit that introduced a bug using binary search

Answer

Split a branch into two parallel branches

Answer

Merge two branches into a common ancestor

Answer

Compare two different repository remotes

Question 6

In DevOps, what is the key advantage of using short-lived feature branches over long-lived feature branches?

Accepted Answer

Short-lived branches reduce merge conflicts and integrate feedback more frequently

Answer

Short-lived branches require more documentation

Answer

Short-lived branches enforce stricter code review policies

Answer

Short-lived branches eliminate the need for CI pipelines

Question 7

What is the purpose of a Git tag, and how does it differ from a branch?

Accepted Answer

A tag marks a specific point in history as immutable; a branch is a movable pointer to commits

Answer

A tag is a temporary reference; a branch is permanent

Answer

A tag creates a new line of development; a branch does not

Answer

Tags and branches are functionally identical in Git