FC0-U71 Software Development Concepts Practice Question
A team is choosing a version control workflow for a project with multiple developers. They want changes to be tracked, reviewed, and integrated safely. Which TWO practices are characteristic of using a distributed version control system such as Git? (Choose two.)
⚠ Common exam trap
The trap here is assuming any repository hosted on a server is centralized, when a distributed system can still use a shared remote while each developer keeps a full local copy.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Each developer has a full local copy of the repository, including its history
Distributed version control gives every developer a complete local repository with full history, enabling offline commits and branching, while collaborative platforms add pull requests so changes can be reviewed before merging. A single central server with mandatory connectivity describes a centralized model, file locking conflicts with parallel work, and automatic unreviewed deployment contradicts the goal of safe integration.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
File locking prevents two developers from editing the same file at the same time
Why it's wrong here
Exclusive file locking is associated with older centralized systems that serialize edits. Distributed systems generally rely on branching and merging instead of locking, letting multiple developers work on the same file and reconcile changes later. Mandatory locking would hinder the parallel workflow the team wants.
- ✓
Each developer has a full local copy of the repository, including its history
Why this is correct
In a distributed version control system, cloning a repository copies the complete history to the developer's machine. This allows commits, branching, and history inspection to happen locally without a network connection. It is a defining characteristic of distributed systems and supports the team's need to track changes independently before sharing them.
- ✗
Every commit is automatically deployed to production without any review
Why it's wrong here
Automatically deploying every commit to production bypasses the review and safe integration the team requires. It also has no relationship to the distributed nature of the version control system. This practice would increase risk rather than support controlled, reviewed integration of changes.
- ✗
The repository exists only on a single central server, and developers must be online to commit
Why it's wrong here
Requiring a central server and constant connectivity describes a centralized version control model rather than a distributed one. In a distributed system, developers commit locally and synchronize later. This option contradicts the defining property of distributed version control, so it does not fit the scenario.
- ✓
Changes are proposed for review through a pull request before being merged into the main branch
Why this is correct
A pull request lets teammates review, comment on, and approve changes before they are integrated. This supports the goal of reviewing and safely integrating work. It is a common collaborative practice built on top of a distributed version control system and helps catch defects before they reach the shared main branch.
Go deeper
Related to this question
About these practice questions
One of 988 original FC0-U71 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This FC0-U71 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the FC0-U71 exam.