CDM Version Control & Collaboration 3

Question 1

What is a 'monorepo' and what is a primary DevOps benefit of using one?

Accepted Answer

A single repository containing multiple projects or services; enables atomic cross-service commits and unified CI

Answer

A single repository containing only one microservice; simplifies deployment

Answer

A repository that only allows one contributor at a time; prevents conflicts

Answer

A repository mirrored across multiple cloud providers; improves availability

Question 2

Which of the following best describes the 'Conventional Commits' specification?

Accepted Answer

A standardized commit message format that enables automated changelog generation and semantic versioning

Answer

A tool that automatically resolves merge conflicts

Answer

A branching strategy for large enterprise teams

Answer

A code review checklist enforced by Git hooks

Question 3

What problem does a Git pre-commit hook solve in a DevOps workflow?

Accepted Answer

It runs automated checks (linting, formatting, secret scanning) before a commit is recorded locally

Answer

It prevents unauthorized users from cloning the repository

Answer

It automatically pushes code to the remote after every commit

Answer

It creates a backup branch before every commit

Question 4

In a distributed team using Git, what is the recommended strategy to maintain a clean and understandable project history?

Accepted Answer

Use squash merging or rebase to consolidate noisy feature branch commits before merging

Answer

Commit all work-in-progress directly to main

Answer

Force-push frequently to update remote branches with local history rewrites

Answer

Avoid using commit messages to save time

Question 5

What is 'GitOps' and which component is central to its implementation?

Accepted Answer

A practice where Git is the single source of truth for infrastructure and application state; central component is a reconciliation agent/operator

Answer

A GUI tool for visualizing Git history; central component is a web dashboard

Answer

A branching strategy optimized for open-source projects; central component is the fork

Answer

A Git hosting platform feature for automated deployments; central component is a webhook

Question 6

When using 'git merge --squash', what happens to the commits from the source branch?

Accepted Answer

All commits are combined into a single staged change, requiring a new commit on the target branch

Answer

All commits are merged individually, preserving their messages

Answer

The source branch is deleted automatically after the merge

Answer

Commits are rebased onto the target branch in chronological order

Question 7

Which access control model is typically recommended for managing permissions in a large DevOps organization's Git repositories?

Accepted Answer

Role-Based Access Control (RBAC) with least-privilege principles applied per repository or project

Answer

Give every developer admin access to all repositories to maximize velocity

Answer

Share a single service account credential among all CI/CD pipelines

Answer

Restrict all access to a single repository owner with manual file distribution