DevOps Version Control & Git Workflows

Question 1

Which Git branching strategy uses long-lived branches named 'main', 'develop', 'release', and 'hotfix'?

Accepted Answer

Gitflow

Answer

GitHub Flow

Answer

Trunk-Based Development

Answer

GitLab Flow

Question 2

What does the command 'git rebase -i HEAD~3' accomplish?

Accepted Answer

Interactively edits the last 3 commits

Answer

Merges the last 3 commits into the main branch

Answer

Resets the repository to 3 commits ago

Answer

Creates a new branch from 3 commits back

Question 3

In Trunk-Based Development, how often should developers integrate their changes into the main branch?

Accepted Answer

At least once per day

Answer

Once per sprint

Answer

After every feature is complete

Answer

Once per release cycle

Question 4

What is a 'fast-forward merge' in Git?

Accepted Answer

A merge where the branch pointer simply moves forward without creating a merge commit

Answer

A merge that skips conflict resolution automatically

Answer

A merge that compresses all commits into one

Answer

A merge that only includes changed files

Question 5

Which Git command is used to temporarily save uncommitted changes without committing them?

Accepted Answer

git stash

Answer

git cache

Answer

git hold

Answer

git save

Question 6

What is the purpose of a '.gitignore' file in a DevOps project?

Accepted Answer

To specify files and directories Git should not track

Answer

To list files that should be deleted during deployment

Answer

To define merge conflict resolution rules

Answer

To configure Git hooks for CI/CD pipelines

Question 7

What is a Git 'tag' primarily used for in a DevOps release workflow?

Accepted Answer

To mark specific commits as release points with a version label

Answer

To assign work items to specific commits

Answer

To protect branches from direct pushes

Answer

To trigger automated CI/CD pipelines