Courseiva

PK0-005 Project Management Concepts Practice Question

A project manager has been authorized to lead a new customer-portal replacement effort. Before any detailed scheduling begins, the PM needs to formally document the measurable outcomes the portal must achieve, the boundaries of what will and will not be delivered, and the acceptance criteria the customer will use. Which document should the project manager produce FIRST to capture these items?

⚠ Common exam trap

The trap here is assuming any early project document will do, when the specific combination of measurable objectives, boundaries, and acceptance criteria points uniquely to the scope statement rather than the charter.

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

Measurable objectives, deliverable descriptions, scope boundaries, and acceptance criteria are all components of the project scope statement, which is developed once the project is authorized. The charter authorizes and sets high-level direction, while a work breakdown schedule and a responsibility assignment matrix address timing and staffing. Because the PM must document what acceptance will look like, the scope statement is the correct artifact.

Answer analysis

Option-by-option breakdown

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

  • ✗

    Project charter

    Why it's wrong here

    The project charter formally authorizes the project and names the project manager, but it captures high-level goals, success criteria, and constraints rather than detailed deliverable descriptions, boundaries, and acceptance criteria. The scenario says authorization has already occurred, and the PM now needs measurable outcomes and acceptance criteria documented, which is the purpose of the scope statement, not the charter.

  • ✗

    Work breakdown schedule

    Why it's wrong here

    A work breakdown schedule is a graphical scheduling tool showing work packages against calendar dates; it is produced after scope is decomposed and activities are sequenced. It cannot define boundaries or acceptance criteria, so it would be premature and would not satisfy what the customer needs documented at this point in the project.

  • ✗

    Responsibility assignment matrix

    Why it's wrong here

    A responsibility assignment matrix maps work packages or activities to the people or groups that perform, approve, or support them. It addresses who does the work, not what the project will deliver or how completion will be judged, so it cannot capture measurable outcomes, scope boundaries, or acceptance criteria for the portal effort.

  • ✓

    Project scope statement

    Why this is correct

    The scope statement documents the project's deliverables, measurable product and project objectives, the boundaries of the work (what is in and out of scope), and the acceptance criteria the customer will apply. That matches every element the PM must record before breaking work into a schedule, making it the correct next artifact to produce for the portal replacement.

About these practice questions

One of 954 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 →

How Courseiva writes practice questions · Editorial policy

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.