Question 420 of 500
Tools and DocumentationmediumMultiple ChoiceObjective-mapped

Quick Answer

The correct document to update next is the project scope statement. This is because the scope statement formally defines the project’s boundaries, deliverables, and acceptance criteria, so when a change is approved through the change control process, it must be revised to reflect the newly authorized work and ensure all stakeholders share a common understanding. On the CompTIA Project+ PK0-005 exam, this tests your grasp of the change control process and the order of updates—a common trap is to jump to updating the work breakdown structure or project schedule first, but the scope statement is the authoritative source that must be updated before any downstream documents. A helpful memory tip is "Scope first, then schedule"—the scope statement is the foundation that defines what is in the project, so after approval, it must be the first document revised to capture the new feature.

PK0-005 Tools and Documentation Practice Question

This PK0-005 practice question tests your understanding of tools and documentation. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

During project execution, a stakeholder requests a new feature that was not in the original scope. The project manager adds it to the change log and obtains approval. Which document should be updated NEXT?

Question 1mediummultiple choice
Full question →

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

Project scope statement

The project scope statement defines the project's boundaries, deliverables, and acceptance criteria. When a new feature is approved via the change control process, the scope statement must be updated to reflect the newly authorized work, ensuring all stakeholders have a common understanding of the project's scope. This aligns with the PMBOK Guide's guidance that the scope statement is a key output of the 'Direct and Manage Project Work' process after a change request is approved.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

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

  • Work breakdown structure

    Why it's wrong here

    WBS updates follow scope updates.

  • Project scope statement

    Why this is correct

    The scope statement defines the baseline scope and must be updated for approved changes.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Communication plan

    Why it's wrong here

    While communication is important, the scope document is directly affected.

  • Lessons learned

    Why it's wrong here

    Lessons learned are captured throughout but not the immediate next step.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often think the WBS should be updated immediately after a scope change, but the correct sequence is to first update the project scope statement, which is the authoritative document defining what is in scope, before decomposing the new work into the WBS.

Detailed technical explanation

How to think about this question

Under the hood, the project scope statement serves as the baseline against which all scope changes are measured; it includes the scope description, acceptance criteria, and exclusions. When a change is approved, the project manager must update this baseline to reflect the new scope, which then triggers updates to other documents like the WBS and schedule. In real-world scenarios, failing to update the scope statement first can lead to scope creep, as team members may work from outdated scope definitions.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A practitioner preparing for the PK0-005 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related PK0-005 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free PK0-005 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this PK0-005 question test?

Tools and Documentation — This question tests Tools and Documentation — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Project scope statement — The project scope statement defines the project's boundaries, deliverables, and acceptance criteria. When a new feature is approved via the change control process, the scope statement must be updated to reflect the newly authorized work, ensuring all stakeholders have a common understanding of the project's scope. This aligns with the PMBOK Guide's guidance that the scope statement is a key output of the 'Direct and Manage Project Work' process after a change request is approved.

What should I do if I get this PK0-005 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

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

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.