hardMultiple ChoiceObjective-mapped
Change Control Process During Execution
A company is implementing a new enterprise resource planning (ERP) system. The project is in the execution phase. The project manager receives a report that during user acceptance testing (UAT), 15 critical defects were found. The defects are related to incorrect calculation logic in the financial module. The testing team estimates that fixing these defects will require two additional weeks of work by the development team. The project sponsor is concerned about the schedule delay and asks the project manager to proceed with the go-live as planned and fix the defects after go-live. The project manager must decide the best course of action. What should the project manager do?
Quick Answer
The correct answer is to initiate a change request to formally document the defects, assess the impact on schedule, and seek approval from the change control board. This is because the change control process during execution requires that any deviation from the baseline—such as fixing critical defects that delay go-live—must be formally evaluated and approved, not decided unilaterally by the sponsor. On the CompTIA Project+ PK0-005 exam, this scenario tests your understanding that the project manager’s role is to follow the established change management framework, even when pressured by stakeholders, and that bypassing the change control board introduces unacceptable risk. A common trap is assuming the sponsor’s authority overrides the process, but the correct path is always to document, assess, and seek formal approval. Remember the memory tip: “Document, Assess, Approve”—never skip the board when scope, schedule, or quality is affected.
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
✓
Initiate a change request to formally document the defects, assess the impact on schedule, and seek approval from the change control board.
Formal change control ensures proper evaluation of the defects' impact on schedule, budget, and quality, and secures stakeholder buy-in before altering the project baseline. Option A is incorrect because bypassing the sponsor and delaying without approval undermines authority and ignores the governance process. Option C is unacceptable because workarounds for critical calculation errors introduce severe operational risk and defer the root cause. Option D is premature because deferring critical defects without a formal risk assessment and change approval violates project management best practices and could jeopardize business operations.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Delay the go-live without formal approval and instruct the team to fix the defects immediately.
Why it's wrong here
Delaying without approval violates the change control process.
- ✓
Initiate a change request to formally document the defects, assess the impact on schedule, and seek approval from the change control board.
Why this is correct
Following the change control process is the correct procedure.
- ✗
Direct the development team to implement a temporary workaround to allow go-live on time.
Why it's wrong here
Workarounds may not be reliable and should be tested.
- ✗
Proceed with go-live as scheduled and address defects post-implementation, as requested by the sponsor.
Why it's wrong here
Critical defects should not be deferred without formal change control.
Go deeper
Related to this question
About these practice questions
One of 980 original PK0-005 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 →
Same concept, more angles
1 more way this is tested on PK0-005
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A project is in execution when a critical vendor fails to deliver a key component. The project manager determines this will push the project past the deadline. After submitting a change request, what should the project manager do next?
hard- A.Fast track the remaining tasks
- ✓ B.Communicate the impact to stakeholders
- C.Request additional resources
- D.Update the risk register
Why B: After submitting a change request, the project manager should communicate the potential impact to stakeholders to manage expectations. Updating the risk register is important but not the immediate next step; fast tracking and requesting resources may be considered after approval.
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.