easyMultiple Choice
PK0-005 Practice Question: A project team is working on a software…
A project team is working on a software development project. The project manager wants to ensure that all changes to the codebase are reviewed and approved before they are integrated. Which type of tool should be used?
⚠ Common exam trap
Many exam-takers confuse a collaboration tool (Option C) with the code review process, but collaboration tools lack the version control and merge-gating capabilities that a VCS provides for enforcing approval before integration.
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
✓
Version control system
A version control system (VCS) like Git enforces code review workflows through pull requests or merge requests, ensuring that changes are reviewed and approved before integration into the main branch. This directly supports the project manager's requirement for a controlled integration process, as VCS tracks every change and requires explicit approval via branch protection rules or merge checks.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Issue tracking system
Why it's wrong here
Issue tracking systems log defects, tasks and their status, but they hold no code and cannot gate merges on recorded approval. It is tempting because issues often reference pull requests, yet the requirement is a version control system enforcing review and approval before integration into the mainline.
- ✗
Time tracking tool
Why it's wrong here
Time tracking records hours spent on tasks; it neither stores code changes nor enforces review and approval gates before integration. It is tempting because time tracking supports project scheduling and effort reporting, but the requirement is version control with mandatory peer review and merge approval.
- ✗
Collaboration tool
Why it's wrong here
Collaboration tools host discussion, chat and shared documents, but they do not version code, branch changes or block merges until approval is recorded. It is tempting because review comments often happen in collaboration platforms, yet enforcement of review-before-integration requires a version control system with protected branches.
- ✓
Version control system
Why this is correct
A version control system such as Git enforces review before integration through pull requests and branch protection, requiring approval before merges to the main branch. It records every change and who approved it, directly satisfying the stem's requirement that code changes be reviewed and approved prior to integration.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PK0-005 question from scratch — 954 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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 PK0-005 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 PK0-005 exam.