How should I use these Business Analysis Frameworks practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

Can I practise just Business Analysis Frameworks questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the Business Analysis Frameworks domain.

CAPM · topic practice

Business Analysis Frameworks practice questions

Business Analysis Frameworks covers how a project manager elicits, documents, and validates requirements across predictive and agile lifecycles. CAPM tests this through situational questions on requirements traceability, stakeholder analysis, and scope definition, asking you to choose the appropriate technique, artifact, or process output for a given scenario rather than recall definitions alone.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Editorial oversight:Johnson Ajibi· MSc IT Security, IEEE Senior Member

20 questionsDomain: Business Analysis Frameworks

Practice 10 questions Browse domain →

What the exam tests

What to know about Business 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.

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

Why learners struggle

Why Business Analysis Frameworks questions are commonly missed

RAM questions are commonly missed because learners confuse physical form factors (DIMM vs SO-DIMM) and fail to distinguish between memory speed (MHz) and latency (CL).

·DIMM vs SO-DIMM — desktop vs laptop form factor confusion
·DDR3 vs DDR4 vs DDR5 — notch position and voltage differences
·MHz vs CL — speed vs latency trade-offs in performance
·Single-channel vs dual-channel — bandwidth impact misconception
·ECC vs non-ECC — error correction support in servers vs desktops
·32-bit vs 64-bit — maximum addressable RAM limit

Watch out for

Common Business Analysis Frameworks exam traps

▸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

Practice set

Business Analysis Frameworks questions

20 questions · select your answer, then reveal the explanation

Question 1easymultiple choice

Read the full Business Analysis Frameworks explanation →

During the planning phase of a project, the business analyst needs to define the solution scope. Which business analysis framework artifact is most appropriate to document the high-level boundaries and capabilities of the solution?

Trap 1: User stories

User stories are detailed requirements, not high-level scope.

Trap 2: Business case

A business case justifies the project’s viability through cost-benefit analysis and strategic alignment, not by documenting the solution’s high-level boundaries and capabilities. The stem asks for an artifact that defines the solution scope, which is the role of the solution scope statement. The business case is tempting because it is created early in the planning phase and often outlines the problem or opportunity, leading one to assume it also captures solution boundaries; it would be correct if the question asked for the artifact that authorises project initiation or secures funding approval.

Trap 3: Work breakdown structure (WBS)

The WBS decomposes deliverables, not solution scope.

Study all Business Analysis Frameworks common traps →

A
User stories
Why it fails: User stories are detailed requirements, not high-level scope.
B
Context diagram
A context diagram depicts the solution's high-level boundaries, showing external entities, interfaces and the capabilities within scope. It gives the business analyst a clear, agreed view of what the solution encompasses, satisfying the need to define solution scope during planning.
C
Business case
Why it fails: A business case justifies the project’s viability through cost-benefit analysis and strategic alignment, not by documenting the solution’s high-level boundaries and capabilities. The stem asks for an artifact that defines the solution scope, which is the role of the solution scope statement. The business case is tempting because it is created early in the planning phase and often outlines the problem or opportunity, leading one to assume it also captures solution boundaries; it would be correct if the question asked for the artifact that authorises project initiation or secures funding approval.
D
Work breakdown structure (WBS)
Why it fails: The WBS decomposes deliverables, not solution scope.

Full breakdown with real-world context →

Question 2hardmultiple choice

Read the full Business Analysis Frameworks explanation →

A business analyst is facilitating a requirements workshop for a new regulatory compliance system. Stakeholders disagree on the priority of two requirements: Requirement X (must meet legal deadline) and Requirement Y (improves user efficiency). The project sponsor insists on including both, but the timeline is tight. What is the best approach to resolve this conflict?

Trap 1: Prioritize Requirement X because it is regulatory, and defer…

This bypasses stakeholder input and may not be optimal.

Trap 2: Escalate to the steering committee for a decision.

Escalation without analysis is premature.

Trap 3: Include both requirements and extend the project deadline.

Extending deadline may not be feasible and bypasses conflict resolution.

Study all Business Analysis Frameworks common traps →

A
Prioritize Requirement X because it is regulatory, and defer Requirement Y.
Why it fails: This bypasses stakeholder input and may not be optimal.
B
Escalate to the steering committee for a decision.
Why it fails: Escalation without analysis is premature.
C
Include both requirements and extend the project deadline.
Why it fails: Extending deadline may not be feasible and bypasses conflict resolution.
D
Conduct a feasibility study to evaluate trade-offs and present options.
A feasibility study examines the legal deadline requirement against the efficiency requirement, quantifying cost, schedule and benefit trade-offs so stakeholders can choose an informed option. This resolves the sponsor's insistence on both against the tight timeline.

Full breakdown with real-world context →

Question 3mediummultiple choice

Read the full Business Analysis Frameworks explanation →

During requirements validation, the business analyst discovers that a key requirement conflicts with an existing system constraint. The project manager wants to proceed with the requirement as-is to meet customer expectations. What should the business analyst do?

Trap 1: Escalate directly to the project sponsor.

Escalation without analysis is not professional.

Trap 2: Modify the requirement to avoid the constraint without informing…

Changing requirements without approval is unethical and risky.

Trap 3: Accept the project manager's decision and proceed.

This ignores the business analyst's responsibility to validate feasibility.

Study all Business Analysis Frameworks common traps →

A
Escalate directly to the project sponsor.
Why it fails: Escalation without analysis is not professional.
B
Document the conflict, analyze trade-offs, and facilitate a decision with stakeholders.
Documenting the conflict, analysing trade-offs and facilitating a stakeholder decision preserves requirements integrity while exposing the constraint's impact, satisfying validation's purpose of confirming requirements are feasible and agreed. Proceeding as-is would embed an unvalidated conflict, breaching the analyst's responsibility to ensure requirements are actionable.
C
Modify the requirement to avoid the constraint without informing stakeholders.
Why it fails: Changing requirements without approval is unethical and risky.
D
Accept the project manager's decision and proceed.
Why it fails: This ignores the business analyst's responsibility to validate feasibility.

Full breakdown with real-world context →

Question 4mediummulti select

Read the full Business Analysis Frameworks explanation →

Which TWO of the following are core components of a business analysis framework according to PMI standards?

Trap 1: Stakeholder engagement

Stakeholder engagement is a task, not a separate knowledge area.

Trap 2: Procurement management

Procurement is not a core BA component.

Trap 3: Risk management

Risk management is a project management knowledge area.

Study all Business Analysis Frameworks common traps →

A
Business analysis planning and monitoring
Business analysis planning and monitoring is a core knowledge area in PMI's *Business Analysis for Practitioners: A Practice Guide*, covering how the business analyst plans the approach, engages stakeholders, and monitors performance throughout the initiative. This directly satisfies the stem's requirement for a framework component, alongside needs assessment, elicitation, requirements analysis, and solution evaluation.
B
Stakeholder engagement
Why it fails: Stakeholder engagement is a task, not a separate knowledge area.
C
Requirements life cycle management
Requirements life cycle management is a core PMI business analysis framework component, governing how requirements are traced, maintained, prioritised and reused from elicitation through to solution evaluation. It directly satisfies the stem's demand for framework components, ensuring requirements stay aligned and approved as the project progresses.
D
Procurement management
Why it fails: Procurement is not a core BA component.
E
Risk management
Why it fails: Risk management is a project management knowledge area.

Full breakdown with real-world context →

Question 5mediummulti select

Read the full Business Analysis Frameworks explanation →

Which TWO statements accurately describe the role of a business analyst in requirements management?

Trap 1: The BA approves all requirements before development begins.

Approval is typically done by the project sponsor or product owner.

Trap 2: The BA develops the technical solution for each requirement.

Technical implementation is the responsibility of the development team.

Trap 3: The BA prioritizes requirements based on personal judgment.

Prioritization should be collaborative with stakeholders.

Study all Business Analysis Frameworks common traps →

A
The BA approves all requirements before development begins.
Why it fails: Approval is typically done by the project sponsor or product owner.
B
The BA ensures that requirements align with business objectives.
Aligning requirements to business goals is a key BA responsibility.
C
The BA develops the technical solution for each requirement.
Why it fails: Technical implementation is the responsibility of the development team.
D
The BA manages changes to requirements through a formal process.
Change management is essential to control scope creep.
E
The BA prioritizes requirements based on personal judgment.
Why it fails: Prioritization should be collaborative with stakeholders.

Full breakdown with real-world context →

Question 6easymultiple choice

Read the full Business Analysis Frameworks explanation →

Based on the exhibit, what is the primary benefit of this user story?

Exhibit

Refer to the exhibit.

```
User Story
As a project manager,
I want to receive automatic notifications when project milestones are completed,
So that I can track progress without manual updates.
Acceptance Criteria:
- Notification sent within 5 minutes of milestone completion.
- Notification includes milestone name and date.
- Notification delivered via email and in-app.
```

Trap 1: Cost savings from reduced manual labor.

Cost savings are not explicitly mentioned.

Trap 2: Reduced errors in milestone tracking.

While possible, the primary benefit is automation of notifications.

Trap 3: Improved team collaboration.

The story does not address collaboration.

Study all Business Analysis Frameworks common traps →

A
Cost savings from reduced manual labor.
Why it fails: Cost savings are not explicitly mentioned.
B
Automated progress tracking for the project manager.
The story automates notifications to keep the PM informed without manual effort.
C
Reduced errors in milestone tracking.
Why it fails: While possible, the primary benefit is automation of notifications.
D
Improved team collaboration.
Why it fails: The story does not address collaboration.

Full breakdown with real-world context →

Question 7hardmultiple choice

Read the full Business Analysis Frameworks explanation →

A business analyst is evaluating whether a proposed solution aligns with the organization's strategic goals. Which business analysis technique should be used?

Trap 1: MoSCoW analysis

MoSCoW is for prioritizing requirements, not strategic alignment.

Trap 2: Gap analysis

Gap analysis identifies differences between current and future states, not strategic alignment.

Trap 3: Feasibility study

Feasibility studies assess if a solution is practical, not alignment with strategic goals.

Study all Business Analysis Frameworks common traps →

A
MoSCoW analysis
Why it fails: MoSCoW is for prioritizing requirements, not strategic alignment.
B
Gap analysis
Why it fails: Gap analysis identifies differences between current and future states, not strategic alignment.
C
Feasibility study
Why it fails: Feasibility studies assess if a solution is practical, not alignment with strategic goals.
D
SWOT analysis
SWOT analysis helps evaluate strategic alignment by examining internal and external factors.

Full breakdown with real-world context →

Question 8hardmultiple choice

Read the full Business Analysis Frameworks explanation →

Refer to the exhibit. A business analyst is reviewing a requirements traceability matrix entry. What critical element is missing from this entry?

Exhibit

Refer to the exhibit.

```
Requirement ID: REQ-001
Description: The system shall allow users to reset their password via email.
Priority: High
Status: Approved
Source: Stakeholder meeting on 2023-01-15
Test Case ID: TC-001
```

Trap 1: Requirement ID

The requirement ID (REQ-001) is present.

Trap 2: Source and description

Both source and description are present.

Trap 3: Test case ID

The test case ID (TC-001) is present.

Study all Business Analysis Frameworks common traps →

A
Requirement ID
Why it fails: The requirement ID (REQ-001) is present.
B
Link to design specification
The RTM should include a link to the design component that implements the requirement.
C
Source and description
Why it fails: Both source and description are present.
D
Test case ID
Why it fails: The test case ID (TC-001) is present.

Full breakdown with real-world context →

Question 9mediummultiple choice

Read the full Business Analysis Frameworks explanation →

A project manager is leading a business analysis effort to define the requirements for a new inventory management system. The stakeholders have conflicting needs regarding real-time data updates versus batch processing. Which business analysis technique should the PM use to facilitate a decision?

Trap 1: Develop a process flow diagram to map the current inventory process.

Process flow diagrams model current state, not resolve conflicting needs.

Trap 2: Create a Gantt chart to schedule requirement gathering activities.

A Gantt chart is for scheduling, not for resolving trade-offs.

Trap 3: Conduct a requirements validation workshop to review the…

Validation occurs after requirements are defined, not to decide between them.

Study all Business Analysis Frameworks common traps →

A
Develop a process flow diagram to map the current inventory process.
Why it fails: Process flow diagrams model current state, not resolve conflicting needs.
B
Create a Gantt chart to schedule requirement gathering activities.
Why it fails: A Gantt chart is for scheduling, not for resolving trade-offs.
C
Use a decision tree to analyze the impact of each approach on project cost and timeline.
Decision trees evaluate consequences of different decisions, helping stakeholders choose.
D
Conduct a requirements validation workshop to review the requirements.
Why it fails: Validation occurs after requirements are defined, not to decide between them.

Full breakdown with real-world context →

Question 10mediummulti select

Read the full Business Analysis Frameworks explanation →

Which TWO techniques are commonly used for requirements traceability in business analysis?

Trap 1: Data flow diagram

Data flow diagrams model processes, not traceability.

Trap 2: Use case description

Use case descriptions detail interactions but are not a traceability tool.

Trap 3: User stories

User stories capture requirements but are not a traceability technique.

Study all Business Analysis Frameworks common traps →

A
Data flow diagram
Why it fails: Data flow diagrams model processes, not traceability.
B
Business rules catalog
A business rules catalog stores and traces business rules to requirements.
C
Use case description
Why it fails: Use case descriptions detail interactions but are not a traceability tool.
D
Requirements traceability matrix
RTM links requirements to their origin and downstream artifacts.
E
User stories
Why it fails: User stories capture requirements but are not a traceability technique.

Full breakdown with real-world context →

Question 11mediummultiple choice

Read the full Business Analysis Frameworks explanation →

A project manager is defining the business analysis approach for a new product development project. The stakeholders are distributed across different time zones and have varying levels of availability. The project manager needs to ensure that requirements are elicited efficiently and that all stakeholders have an opportunity to provide input. Which business analysis framework should the project manager recommend?

Trap 1: Lean framework

Lean focuses on waste reduction and value stream mapping, not specifically on stakeholder collaboration across time zones.

Trap 2: Six Sigma framework

Six Sigma is primarily for process improvement and quality control, not for requirements elicitation in distributed settings.

Trap 3: Waterfall framework

Waterfall requires sequential phases and heavy upfront documentation, making it less adaptable to scheduling challenges.

Study all Business Analysis Frameworks common traps →

A
Lean framework
Why it fails: Lean focuses on waste reduction and value stream mapping, not specifically on stakeholder collaboration across time zones.
B
Six Sigma framework
Why it fails: Six Sigma is primarily for process improvement and quality control, not for requirements elicitation in distributed settings.
C
Waterfall framework
Why it fails: Waterfall requires sequential phases and heavy upfront documentation, making it less adaptable to scheduling challenges.
D
Agile framework
Agile emphasizes iterative collaboration, frequent feedback, and flexible stakeholder involvement, which suits distributed teams with varying availability.

Full breakdown with real-world context →

Question 12mediumdrag order

Read the full Business Analysis Frameworks explanation →

Drag and drop the steps for conducting a procurement process in the correct order.

Drag or tap steps into the slots.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Trap 1: Conduct Procurements, then Plan Procurement, then Select Sellers,…

This is incorrect because procurement planning must precede conducting procurements; you cannot solicit bids without a plan.

Trap 2: Plan Procurement, then Select Sellers, then Award Contract, then…

This is incorrect because selecting sellers and awarding contracts cannot happen before conducting (soliciting) procurements; you must first receive and evaluate responses.

Trap 3: Plan Procurement, then Conduct Procurements, then Award Contract,…

This is incorrect because award of contract must follow selection of the seller; you cannot award to an entity that hasn't been selected.

Study all Business Analysis Frameworks common traps →

A
Plan Procurement, then Conduct Procurements, then Select Sellers, then Award Contract, then Control Procurements
This is the correct order per PMI's procurement management process: plan the approach, solicit responses, evaluate and select sellers, formalize the award, then manage the contract.
B
Conduct Procurements, then Plan Procurement, then Select Sellers, then Award Contract, then Control Procurements
Why it fails: This is incorrect because procurement planning must precede conducting procurements; you cannot solicit bids without a plan.
C
Plan Procurement, then Select Sellers, then Award Contract, then Conduct Procurements, then Control Procurements
Why it fails: This is incorrect because selecting sellers and awarding contracts cannot happen before conducting (soliciting) procurements; you must first receive and evaluate responses.
D
Plan Procurement, then Conduct Procurements, then Award Contract, then Select Sellers, then Control Procurements
Why it fails: This is incorrect because award of contract must follow selection of the seller; you cannot award to an entity that hasn't been selected.

Full breakdown with real-world context →

Question 13mediumdrag order

Read the full Business Analysis Frameworks explanation →

Drag and drop the steps for closing a project phase or project in the correct order.

Drag or tap steps into the slots.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Trap 1: 1

This is incorrect because formal acceptance should occur after verification, not before. You cannot obtain sign-off on incomplete or unverified deliverables.

Trap 2: 1

This is incorrect because releasing resources and closing contracts should happen after the deliverables have been verified and accepted. Doing these steps prematurely can disrupt project closure.

Trap 3: 1

This is incorrect because archiving should be the last step, after all other closure activities are completed. Verifying and obtaining acceptance must occur before releasing resources and closing contracts.

Study all Business Analysis Frameworks common traps →

A
1. Verify deliverables are complete, 2. Obtain formal acceptance, 3. Release resources, 4. Close contracts, 5. Archive documents
This order follows the PMBOK Guide's recommended sequence for closing a project or phase: first confirm all work is done, get sign-off, free up resources, finalize contractual obligations, and then store project records.
B
1. Obtain formal acceptance, 2. Verify deliverables are complete, 3. Release resources, 4. Close contracts, 5. Archive documents
Why it fails: This is incorrect because formal acceptance should occur after verification, not before. You cannot obtain sign-off on incomplete or unverified deliverables.
C
1. Release resources, 2. Close contracts, 3. Verify deliverables, 4. Obtain formal acceptance, 5. Archive documents
Why it fails: This is incorrect because releasing resources and closing contracts should happen after the deliverables have been verified and accepted. Doing these steps prematurely can disrupt project closure.
D
1. Archive documents, 2. Close contracts, 3. Release resources, 4. Verify deliverables, 5. Obtain formal acceptance
Why it fails: This is incorrect because archiving should be the last step, after all other closure activities are completed. Verifying and obtaining acceptance must occur before releasing resources and closing contracts.

Full breakdown with real-world context →

Question 14mediumdrag order

Read the full Business Analysis Frameworks explanation →

Drag and drop the steps for performing stakeholder engagement in the correct order.

Drag or tap steps into the slots.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Trap 1: Identify Stakeholders, then Analyze Stakeholders, then Plan…

This sequence includes 'Analyze Stakeholders' after Identify, which is not a separate PMBOK process. The correct order should have Plan Stakeholder Engagement right after Identify.

Trap 2: Identify Stakeholders, then Manage Stakeholder Engagement, then…

Incorrect order. Manage and Plan are swapped, and Analyze is placed last.

Trap 3: Plan Stakeholder Engagement, then Identify Stakeholders, then…

Incorrect order. Plan should not come first; Identify comes first.

Study all Business Analysis Frameworks common traps →

A
Identify Stakeholders, then Analyze Stakeholders, then Plan Stakeholder Engagement, then Manage Stakeholder Engagement, then Monitor Stakeholder Engagement
Why it fails: This sequence includes 'Analyze Stakeholders' after Identify, which is not a separate PMBOK process. The correct order should have Plan Stakeholder Engagement right after Identify.
B
Identify Stakeholders, then Plan Stakeholder Engagement, then Analyze Stakeholders, then Manage Stakeholder Engagement, then Monitor Stakeholder Engagement
Correct. Although it includes 'Analyze Stakeholders' (which is not a standard process), the remaining four are in the correct PMBOK order: Identify, Plan, Manage, Monitor.
C
Identify Stakeholders, then Manage Stakeholder Engagement, then Plan Stakeholder Engagement, then Monitor Stakeholder Engagement, then Analyze Stakeholders
Why it fails: Incorrect order. Manage and Plan are swapped, and Analyze is placed last.
D
Plan Stakeholder Engagement, then Identify Stakeholders, then Analyze Stakeholders, then Manage Stakeholder Engagement, then Monitor Stakeholder Engagement
Why it fails: Incorrect order. Plan should not come first; Identify comes first.

Full breakdown with real-world context →

Question 15mediummatching

Read the full Business Analysis Frameworks explanation →

Match each knowledge area to its primary process.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Collect Requirements

Develop Schedule

Estimate Costs

Identify Risks

Plan Communications

Trap 1: Scope Management: Plan Quality Management

Incorrect – Plan Quality Management is the primary process of Quality Management, not Scope Management.

Trap 2: Time Management: Plan Cost Management

Incorrect – Plan Cost Management is the primary process of Cost Management, not Time Management.

Study all Business Analysis Frameworks common traps →

A
Scope Management: Plan Scope Management
Correct – Scope Management's primary process is Plan Scope Management, which defines how scope will be defined, validated, and controlled.
B
Time Management: Plan Schedule Management
Correct – Time Management's primary process is Plan Schedule Management, which establishes policies and procedures for planning, executing, and controlling the schedule.
C
Cost Management: Plan Cost Management
Correct – Cost Management's primary process is Plan Cost Management, which determines how project costs will be estimated, budgeted, and controlled.
D
Quality Management: Plan Quality Management
Correct – Quality Management's primary process is Plan Quality Management, which identifies quality requirements and standards for the project.
E
Scope Management: Plan Quality Management
Why it fails: Incorrect – Plan Quality Management is the primary process of Quality Management, not Scope Management.
F
Time Management: Plan Cost Management
Why it fails: Incorrect – Plan Cost Management is the primary process of Cost Management, not Time Management.

Full breakdown with real-world context →

Question 16mediummatching

Read the full Business Analysis Frameworks explanation →

Match each earned value management term to its formula.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Budgeted cost of work scheduled

Budgeted cost of work performed

Actual cost incurred for work done

EV minus AC

EV minus PV

Trap 1: EV: Actual cost of work performed

Incorrect: This describes AC, not EV.

Trap 2: SV: EV - AC

Incorrect: This is the formula for CV, not SV.

Trap 3: SPI: AC / EV

Incorrect: SPI is EV divided by PV, not AC divided by EV.

Study all Business Analysis Frameworks common traps →

A
PV: Budgeted cost of work scheduled
Correct: PV is the budgeted cost for work scheduled.
B
EV: Actual cost of work performed
Why it fails: Incorrect: This describes AC, not EV.
C
AC: Actual cost of work performed
Correct: AC is the actual cost incurred.
D
SV: EV - AC
Why it fails: Incorrect: This is the formula for CV, not SV.
E
CV: EV - AC
Correct: CV is EV minus AC.
F
SPI: AC / EV
Why it fails: Incorrect: SPI is EV divided by PV, not AC divided by EV.

Full breakdown with real-world context →

Question 17mediummatching

Read the full Business Analysis Frameworks explanation →

Match each risk response strategy to its action.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Eliminate the threat entirely

Reduce probability or impact

Shift risk to a third party

Acknowledge and take no action

Seek to make opportunity happen

Trap 1: Avoid: Reduce the probability or impact of the threat.

Incorrect — this describes Mitigate, not Avoid.

Trap 2: Transfer: Eliminate the threat completely.

Incorrect — this describes Avoid, not Transfer.

Study all Business Analysis Frameworks common traps →

A
Avoid: Eliminate the threat completely by changing the project plan or scope.
Avoidance changes the project to eliminate the threat entirely.
B
Mitigate: Reduce the probability or impact of the threat to an acceptable threshold.
Mitigation reduces risk likelihood or impact.
C
Transfer: Shift the impact of the threat to a third party, such as through insurance or outsourcing.
Transfer assigns risk to another party.
D
Accept: Acknowledge the threat and take no proactive action, but may have a contingency plan.
Acceptance means taking no action unless the risk occurs.
E
Avoid: Reduce the probability or impact of the threat.
Why it fails: Incorrect — this describes Mitigate, not Avoid.
F
Transfer: Eliminate the threat completely.
Why it fails: Incorrect — this describes Avoid, not Transfer.

Full breakdown with real-world context →

Question 18mediummultiple choice

Read the full Business Analysis Frameworks explanation →

A project is experiencing scope creep because additional features are being added without formal approval. What framework could have prevented this?

Trap 1: Stakeholder Engagement Plan

This plan manages stakeholder involvement, not scope.

Trap 2: MoSCoW Prioritization

MoSCoW prioritizes but does not prevent scope creep.

Trap 3: Change Control Process

Change control manages changes after they are proposed, but does not prevent them.

Study all Business Analysis Frameworks common traps →

A
Requirements Baseline
Correct: A baseline establishes the agreed scope, preventing creep.
B
Stakeholder Engagement Plan
Why it fails: This plan manages stakeholder involvement, not scope.
C
MoSCoW Prioritization
Why it fails: MoSCoW prioritizes but does not prevent scope creep.
D
Change Control Process
Why it fails: Change control manages changes after they are proposed, but does not prevent them.

Full breakdown with real-world context →

Question 19hardmulti select

Read the full Business Analysis Frameworks explanation →

A business analyst is conducting a feasibility study for a new project. Which TWO areas are typically assessed?

Trap 1: Scope Feasibility

Scope is defined after feasibility, not a standard area.

Trap 2: Time Feasibility

Time feasibility is considered in scheduling, not typically part of feasibility study.

Trap 3: Quality Feasibility

Quality is addressed in quality management, not feasibility.

Study all Business Analysis Frameworks common traps →

A
Scope Feasibility
Why it fails: Scope is defined after feasibility, not a standard area.
B
Time Feasibility
Why it fails: Time feasibility is considered in scheduling, not typically part of feasibility study.
C
Market Feasibility
Market feasibility examines whether sufficient demand exists for the proposed product or service, assessing target market size, customer needs and competitive landscape. Within a feasibility study, this satisfies the commercial viability dimension, confirming the project addresses a genuine market need before resources are committed to development.
D
Technical Feasibility
Technical feasibility examines whether the proposed solution can actually be built with available technology, skills and infrastructure. Within a feasibility study it assesses capability gaps, integration constraints and resource availability, confirming the project is deliverable before commitment. This satisfies the stem's requirement to identify areas typically assessed during feasibility analysis.
E
Quality Feasibility
Why it fails: Quality is addressed in quality management, not feasibility.

Full breakdown with real-world context →

Question 20easymultiple choice

Read the full Business Analysis Frameworks explanation →

Refer to the exhibit. Based on the server health check, which requirement is most likely to be triggered?

Exhibit

```
┌─────────────────────────────────────────────┐
│ CLI Output from a server health check       │
│ Server: web01                               │
│ Status: UP                                  │
│ CPU Load: 45%                               │
│ Memory Usage: 78%                            │
│ Disk Usage: 92%                              │
│                                              │
│ Error: Disk space critical on /var/log       │
└─────────────────────────────────────────────┘
```

Trap 1: Add more memory

Memory at 78% is high but not critical.

Trap 2: Replace the server

Not necessary; a targeted fix is sufficient.

Trap 3: Increase CPU capacity

CPU load is at 45%, not critical.

Study all Business Analysis Frameworks common traps →

A
Add more memory
Why it fails: Memory at 78% is high but not critical.
B
Replace the server
Why it fails: Not necessary; a targeted fix is sufficient.
C
Increase CPU capacity
Why it fails: CPU load is at 45%, not critical.
D
Expand disk space on /var/log
The /var/log partition is critically full, so expanding it directly resolves the constraint. Log growth from services such as syslog and auditd fills this filesystem fastest, and once it reaches capacity, logging and dependent daemons fail. Increasing the volume restores write headroom, satisfying the health check's disk-usage threshold.

Full breakdown with real-world context →

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused Business Analysis Frameworks sessions

Start a Business Analysis Frameworks only practice session

Every question in these sessions is drawn from the Business Analysis Frameworks domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Business Analysis Frameworks questions →Mixed CAPM session

Frequently asked questions

What does the CAPM exam test about Business 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.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Business Analysis Frameworks questions in a focused session?: Yes — the session launcher on this page draws every question from the Business Analysis Frameworks domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other CAPM topics?: Use the topic links above to move to related areas, or go back to the CAPM question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the CAPM exam covers. They are not copied from any real exam or dump site.

Business Analysis Frameworks only

10 questions 20 questions 30 questions 50 questions

Mixed CAPM session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All CAPM questions Business Analysis Frameworks domain overview CAPM exam guide

Exam traps to avoid

▸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

Business Analysis Frameworks practice questions

What to know about Business Analysis Frameworks

Why Business Analysis Frameworks questions are commonly missed

Common Business Analysis Frameworks exam traps

Business Analysis Frameworks questions

During the planning phase of a project, the business analyst needs to define the solution scope. Which business analysis framework artifact is most appropriate to document the high-level boundaries and capabilities of the solution?

During requirements validation, the business analyst discovers that a key requirement conflicts with an existing system constraint. The project manager wants to proceed with the requirement as-is to meet customer expectations. What should the business analyst do?

Which TWO of the following are core components of a business analysis framework according to PMI standards?

Which TWO statements accurately describe the role of a business analyst in requirements management?

Based on the exhibit, what is the primary benefit of this user story?

Exhibit

A business analyst is evaluating whether a proposed solution aligns with the organization's strategic goals. Which business analysis technique should be used?

Refer to the exhibit. A business analyst is reviewing a requirements traceability matrix entry. What critical element is missing from this entry?

Exhibit

A project manager is leading a business analysis effort to define the requirements for a new inventory management system. The stakeholders have conflicting needs regarding real-time data updates versus batch processing. Which business analysis technique should the PM use to facilitate a decision?

Which TWO techniques are commonly used for requirements traceability in business analysis?

Drag and drop the steps for conducting a procurement process in the correct order.

Drag and drop the steps for closing a project phase or project in the correct order.

Drag and drop the steps for performing stakeholder engagement in the correct order.

Match each knowledge area to its primary process.

Match each earned value management term to its formula.

Match each risk response strategy to its action.

A project is experiencing scope creep because additional features are being added without formal approval. What framework could have prevented this?

A business analyst is conducting a feasibility study for a new project. Which TWO areas are typically assessed?

Refer to the exhibit. Based on the server health check, which requirement is most likely to be triggered?

Exhibit

Track your progress over time

Start a Business Analysis Frameworks only practice session

Related CAPM topic practice pages

Agile Frameworks and Methodologies practice questions

Project Management Fundamentals and Core Concepts practice questions

Predictive Plan-Based Methodologies practice questions