Question 3 of 500
Project Management ConceptshardMultiple ChoiceObjective-mapped

Quick Answer

The answer is that the project scope is defined early and changes are tightly constrained. This is the defining characteristic of a predictive life cycle, often called waterfall, because the entire project plan—including scope, schedule, and cost—is baselined at the start, and any deviation requires formal approval through a strict change control process. On the CompTIA Project+ PK0-005 exam, this concept tests your ability to distinguish predictive from adaptive life cycles; a common trap is confusing “defined early” with “no changes allowed,” when in reality changes are simply controlled, not forbidden. For memory, think of the phrase “scope first, changes last”—the predictive approach locks in requirements upfront to minimize disruption, making it ideal for projects with fixed regulatory or contractual specifications.

PK0-005 Project Management Concepts Practice Question

This PK0-005 practice question tests your understanding of project management concepts. 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.

A project manager is using a predictive life cycle for a software development project. What is a key characteristic of this approach?

Question 1hardmultiple 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

The project scope is defined early and changes are constrained

In a predictive (waterfall) life cycle, the project scope is defined and baselined early in the project, and changes are tightly controlled through a formal change control process. This approach is suitable for software development projects where requirements are well-understood and unlikely to change significantly, such as when building a system with fixed regulatory or contractual specifications.

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.

  • Deliverables are produced in small increments

    Why it's wrong here

    Incremental life cycles deliver in small pieces.

  • The project scope is defined early and changes are constrained

    Why this is correct

    Predictive life cycles require detailed planning upfront and manage changes through formal process.

    Related concept

    Read the scenario before looking for a memorised answer.

  • The team adapts to changing requirements

    Why it's wrong here

    Adaptive life cycles (e.g., Agile) embrace change.

  • Requirements are defined iteratively

    Why it's wrong here

    Iterative life cycles define requirements in iterations.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse 'predictive' with 'iterative' or 'agile' because all involve phases, but the key differentiator is when scope is finalized and how changes are handled—predictive locks scope early, while agile embraces change throughout.

Detailed technical explanation

How to think about this question

Under the hood, a predictive life cycle relies on a detailed Work Breakdown Structure (WBS) and a project management plan that is approved before execution begins. Real-world scenarios include government or defense software contracts where requirements are locked in a Request for Proposal (RFP) and changes require a formal contract modification, often invoking the PMBOK Guide's integrated change control process.

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?

Project Management Concepts — This question tests Project Management Concepts — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The project scope is defined early and changes are constrained — In a predictive (waterfall) life cycle, the project scope is defined and baselined early in the project, and changes are tightly controlled through a formal change control process. This approach is suitable for software development projects where requirements are well-understood and unlikely to change significantly, such as when building a system with fixed regulatory or contractual specifications.

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

Keep practising

More PK0-005 practice questions

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.