CAPM Business Analysis Frameworks Practice Question
A business analyst is planning stakeholder engagement for a new regulatory compliance project. To ensure stakeholder buy-in and minimize risks, when should the business analyst involve key stakeholders?
⚠ Common exam trap
CAPM often tests the misconception that stakeholder involvement is a phase (requirements or sign-off) rather than a continuous thread, so candidates pick the option that sounds most 'efficient' instead of the iterative best practice.
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
✓
Early and continuously throughout the project
Best practice in business analysis (per PMI's Business Analysis for Practitioners and the BABOK Guide) is to engage stakeholders early and continuously throughout the project lifecycle. Early involvement builds buy-in, surfaces requirements and constraints before costly rework, and continuous engagement keeps stakeholders aligned as scope, risks, and regulatory interpretations evolve — critical for a compliance project where regulations may shift.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Only during requirements gathering
Why it's wrong here
Restricting involvement to requirements gathering leaves stakeholders excluded from design decisions, testing and acceptance, so regulatory misinterpretations go unchallenged. Engagement must continue throughout the project; requirements gathering is only the first touchpoint, not the whole plan.
- ✗
Only at project sign-off
Why it's wrong here
Involving stakeholders only at sign-off gives them no opportunity to shape requirements, so regulatory gaps surface late and buy-in is withheld. Continuous engagement across the life cycle is expected; sign-off is merely the formal acceptance point, not the engagement window.
- ✓
Early and continuously throughout the project
Why this is correct
Engaging key stakeholders early and continuously lets the business analyst capture regulatory requirements, surface concerns and secure buy-in before decisions harden. Ongoing involvement sustains alignment through the project, reducing the likelihood of late resistance or compliance gaps that jeopardise acceptance.
- ✗
After the solution is developed
Why it's wrong here
Waiting until the solution is developed removes any chance to influence scope or design, guaranteeing rework when regulatory expectations differ. Stakeholders should be engaged from initiation onward; post-development review is validation, not engagement, and cannot secure buy-in.
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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official PMI exam blueprint
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.