Version Control & Collaboration Flashcards

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

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

A monorepo hosts multiple projects in one repository, allowing atomic commits that span services and simplifying dependency management and CI/CD pipeline coordination.

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

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

Conventional Commits defines a lightweight commit message convention (e.g., feat:, fix:, chore:) that allows tools to automatically determine version bumps and generate changelogs.

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

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

Pre-commit hooks execute scripts before a commit is finalized, enabling early enforcement of code style, quality gates, and security checks without relying solely on CI.

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

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

Squash merging or rebasing condenses many small work-in-progress commits into meaningful, atomic commits, keeping the shared history clean and easier to audit.

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

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

GitOps uses Git repositories as the authoritative source for declarative infrastructure and application config, with an operator (e.g., Flux, Argo CD) continuously reconciling live state to match the repo.

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

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

git merge --squash collapses all commits from the source branch into a single working-tree change without committing it, so the author creates one clean commit summarizing the entire feature.

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

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

RBAC with least-privilege ensures each developer and service account has only the permissions required for their role, reducing the blast radius of compromised credentials or human error.