Design and implement a source control strategy
Practise only this domain. 31 questions with explanations, 20 at a time.
Start this domainSample questions
- A team practicing continuous integration wants every developer to integrate into the shared line at least daily, while still releasing unfinished functionality without exposing it to customers. Which arrangement fits?Medium
- A company keeps its web frontend, API and background worker in one repository. A change to the frontend should not trigger expensive builds of the worker. Which setup addresses this?Hard
- A software house wants developers to catch leaked secrets and formatting errors before a commit ever leaves their laptop, and it wants the server to reject anything that bypasses that step. Which pairing is strongest?Hard
- A developer is midway through an edit when an urgent request arrives. The branch must be clean for the switch, but the partial edits need to stay recoverable. Which action is correct?Easy
- A feature branch has twenty small commits, several of them fixups. The team wants the target branch to receive a single clean change when the pull request completes. Which option achieves this?Medium
- A company wants to contribute a bug fix to a public open-source project hosted on another platform, while keeping its own working copy under the company's account. What is the standard workflow?Easy
- A five-person startup with little Git experience wants a branching model that is quick to learn, still requires peer review of changes, and fits a continuous deployment pipeline. Which model should it choose?Easy
- A company's monorepo has a very large history and thousands of branches, which makes clones and routine fetches slow on developer Windows machines. Which Microsoft-developed tooling improves this without splitting the repository?Hard