PK0-005 Project Life Cycle Practice Question
A project manager learns that a regulatory change will require an additional compliance review not included in the approved scope baseline. The change is mandatory to keep the project legally compliant. What should the project manager do first?
⚠ Common exam trap
The trap here is assuming that mandatory or regulatory changes can skip change control because they are not optional.
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
✓
Submit a change request and perform impact analysis on scope, schedule, and cost.
Mandatory changes still follow formal change control: the project manager documents a change request and analyzes impacts on scope, schedule, and cost before approval. Implementing work early, rejecting a legal requirement, or only logging the item would bypass governance or delay compliance, so submitting the change request for impact analysis is the correct first step.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Log the change in the issue log and take no further action until the next status meeting.
Why it's wrong here
An issue log tracks problems and their resolution, but a change to scope belongs in a change request processed through change control. Merely logging it delays action and may cause the team to miss a compliance deadline. The project manager should initiate the formal change process rather than defer it.
- ✗
Implement the compliance review immediately and update the schedule baseline afterward.
Why it's wrong here
Implementing work before it is approved bypasses the change control process and can create unauthorized scope and cost. Even when a change is mandatory, the project manager should document it and route it through the appropriate approval path so impacts are understood. Acting first and updating baselines later undermines governance and may cause budget overruns that are hard to justify.
- ✓
Submit a change request and perform impact analysis on scope, schedule, and cost.
Why this is correct
All changes, including mandatory regulatory ones, should be documented in a change request and analyzed for impact before approval. This lets the change control board or sponsor decide how to proceed with full knowledge of effects on baselines and resources. It preserves the integrity of the plan while ensuring compliance is addressed through the proper channel.
- ✗
Reject the change because the scope baseline has already been approved by the sponsor.
Why it's wrong here
Rejecting a mandatory regulatory requirement would leave the project noncompliant and expose the organization to legal and financial penalties. Baselines can be changed through formal change control when justified. The project manager should not use the approved baseline as a reason to ignore a legal obligation that affects project viability.
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 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 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.