mediumMultiple Choice
PK0-005 Practice Question: During the execution phase of a software…
During the execution phase of a software development project, the team discovers that the database schema needs to be altered to accommodate a new regulatory requirement. The project manager is reviewing the change request. What is the MOST important factor to consider before approving the change?
⚠ Common exam trap
Many candidates assume regulatory deadlines justify immediate action (Option B) or that budget alone is sufficient (Option D), but the exam tests the formal change control process where impact analysis on the triple constraint is the most important factor before approval.
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
✓
The change's impact on the project's schedule, cost, and scope must be analyzed.
Any change to a database schema during the execution phase of a software development project carries significant risk to schedule, cost, and scope. The project manager must perform a formal impact analysis to understand how the schema alteration affects existing data integrity, application code dependencies, testing cycles, and deployment timelines before approving the change. This aligns with the integrated change control process defined in the PMBOK Guide and is critical for maintaining project baselines.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The project manager must approve the change to avoid delaying the project.
Why it's wrong here
Managerial approval alone does not establish that the schema alteration actually satisfies the regulatory requirement or that its impacts are understood. Authority to approve differs from the basis for approving. Unilateral sign-off suits urgent, low-impact changes where no formal change control board exists and analysis is trivial.
- ✗
The team should implement the change immediately to meet the regulatory deadline.
Why it's wrong here
Immediate implementation bypasses integrated change control, so the regulatory impact on scope, schedule, cost and risk goes unassessed before work begins. The deadline is a scheduling input, not an approval criterion. Fast-tracking suits low-risk changes with no cross-project dependencies, where analysis is already complete.
- ✓
The change's impact on the project's schedule, cost, and scope must be analyzed.
Why this is correct
Approving any change during execution requires assessing its effect on the triple constraint. Altering the database schema for a regulatory requirement will likely shift schedule, cost, and scope, so this analysis lets the project manager make an informed decision before committing.
- ✗
The change should be approved if it is within the current phase's budget.
Why it's wrong here
Budget compliance does not address whether the altered schema satisfies the regulatory requirement, which is the driver of the change. Cost sits within the integrated change control review, but a change meeting budget while failing compliance must still be rejected. Budget checks would be the deciding factor for a discretionary, non-mandatory enhancement.
Go deeper
Related to this question
About these practice questions
This PK0-005 question is part of Courseiva's 954-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 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.