Courseiva
Question 849 of 980
hardMultiple ChoiceObjective-mapped

Change Control Process: First Step

A project has been delayed due to unexpected regulatory changes. The project manager has analyzed the impact and determines that the project will miss the original deadline by two months. The sponsor is concerned about the delay. What is the first step the PM should take?

Quick Answer

The answer is to submit a change request to the change control board with the revised schedule and impact analysis. This is correct because the change control process first step, as defined in the PMBOK Guide and tested on the CompTIA Project+ PK0-005 exam, is always to formally document and submit the proposed change for review, even when the delay is caused by an external factor like regulatory shifts. The project manager must not adjust the baseline independently; instead, they present the impact analysis to the Change Control Board (CCB) to maintain governance and traceability. On the exam, this question tests your understanding that the change control process first step is submission, not approval or communication—a common trap is choosing “inform the sponsor” first, but formal documentation must precede any notification. Remember the mnemonic “SCR” for the sequence: Submit, then CCB reviews, then Revise the baseline.

⚠ Common exam trap

The PK0-005 exam often tests the misconception that the project manager can unilaterally adjust the schedule or fast-track tasks without formal change approval, but the correct first step is always to submit a change request to the CCB.

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 to the change control board with the revised schedule and impact analysis.

When a project is delayed due to an external factor like regulatory changes, the project manager must follow the formal change control process. Submitting a change request with the revised schedule and impact analysis ensures that the sponsor and change control board (CCB) can formally approve the new baseline, maintaining governance and traceability. This aligns with the PMBOK Guide's guidance on managing changes to the project management plan.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Inform the team and proceed with the new schedule.

    Why it's wrong here

    Proceeding without approval bypasses change control.

  • Resign from the project due to the delay.

    Why it's wrong here

    Resigning is not a professional response to a project delay.

  • Submit a change request to the change control board with the revised schedule and impact analysis.

    Why this is correct

    Following the change control process is the appropriate first step to get approval for the schedule change.

  • Fast-track the remaining tasks to recover time.

    Why it's wrong here

    Fast-tracking may not recover two months and should be part of a change request.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

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 team is experiencing scope creep because stakeholders keep adding minor features without formal approval. What is the best way to prevent this in the future?

medium
  • A.Implement a change control process
  • B.Increase project budget
  • C.Ignore the requests until the next phase
  • D.Update the project charter

Why A: A change control process is the formal mechanism to evaluate, approve, or reject changes to project scope. By requiring all feature requests to go through this process, the project manager ensures that scope creep is prevented because no minor feature can be added without documented approval and impact analysis. This directly addresses the root cause—stakeholders bypassing formal approval.

Last reviewed: Jun 24, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

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.