CAPM Practice Question: Project Management Fundamentals and Core Concepts
A project manager notices that the team is frequently redoing work because requirements were unclear. Which process group interaction would help address this issue?
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
✓
Iterative interactions between Planning and Executing
Iterative interactions between the Planning and Executing process groups allow for continuous feedback and refinement of requirements, reducing the need for rework. Option A is incorrect because a direct progression from Initiating to Closing skips the iterative cycles needed for requirement clarity. Option B is incorrect because sequential handoffs from Executing to Closing do not address issues that arise during planning. Option C is incorrect because continuous monitoring between Initiating and Planning does not cover the execution phase where rework occurs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Direct progression from Initiating to Closing
Why it's wrong here
Skipping Planning and Executing entirely leaves no mechanism to elicit, document or verify requirements, so the rework persists. It appeals when a project is trivial and needs no formal planning, but unclear requirements demand iterative Planning-to-Executing feedback, not a straight Initiating-to-Closing path.
- ✗
Sequential handoffs from Executing to Closing
Why it's wrong here
Handing work sequentially from Executing to Closing provides no feedback loop to correct misunderstood requirements before delivery, so defects surface only at closure. It suits stable, well-defined projects with fixed scope, but unclear requirements need iterative Planning-to-Executing cycles to refine and validate them.
- ✗
Continuous monitoring between Initiating and Planning
Why it's wrong here
Monitoring alone between Initiating and Planning detects nothing about requirement clarity, because Planning artefacts such as the requirements documentation and scope baseline are never produced or validated. It tempts teams wanting oversight without rework, yet the fix requires Planning-to-Executing iterations where requirements are elaborated and confirmed.
- ✓
Iterative interactions between Planning and Executing
Why this is correct
Iterative interactions between Planning and Executing let the team revisit and refine unclear requirements as work progresses, rather than freezing them upfront. This directly addresses the stem's constraint of frequent rework caused by ambiguity, because each cycle surfaces gaps early and feeds corrections back into planning before more effort is wasted.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CAPM question from scratch — 451 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CAPM practice question is part of Courseiva's free PMI 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 CAPM exam.