CAPM Cheat Sheet

#	Domain	Weight	Questions	Practice
4.0	Business Analysis Frameworks	27%	216	Practice →
Total	27%	643

Domain

Weight

Questions

Practice

4.0

Business Analysis Frameworks

27%

216

Practice →

Total

27%

643

Domain Quick Reference

4.0Business Analysis Frameworks

Map each requirement to its source and deliverable in a requirements traceability matrix, then validate scope through stakeholder sign-off; in Jira, link epics to stories via issue links and confirm acceptance criteria before baseline.

27%

Key concepts

✓Selecting elicitation techniques like interviews, focus groups, or observation for a given stakeholder scenario
✓Distinguishing product scope from project scope using the scope baseline and requirements documentation
✓Applying requirements traceability matrix to link requirements to business objectives and deliverables
✓Choosing predictive versus adaptive lifecycle approaches based on requirement stability and stakeholder availability

Watch out for

⚠Confusing product scope with project scope, then selecting the wrong baseline document or change control path
⚠Treating the requirements traceability matrix as a scheduling tool rather than a requirements-to-objective linkage artifact
⚠Assuming agile projects skip requirements documentation entirely, ignoring the product backlog and user story acceptance criteria

Exam Day Reminders

→Read every question stem fully — look for qualifiers like 'MOST likely,' 'BEST,' or 'EXCEPT.'

→Flag uncertain questions and come back — don't waste time on one question.

→Eliminate obviously wrong options first, then choose between remaining ones.

→Trust your first instinct unless you have a specific reason to change.

→For CAPM, scenarios typically have one clearly best answer — look for the option that matches the specific constraints in the question.

#	Domain	Weight	Questions	Practice
4.0	Business Analysis Frameworks	27%	216	Practice →
Total	27%	643

Domain

Weight

Questions

Practice

4.0

Business Analysis Frameworks

27%

216

Practice →

Total

27%

643

Domain Quick Reference

4.0Business Analysis Frameworks

27%

Key concepts

✓Selecting elicitation techniques like interviews, focus groups, or observation for a given stakeholder scenario
✓Distinguishing product scope from project scope using the scope baseline and requirements documentation
✓Applying requirements traceability matrix to link requirements to business objectives and deliverables
✓Choosing predictive versus adaptive lifecycle approaches based on requirement stability and stakeholder availability

Watch out for

⚠Confusing product scope with project scope, then selecting the wrong baseline document or change control path
⚠Treating the requirements traceability matrix as a scheduling tool rather than a requirements-to-objective linkage artifact
⚠Assuming agile projects skip requirements documentation entirely, ignoring the product backlog and user story acceptance criteria

Exam Day Reminders

→Read every question stem fully — look for qualifiers like 'MOST likely,' 'BEST,' or 'EXCEPT.'

→Flag uncertain questions and come back — don't waste time on one question.

→Eliminate obviously wrong options first, then choose between remaining ones.

→Trust your first instinct unless you have a specific reason to change.

→For CAPM, scenarios typically have one clearly best answer — look for the option that matches the specific constraints in the question.

CAPM Exam Blueprint — At a Glance

Domain Quick Reference

4.0Business Analysis Frameworks

Exam Day Reminders

More CAPM resources

CAPM Cheat Sheet

CAPM Exam Blueprint — At a Glance

Domain Quick Reference

4.0Business Analysis Frameworks

Exam Day Reminders

More CAPM resources