hardMultiple Choice
FC0-U71 Practice Question: A software team uses version control and one…
A software team uses version control and one developer commits a change that breaks the build. Which practice should be enforced to prevent this in the future?
⚠ Common exam trap
Test-takers frequently confuse 'preventing' with 'detecting'—they choose daily builds (A) or peer review (B) because those are familiar practices, but only a pre-commit hook actively blocks the broken code from being committed in the first place.
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
✓
Set up a pre-commit hook to run unit tests
A pre-commit hook runs automated unit tests on the developer's local machine before the commit is accepted. If the tests fail, the commit is blocked, preventing broken code from entering the shared repository and breaking the build. This enforces immediate validation at the point of commit, catching issues before they affect other team members.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Schedule daily automated builds
Why it's wrong here
Daily automated builds detect a broken build only after the commit has landed, so they cannot prevent it. It tempts because CI builds catch integration errors early, and would be right for surfacing failures quickly, but the requirement is stopping the bad commit before it merges.
- ✗
Require peer review for all commits
Why it's wrong here
Peer review inspects a change before it merges, but reviewers can approve build-breaking code; it does not itself verify the build. It tempts because review is a genuine quality gate, and would be correct for catching logic or style defects, not for guaranteeing the build compiles.
- ✗
Implement a code freeze during releases
Why it's wrong here
A code freeze halts commits near release, so it cannot stop a bad commit breaking the build during normal development. It tempts because freezes stabilise release branches, which is correct when shipping a fixed version, not for continuous prevention of build-breaking commits.
- ✓
Set up a pre-commit hook to run unit tests
Why this is correct
A pre-commit hook runs the unit tests locally before the commit is recorded, blocking code that fails tests from entering the repository. This enforces verification at the earliest point, preventing the broken build reaching shared branches.
Go deeper
Related to this question
About these practice questions
This FC0-U71 question is part of Courseiva's 988-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.