DevOps Version Control & Git Workflows 3

Question 1

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

Accepted Answer

A versioning scheme using MAJOR.MINOR.PATCH

Answer

A date-based versioning system using YYYY.MM.DD

Answer

A hash-based system using commit SHA values

Answer

A sequential numbering system using build numbers only

Question 2

What is the purpose of a Git 'hook'?

Accepted Answer

A script that runs automatically before or after specific Git events

Answer

A syntax for referencing remote repositories

Answer

A method for connecting Git to external issue trackers

Answer

A special branch that cannot be deleted

Question 3

When using a monorepo, what is a common challenge teams face with Git?

Accepted Answer

Slower clone and fetch times due to the large repository size

Answer

Inability to use pull requests across modules

Answer

Incompatibility with most CI/CD platforms

Answer

Requirement to use a separate Git server per team

Question 4

What does 'git bisect' help a DevOps engineer do?

Accepted Answer

Identify which commit introduced a bug using binary search

Answer

Split a large commit into smaller atomic commits

Answer

Compare two branches for differences

Answer

Merge two diverged branches with no conflicts

Question 5

Which practice ensures that configuration and infrastructure definitions are stored and versioned alongside application code?

Accepted Answer

GitOps

Answer

Blue-green deployment

Answer

Canary releasing

Answer

Feature flagging

Question 6

What is the main risk of using 'git push --force' on a shared branch?

Accepted Answer

It overwrites remote history, potentially losing teammates' committed work

Answer

It permanently deletes all tags in the repository

Answer

It resets all branch protections and CI integrations

Answer

It merges all pending pull requests automatically

Question 7

What is the recommended approach when a long-lived feature branch falls significantly behind the main branch?

Accepted Answer

Rebase the feature branch onto the latest main to incorporate updates

Answer

Delete the branch and recreate it from main

Answer

Create a new hotfix branch to bridge the gap

Answer

Merge main into the feature branch only at the time of the final release