Knowledge + Practice

CCNA Business Analysis Frameworks Questions

75 of 141 questions · Page 1/2 · Business Analysis Frameworks · Answers revealed

Practice these questions Domain overview All questions

1

MCQhard

You are a business analyst working on a project to digitize the supply chain operations of a large logistics company. After completing the requirements documentation, you review the requirements against the organization's strategic goals. You discover that several key requirements directly conflict with the company's recently announced strategic objective to reduce carbon emissions by 30% within two years. Specifically, the proposed solution relies on increased just-in-time deliveries that would require more transportation, contradicting the sustainability goal. You bring this to the attention of the project sponsor, who is the VP of Operations. The sponsor acknowledges the conflict but insists on proceeding with the original requirements, arguing that the strategic goal is not feasible and that operational efficiency is more important. The project is already approved and has a significant budget. What should the business analyst do?

A.Record the conflict in the issues log and proceed with the project as planned, noting the risk in the risk register.

B.Document the conflict and escalate to the steering committee for a decision on how to resolve the inconsistency.

C.Update the business case to align the project's objectives with the new requirements, justifying the deviation from the strategic goal.

D.Ignore the conflict because the sponsor has the authority to make decisions, and the project has already been approved.

AnswerB

The sponsor cannot unilaterally override an approved strategic objective, so the analyst documents the sustainability conflict and escalates it to the steering committee, which owns such cross-cutting decisions. This preserves the analyst's objectivity and gives governance authority the evidence to resolve the inconsistency.

Why this answer

The business analyst has a duty to escalate unresolved conflicts that threaten strategic alignment. Recording the conflict and escalating to the steering committee ensures that decision-makers with broader authority can resolve the issue. Updating the business case to align with requirements would be unethical if it contradicts strategy.

Proceeding without action ignores the conflict, and ignoring it violates professional responsibility.

Practice this question →

2

MCQeasy

A business analyst is working on a project to replace a legacy customer relationship management (CRM) system. The project manager asks the BA to ensure that all requirements are aligned with the organization's strategic goals. Which of the following best describes the purpose of tracing requirements to business objectives?

A.To estimate the cost and effort required to implement each requirement

B.To document the technical specifications for how each requirement will be built

C.To assign each requirement to a specific project team member for implementation

D.To validate that each requirement delivers value and supports the business case

AnswerD

Tracing requirements to business objectives ensures that every requirement contributes to the strategic goals and the business case. This alignment helps prioritize requirements and prevents scope creep by identifying requirements that do not add value. In this scenario, the BA can use tracing to confirm that CRM requirements support the organization's goals, such as improving customer retention or increasing sales.

Why this answer

Tracing requirements to business objectives ensures that the project delivers value and supports the business case. It helps the BA prioritize requirements and avoid unnecessary work. In the CRM replacement scenario, this traceability confirms that each requirement contributes to strategic goals, such as improved customer service or increased revenue, rather than just technical functionality.

Exam trap

The trap here is confusing requirements traceability with task assignment or technical design, when its core purpose is to ensure alignment with business goals.

Practice this question →

3

MCQmedium

A business analyst is introducing a formal business analysis framework to an organization that has previously operated without one. The project manager asks why such a framework is needed. What is the primary benefit of using a business analysis framework?

A.It guarantees faster project delivery

B.It provides a structured approach to business analysis

C.It is only useful for large-scale projects

D.It eliminates the need for stakeholder communication

AnswerB

A framework supplies repeatable phases, tasks and deliverables, so analysis is performed consistently rather than ad hoc. This structured approach directly addresses the organisation's lack of an existing framework, giving the project manager a defined, governable method for eliciting, documenting and managing requirements across the lifecycle.

Why this answer

The primary benefit of a business analysis framework is that it provides a structured approach to business analysis, ensuring consistent processes, deliverables, and governance across projects. It does not guarantee faster delivery, is not limited to large projects, and does not eliminate the need for stakeholder communication. The framework standardizes how requirements are elicited, analyzed, documented, and managed.

Exam trap

CAPM often tests the purpose of frameworks by offering absolute claims (guarantees faster delivery, only for large projects, eliminates communication), so candidates who pick an absolute benefit instead of the structured-approach benefit fall for the overstatement trap.

How to eliminate wrong answers

Option A is wrong because a framework provides structure and consistency, not a guarantee of faster project delivery; speed depends on many factors including scope, resources, and organizational maturity. Option C is wrong because a business analysis framework is scalable and applicable to projects of all sizes, not only large-scale ones. Option D is wrong because stakeholder communication remains essential regardless of the framework; the framework actually emphasizes stakeholder engagement as a core practice.

Practice this question →

4

MCQmedium

During a project, a stakeholder requests a change that adds new functionality. The BA determines the change is feasible but will delay the schedule. What should the BA do first?

A.Document the impact in the change request

B.Reject the change

C.Approve the change

D.Implement the change

AnswerA

Documenting the impact in the change request captures the schedule delay, cost and benefit implications before any decision. This satisfies the stem's constraint that the change is feasible but delays the schedule, giving the change control board accurate information to approve, defer or reject.

Why this answer

When a change is feasible but impacts the schedule, the BA's first step is to document the impact in the change request so the change control board (or sponsor) can make an informed decision. Approving, rejecting, or implementing the change are decisions that belong to the change control process, not to the BA acting alone. Documenting the impact preserves the audit trail and enables proper evaluation.

Exam trap

CAPM often tests the sequence of change control — candidates see 'feasible' and jump to approve or implement, forgetting that documentation and impact analysis must precede any decision, and that the BA lacks approval authority.

How to eliminate wrong answers

Option B is wrong because the BA does not have the authority to unilaterally reject a change — rejection is a decision made by the change control board or sponsor after reviewing the documented impact. Option C is wrong because approval authority rests with the change control board or project sponsor, not the BA, and approving without documenting the impact violates change control governance. Option D is wrong because implementing the change before it has been reviewed and approved bypasses the integrated change control process and creates unauthorized scope creep.

Practice this question →

5

Multi-Selecthard

Which THREE of the following are techniques commonly used in business analysis frameworks to elicit requirements?

Select 3 answers

A.Prototyping

B.Interviews

C.SWOT analysis

D.Critical path method

E.Document analysis

AnswersA, B, E

Prototyping builds a partial working model so stakeholders react to something concrete rather than abstract descriptions, surfacing requirements they cannot articulate verbally. This iterative feedback loop is a recognised elicitation technique in business analysis frameworks such as BABOK.

Why this answer

Prototyping (A) is a recognized elicitation technique in business analysis frameworks such as the IIBA BABOK, where a mock-up or working model is shown to stakeholders to draw out and refine requirements that are hard to articulate in the abstract. Interviews (B) are a core elicitation method in which the analyst asks stakeholders structured or unstructured questions to uncover needs, expectations, and constraints directly. Document analysis (E), also called document review, is an elicitation technique that examines existing business documents, policies, system specs, and reports to derive requirements and identify gaps.

SWOT analysis (C) is a strategic planning tool for assessing strengths, weaknesses, opportunities, and threats, not a requirements elicitation technique. The critical path method (D) is a project scheduling technique used to determine the longest sequence of dependent tasks and float, so it does not elicit requirements.

Exam trap

The trap here is that candidates may confuse strategic analysis tools (like SWOT) or project scheduling tools (like critical path method) with requirements elicitation techniques, which are specifically designed to gather information from stakeholders.

Practice this question →

6

Multi-Selecthard

Which THREE elements are typically included in a project business case?

Select 3 answers

A.Risk assessment

B.Stakeholder register

C.Alternatives analysis

D.Project charter

E.Cost-benefit analysis

AnswersA, C, E

A business case documents the risk assessment, identifying uncertainties and their potential effect on benefits, costs and schedule. This satisfies the stem's requirement for a typical element, since decision-makers need this analysis to judge whether the expected value justifies proceeding with the proposed project.

Why this answer

A business case typically includes a risk assessment (A), because decision-makers need to understand the uncertainties, threats, and potential negative outcomes that could affect the expected value of the proposed investment. It also includes an alternatives analysis (C), which documents the options considered (e.g., build vs. buy vs. do nothing) and justifies why the recommended solution was selected over the others. A cost-benefit analysis (E) is also a core element, quantifying expected costs, benefits, ROI, NPV, or payback period to demonstrate the financial viability of the initiative.

The stakeholder register (B) is a project stakeholder management artifact produced during project initiation or planning, not a component of the business case itself. The project charter (D) is a separate authorization document that formally initiates the project and is created after, and often based on, the approved business case.

Exam trap

CAPM often tests the boundary between the business case and adjacent initiation documents (charter, stakeholder register), so candidates include artifacts that are inputs to or outputs of the business case rather than its actual components.

Practice this question →

7

MCQmedium

A BA is conducting stakeholder analysis and needs to categorize stakeholders based on their influence and interest. Which grid is commonly used?

A.Communication matrix

B.Decision tree

C.RACI matrix

D.Power/interest grid

AnswerD

The power/interest grid plots stakeholders by authority over the project and their level of concern, producing tailored engagement strategies for each quadrant. It directly satisfies the stem's requirement to categorise stakeholders by influence and interest.

Why this answer

The power/interest grid is a stakeholder analysis tool that categorizes stakeholders based on their level of authority (power) and concern (interest) in the project. It helps determine engagement strategies, such as managing closely those with high power and high interest. This grid is commonly used in business analysis and project management to prioritize stakeholder communication.

Exam trap

The trap is confusing the power/interest grid with other stakeholder tools like the RACI matrix or communication matrix; candidates may pick RACI because it also involves stakeholders, but it serves a different purpose.

How to eliminate wrong answers

Option A is wrong because a communication matrix outlines who needs what information, when, and how, but does not categorize stakeholders by influence and interest. Option B is wrong because a decision tree is a graphical tool for decision analysis under uncertainty, not stakeholder categorization. Option C is wrong because a RACI matrix assigns roles (Responsible, Accountable, Consulted, Informed) for tasks, not for analyzing stakeholder influence and interest.

Practice this question →

8

MCQhard

A mid-sized insurance company is implementing a new claims management system using a traditional waterfall approach. The business analyst (BA) spent three months gathering and documenting detailed requirements, which were signed off by stakeholders. However, during the development phase, the claims processing team requests frequent changes due to evolving regulatory requirements and customer feedback. The project manager is concerned about scope creep and budget overruns. The development team is frustrated because rework is affecting their velocity. The BA needs to recommend an approach that balances flexibility with control. The organization has limited experience with agile methods but is open to change. The BA should recommend:

A.Adopt a hybrid approach that retains the high-level scope from the waterfall document but uses iterative cycles with rolling wave planning for detailed requirements

B.Switch to a pure agile framework using user stories and a product backlog, abandoning the existing detailed requirements

C.Document every change request and ask the project sponsor for a budget increase to cover all rework

D.Continue with the waterfall approach but establish a strict change control board to evaluate all requests

AnswerA

A hybrid approach keeps the signed-off high-level scope under change control while iterative cycles with rolling wave planning absorb evolving regulatory detail. This satisfies the stem's constraint of balancing flexibility with control given limited agile experience, avoiding full waterfall rigidity or unmanaged scope creep.

Why this answer

It balances the need for flexibility with control by retaining the high-level scope from the signed-off waterfall document while using iterative cycles and rolling wave planning to detail requirements as the project progresses. This hybrid approach accommodates evolving regulatory requirements and customer feedback without abandoning the existing investment in requirements, and it mitigates scope creep by keeping the overall scope fixed while allowing detailed adjustments in short cycles.

Exam trap

The trap here is that candidates often assume that any change from waterfall must mean a full switch to agile (Option B), but the CAPM exam tests the ability to recognize hybrid approaches as a practical compromise that leverages existing artifacts while introducing iterative flexibility.

How to eliminate wrong answers

Option B is wrong because switching to a pure agile framework and abandoning the existing detailed requirements would waste the three months of effort and likely cause confusion, as the organization has limited agile experience and the signed-off scope provides a necessary baseline for regulatory compliance. Option C is wrong because simply documenting every change request and asking for a budget increase does not address the root cause of frequent changes or provide a process to manage them proactively; it only reacts to scope creep without improving flexibility or control. Option D is wrong because continuing with a strict waterfall approach and a change control board would slow down responses to evolving regulatory requirements and customer feedback, leading to further frustration and rework without the iterative flexibility needed.

Practice this question →

9

MCQhard

A business analyst is using a requirements traceability matrix. A test case failure reveals that requirement REQ-007 was not implemented correctly. What does the RTM help the BA identify?

A.The priority of the requirement

B.The source of the requirement

C.The related design and test artifacts

D.The stakeholder who approved it

AnswerC

A requirements traceability matrix links each requirement to its originating need and to downstream design, development and test artifacts. When REQ-007 fails, the RTM reveals the associated design components and test cases, enabling targeted impact analysis and correction.

Why this answer

A requirements traceability matrix (RTM) links requirements to their source, design artifacts, test cases, and other deliverables, providing bidirectional traceability. When a test case fails, the RTM helps the business analyst trace from the test case back to the related design and requirement to identify where the implementation went wrong. This is the primary purpose of the RTM in verification and validation.

Exam trap

CAPM often tests the RTM by offering attributes like priority or source as answers, catching candidates who confuse the matrix's traceability function with general requirement metadata.

How to eliminate wrong answers

Option A is wrong because priority is an attribute of the requirement, not a traceability link that helps diagnose implementation failures. Option B is wrong because the source of the requirement (e.g., stakeholder or business need) is one traceability link, but it does not directly help identify the design or test artifacts affected by a failure. Option D is wrong because the approver is a metadata attribute, not a traceability relationship that aids in diagnosing a test failure.

Practice this question →

10

MCQeasy

A project team is identifying the business need for a new system. Which business analysis activity should be performed first?

A.Conduct a needs assessment

B.Validate requirements

C.Elicit requirements

D.Define solution scope

AnswerA

A needs assessment precedes all other business analysis work, establishing the current-state problems, gaps and desired outcomes before requirements are elicited. Conducting it first satisfies the stem's constraint that the initial activity must define the business need driving the new system.

Why this answer

A needs assessment is the foundational business analysis activity that identifies and defines the business problem or opportunity before any solution work begins. It establishes why the project exists, what business goals must be met, and what the gap is between current and desired state. All other activities — elicitation, validation, and solution scope definition — depend on the needs assessment output.

Exam trap

CAPM often tests the sequencing of business analysis activities, and candidates frequently confuse elicitation (gathering requirements) with needs assessment (defining the problem), picking elicitation because it sounds like the natural 'first step' in requirements work.

How to eliminate wrong answers

Option B is wrong because validating requirements occurs after requirements have been elicited and documented; you cannot validate what has not yet been defined. Option C is wrong because eliciting requirements is a downstream activity that requires the business need and context to be understood first — elicitation without a defined need produces unfocused, potentially irrelevant requirements. Option D is wrong because defining solution scope presupposes that the business need has been identified and analyzed; scope definition translates the need into boundaries of what the solution will and will not address.

Practice this question →

11

MCQeasy

A business analyst is creating a model to represent the flow of data between external entities and the system. The goal is to show the inputs, outputs, and storage of data without focusing on the internal processing logic. Which business analysis technique should the BA use?

A.State diagram

B.Use case diagram

C.Entity relationship diagram

D.Data flow diagram

AnswerD

A data flow diagram (DFD) visually represents the flow of data within a system, showing external entities, processes, data stores, and data flows. It focuses on data movement and transformation, not on internal processing logic, making it ideal for this scenario.

Why this answer

A data flow diagram is specifically designed to depict how data moves through a system, including external entities, processes, data stores, and data flows. It abstracts away internal processing logic and focuses on data inputs, outputs, and storage, which aligns exactly with the business analyst's goal.

Exam trap

The trap here is confusing data modeling diagrams like entity relationship diagrams with process modeling diagrams like data flow diagrams, even though they serve different purposes.

Practice this question →

12

MCQmedium

A project manager is initiating a project to develop a new mobile application. The business environment is highly uncertain, and requirements are expected to evolve frequently. Which business analysis framework is most appropriate for this scenario?

A.Waterfall

B.PRINCE2

C.Six Sigma

D.Agile (Scrum)

AnswerD

Agile (Scrum) suits volatile requirements through iterative sprints, delivering working increments every two to four weeks so feedback reshapes the backlog continuously. This directly satisfies the stem's highly uncertain environment and frequently evolving requirements, which predictive frameworks cannot accommodate without costly change control.

Why this answer

Agile (Scrum) is the most appropriate framework for a project with high uncertainty and evolving requirements because it embraces change through iterative development and frequent feedback. Scrum's empirical approach allows the team to adapt to new requirements at the end of each sprint, delivering value incrementally. Waterfall, PRINCE2, and Six Sigma are more predictive or process-oriented and do not handle frequent changes well.

Therefore, Agile (Scrum) is the best fit.

Exam trap

CAPM often tests the misconception that any structured framework like PRINCE2 can handle uncertainty, but Agile (Scrum) is specifically designed for evolving requirements.

How to eliminate wrong answers

Option A is wrong because Waterfall is a linear, sequential approach that assumes requirements are stable and known upfront, making it unsuitable for highly uncertain environments. Option B is wrong because PRINCE2 is a structured project management method that, while it can be tailored, is not inherently iterative and does not emphasize frequent adaptation to changing requirements as Agile does. Option C is wrong because Six Sigma is a data-driven methodology focused on reducing defects and variation in processes, not on managing evolving software requirements.

Practice this question →

13

MCQmedium

A business analyst is facilitating a requirements workshop for a new customer relationship management (CRM) system. Several stakeholders from sales, marketing, and customer support are present. The BA wants to generate a large number of ideas quickly, encourage creativity, and avoid early criticism. Which technique is most appropriate?

A.Brainstorming

B.Nominal group technique

C.Focus groups

D.Delphi technique

AnswerA

Brainstorming is designed to produce a high volume of creative ideas in a short time while suspending judgment. In this workshop, it lets sales, marketing, and support contributors propose CRM features freely. The BA captures all ideas without debate, then later groups and evaluates them. This matches the goal of rapid idea generation and reduced criticism during divergent thinking.

Why this answer

Brainstorming is the best fit because it deliberately separates idea generation from evaluation, allowing a diverse group to produce many CRM feature ideas quickly. The other techniques either require anonymity and multiple rounds, impose silent writing and voting, or focus on perceptions rather than generating a broad set of requirements ideas.

Exam trap

The trap here is assuming any group discussion technique generates ideas rapidly, when structured techniques like Delphi or nominal group technique actually trade speed for consensus or reduced bias.

Practice this question →

14

MCQhard

You are a business analyst for a large retail company implementing a new inventory management system. The project uses a waterfall business analysis framework. During the requirements phase, you have completed stakeholder analysis, conducted interviews, and documented functional requirements. Now, during requirements validation, the warehouse manager (a key stakeholder) states that the system must support real-time inventory updates from handheld scanners, a requirement not previously mentioned. The project manager is concerned because this requirement could impact the budget and schedule, and the design phase is scheduled to begin next week. You have a requirements prioritization meeting tomorrow. The warehouse manager insists this is critical for operations. The project sponsor expects all requirements to be finalized before design. What is the best course of action?

A.Immediately escalate to the project sponsor to decide whether to include the requirement.

B.Add the requirement to the requirements document and adjust the project plan accordingly.

C.Analyze the impact of the requirement on cost, schedule, and scope, and present options at the prioritization meeting.

D.Reject the requirement because it was not identified during elicitation and will delay the project.

AnswerC

Analysing cost, schedule and scope impact and presenting options at the prioritisation meeting satisfies the sponsor's requirement that requirements be finalised before design, while giving stakeholders evidence to decide the late requirement's fate. Proceeding directly to design would breach the waterfall phase gate.

Why this answer

As a business analyst following a waterfall framework, you must analyze the impact of a new requirement on cost, schedule, and scope before making decisions. Presenting this analysis at the prioritization meeting allows stakeholders to make an informed trade-off decision, aligning with the project sponsor's expectation that requirements are finalized before design begins. This approach maintains the integrity of the requirements validation process without prematurely escalating or rejecting the requirement.

Exam trap

The trap here is that candidates may assume any late requirement must be immediately rejected or escalated, but the CAPM exam tests the correct process of analyzing impact and presenting options to stakeholders for prioritization.

How to eliminate wrong answers

Option A is wrong because immediately escalating to the sponsor bypasses the structured prioritization meeting and the business analyst's role to provide impact analysis, which is essential for informed decision-making. Option B is wrong because adding the requirement and adjusting the plan without analyzing its impact violates the waterfall principle of controlled change management and could lead to unapproved scope creep. Option D is wrong because rejecting the requirement outright ignores the stakeholder's legitimate operational need and the business analyst's responsibility to validate and prioritize requirements, even if they emerge late.

Practice this question →

15

Drag & Dropmedium

Drag and drop the steps for creating a work breakdown structure (WBS) in the correct order.

Drag or tap steps into the slots.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

Why this order

The WBS is built by identifying deliverables, decomposing them, structuring hierarchically, coding elements, and verifying completeness.

Practice this question →

16

MCQhard

A business analyst has developed a working prototype for a new user interface. The prototype is used to demonstrate the workflow to stakeholders and gather feedback. Which type of requirements validation does this represent?

A.Validation

B.Quality assurance

C.Peer review

D.Verification

AnswerA

Validation confirms the built product meets stakeholder needs and intended use. Demonstrating a working prototype to stakeholders and gathering their feedback tests whether the artefact is fit for purpose, which is validation rather than verification against specifications.

Why this answer

Validation confirms that the product meets the intended use and stakeholder needs — building the right product. Demonstrating a working prototype to stakeholders to gather feedback is a classic validation activity because it checks whether the requirements actually solve the business problem. Verification, by contrast, checks that the product was built correctly according to specifications.

Exam trap

The trap is confusing verification with validation — candidates see 'prototype' and think 'testing,' but the key phrase is 'gather feedback from stakeholders,' which is validation (right product), not verification (product built right).

How to eliminate wrong answers

Option B is wrong because quality assurance is a broader process-oriented discipline (defining standards, processes, and audits) rather than the specific act of confirming stakeholder needs through a prototype. Option C is wrong because peer review is a static inspection technique performed by colleagues on documents or code, not an interactive stakeholder demonstration. Option D is wrong because verification confirms the product was built correctly per the specification (e.g., 'did we build the product right?'), whereas the prototype demo is about confirming the right product was built — that is validation.

Practice this question →

17

MCQmedium

A business analyst is developing a business case for a proposed IT system. Which component should be included to evaluate the financial viability?

A.Requirements traceability matrix

B.Stakeholder register

C.Cost-benefit analysis

D.Work breakdown structure

AnswerC

A cost-benefit analysis quantifies expected costs against projected benefits, yielding metrics such as net present value, ROI and payback period. This directly satisfies the stem's requirement to evaluate the proposed IT system's financial viability within the business case.

Why this answer

Cost-benefit analysis compares the costs and benefits to determine financial viability. Option A is incorrect because requirements traceability matrix links requirements, not financials. Option B is incorrect because stakeholder register identifies stakeholders, not financials.

Option D is incorrect because WBS decomposes work.

Practice this question →

18

MCQeasy

Which document serves as the primary source for defining the product scope?

A.Stakeholder register

B.Requirements documentation

C.Project charter

D.Business case

AnswerB

Requirements documentation captures the agreed needs, features and constraints the product must satisfy, making it the primary source for defining product scope. The project charter authorises the project and states high-level scope, but detailed product boundaries derive from documented requirements.

Why this answer

Requirements documentation contains detailed product requirements that define the product scope. Option A is wrong because the stakeholder register lists stakeholders, not scope. Option C is wrong because the project charter provides high-level scope but not detailed product scope.

Option D is wrong because the business case justifies the project but does not define scope.

Practice this question →

19

MCQhard

A project team is evaluating a proposed solution that reduces operating costs by $200,000 annually but requires an initial investment of $800,000. The project lifespan is 5 years and the discount rate is 8%. What is the net present value (NPV) of this solution? (Assume annual cost savings occur at year-end.)

A.$20,000

B.-$20,000

C.-$1,458

D.$200,000

AnswerC

Discounting $200,000 annually at 8% over five years gives a present value of approximately $798,542. Subtracting the $800,000 initial investment yields an NPV of about -$1,458, confirming the solution destroys value at this discount rate.

Why this answer

NPV is calculated by discounting each year's $200,000 savings at 8% over 5 years and subtracting the $800,000 initial investment. The present value annuity factor for 8% over 5 years is approximately 3.9927, giving PV of savings ≈ $798,542. Subtracting the $800,000 investment yields NPV ≈ -$1,458, so the project destroys value at this discount rate.

Exam trap

The trap is forgetting to discount future cash flows — candidates who simply multiply $200,000 × 5 and subtract $800,000 get $200,000 and pick the wrong answer, ignoring the time value of money.

How to eliminate wrong answers

Option A is wrong because $20,000 ignores the time value of money — it appears to be a rough undiscounted estimate (5 × $200,000 = $1,000,000 minus $800,000 = $200,000, then perhaps divided incorrectly), but proper discounting yields a negative NPV. Option B is wrong because -$20,000 does not match the precise discounted calculation; it may result from using a simple approximation rather than the exact annuity factor. Option D is wrong because $200,000 is the annual savings, not the NPV — it confuses a cash flow figure with the net present value result.

Practice this question →

20

MCQhard

A BA is analyzing the cost-benefit analysis for a project and finds that the net present value (NPV) is negative. What does this indicate?

A.The project is financially viable.

B.The costs exceed the benefits over the project's life.

C.The benefits outweigh the costs.

D.The payback period is short.

AnswerB

A negative net present value means discounted future cash inflows are worth less than the initial and ongoing outflows, so total costs exceed total benefits across the project's life. The project therefore destroys value at the required rate of return and should not proceed as analysed.

Why this answer

A negative Net Present Value means that, after discounting all future cash inflows and outflows back to present value using the required rate of return, the project's costs exceed its benefits. In other words, the project would destroy value rather than create it, so it should generally be rejected unless non-financial strategic factors override the analysis.

Exam trap

CAPM often tests the confusion between NPV and payback period — candidates see 'costs exceed benefits' and second-guess themselves because they conflate discounted NPV with undiscounted cash-flow totals or recovery time.

How to eliminate wrong answers

Option A is wrong because a negative NPV is the textbook signal of financial non-viability, not viability — a viable project has NPV greater than zero. Option C is wrong because if benefits outweighed costs, NPV would be positive; a negative NPV directly contradicts this. Option D is wrong because payback period is a separate, non-discounted metric that measures how quickly the initial investment is recovered — it says nothing about NPV, and a short payback period can coexist with a negative NPV.

Practice this question →

21

Multi-Selecteasy

Which TWO of the following are commonly used techniques for requirements prioritization?

Select 2 answers

A.Kano

B.SWOT

C.Fishbone

D.MoSCoW

E.Risk Register

AnswersA, D

The Kano model classifies requirements by their effect on customer satisfaction, distinguishing basic, performance, delighter, indifferent and reverse attributes. It satisfies the stem's prioritisation requirement by revealing which features disproportionately raise satisfaction versus merely avoiding dissatisfaction.

Why this answer

Kano analysis categorizes features based on how they affect customer satisfaction (basic, performance, excitement) to prioritize by impact. MoSCoW (Must have, Should have, Could have, Won't have) classifies requirements by necessity and stakeholder agreement. Both are standard prioritization techniques in business analysis for the CAPM exam.

Exam trap

PMI often tests the distinction between tools used for analysis versus prioritization, so candidates may confuse SWOT (a strategic analysis tool) or Fishbone (a root cause analysis tool) as valid prioritization techniques because they are also used in business analysis contexts.

Practice this question →

22

Multi-Selecthard

Which THREE of the following are commonly used techniques for requirements elicitation?

Select 3 answers

A.Earned value management

B.Interviews

C.Brainstorming

D.Observation

E.SWOT analysis

AnswersB, C, D

Interviews are a direct way to gather requirements from stakeholders.

Why this answer

Interviews are a direct, one-on-one technique used to elicit requirements from stakeholders by asking structured or unstructured questions. They allow the business analyst to probe deeply into stakeholder needs, clarify ambiguities, and uncover implicit requirements that might not surface in group settings.

Exam trap

PMI often tests the distinction between project management tools (like EVM) and business analysis elicitation techniques, leading candidates to confuse performance measurement with requirements gathering.

Practice this question →

23

MCQmedium

A business analyst is working on a project to replace a legacy billing system. The project sponsor wants to ensure that the new system meets the needs of the finance department. Which technique should the business analyst use to understand the detailed steps and decision points in the current billing process?

A.Data modeling

B.Interface analysis

C.Document analysis

D.Process modeling

AnswerD

Process modeling visually represents the sequence of activities, decision points, inputs, and outputs of a business process. It helps the business analyst capture the current state of the billing process, identify inefficiencies, and communicate requirements for the future state. This technique is specifically designed to analyze workflows and decision logic.

Why this answer

Process modeling is the most appropriate technique because it explicitly captures the flow of activities, decision points, and roles involved in the billing process. It allows the business analyst to document the current state and define the future state, ensuring that the new system supports the finance department's operational needs. This visual representation also facilitates stakeholder validation and identification of gaps.

Exam trap

The trap here is confusing data modeling with process modeling, because both are analytical techniques, but only process modeling addresses the sequence of activities and decision logic.

Practice this question →

24

MCQmedium

During the requirements elicitation for a new software system, the business analyst (BA) conducts a series of interviews with stakeholders. After the first interview, the BA realizes that the questions are too technical and the stakeholders are struggling to provide clear requirements. What should the BA do to improve the elicitation process?

A.Continue with the same questions but provide a glossary of technical terms.

B.Revise the interview questions to be more open-ended and focus on business outcomes.

C.Replace interviews with a review of existing documentation.

D.Reduce the number of stakeholders to only those with technical backgrounds.

AnswerB

Revising questions to be open-ended and outcome-focused shifts elicitation from technical detail to business need, which is precisely the constraint the stem identifies: stakeholders cannot articulate requirements when questioned technically. Open-ended prompts let them describe goals and value in their own language, yielding clearer, more complete requirements.

Why this answer

The BA's questions are too technical, causing stakeholders to focus on implementation details rather than their actual needs. By revising questions to be open-ended and focused on business outcomes, the BA shifts the conversation from 'how the system should work' to 'what business problem needs to be solved,' which is the core of effective requirements elicitation. This approach aligns with the BABOK's principle of understanding stakeholder needs before defining technical solutions.

Exam trap

The trap here is that candidates often assume providing a glossary (Option A) is sufficient to bridge the technical gap, but the CAPM exam tests the deeper principle that the BA must adapt the elicitation technique itself to match the stakeholder's language and perspective, not just translate terms.

How to eliminate wrong answers

Option A is wrong because providing a glossary of technical terms does not address the root issue—the questions themselves are too technical, forcing stakeholders to think in terms of system features rather than business goals; a glossary only patches the symptom. Option C is wrong because replacing interviews with documentation review abandons direct stakeholder interaction, which is essential for capturing tacit knowledge, context, and unspoken requirements that documents cannot convey. Option D is wrong because reducing stakeholders to only those with technical backgrounds eliminates the very business and end-user perspectives needed to define correct requirements, violating the principle of involving all relevant stakeholder groups.

Practice this question →

25

MCQeasy

A business analyst is creating a requirements traceability matrix (RTM) for a project. Which of the following is the primary purpose of an RTM?

A.To document the final version of requirements after project closure.

B.To assign requirements to specific team members.

C.To track requirements from identification through delivery and testing.

D.To estimate the cost of each requirement.

AnswerC

An RTM provides bidirectional linkage, mapping each requirement to its source, design, build and test artefacts. This satisfies the stem's need to track requirements from identification through delivery and testing, exposing gaps, gold-plating and unverified scope across the project lifecycle.

Why this answer

The primary purpose of a Requirements Traceability Matrix (RTM) is to link each requirement from its origin through the entire project lifecycle, including design, development, testing, and delivery. Option C correctly identifies this end-to-end traceability function, which ensures that every requirement is accounted for and validated against test cases and deliverables.

Exam trap

PMI often tests the misconception that the RTM is used for resource assignment or cost tracking, leading candidates to confuse it with other project documents like the WBS or cost management plan.

How to eliminate wrong answers

Option A is wrong because the RTM is a living document maintained throughout the project, not a post-closure archive; it tracks requirements in real time, not just the final version. Option B is wrong because assigning requirements to team members is a function of a work breakdown structure (WBS) or resource assignment matrix, not the RTM, which focuses on traceability rather than ownership. Option D is wrong because cost estimation is performed using techniques like analogous or parametric estimation, not the RTM, which does not capture financial data or cost breakdowns.

Practice this question →

26

MCQeasy

A business analyst is creating a model to represent the flow of data between external entities, processes, and data stores for a new payroll system. The BA needs to show how data moves through the system and what transformations occur. Which model is most suitable?

A.State machine diagram

B.Data flow diagram (DFD)

C.Entity-relationship diagram (ERD)

D.Use case diagram

AnswerB

A data flow diagram (DFD) graphically represents the flow of data through a system, including external entities, processes, data stores, and data flows. It is specifically designed to show how data moves, where it is transformed, and where it is stored. In this scenario, the BA needs to depict the payroll system's data movement and transformations, making a DFD the most suitable model. DFDs are a core technique for documenting functional requirements.

Why this answer

A data flow diagram is the correct model because it explicitly depicts the movement of data between external entities, processes, and data stores, and shows how data is transformed. It provides a clear, hierarchical view of data flow that is essential for understanding and documenting functional requirements. Other models like ERDs, use case diagrams, and state machine diagrams serve different purposes and cannot adequately represent data flow and transformation.

Exam trap

The trap here is confusing a data flow diagram with an entity-relationship diagram, as both deal with data, but only the DFD shows the flow and transformation of data through processes.

Practice this question →

27

MCQeasy

A business analyst needs to gather input from a large number of geographically dispersed stakeholders about their preferences for a new system. The project has a limited budget and timeline. Which elicitation technique is most efficient in this scenario?

A.Focus groups

B.One-on-one interviews

C.Survey / Questionnaire

D.Observation

AnswerC

Surveys reach many dispersed stakeholders simultaneously at minimal cost, satisfying the limited budget and timeline constraint. Responses are collected asynchronously, avoiding travel and scheduling overhead that workshops, interviews or focus groups would impose across multiple locations.

Why this answer

A survey or questionnaire is the most efficient elicitation technique when gathering input from many geographically dispersed stakeholders under budget and time constraints, because it can be distributed simultaneously to all participants at minimal cost and requires no travel or scheduling coordination. It scales linearly in cost per additional respondent, unlike interviews or focus groups.

Exam trap

CAPM often tests technique selection by scenario constraints — the trap is ignoring the 'geographically dispersed' and 'limited budget' cues and picking interviews or focus groups for their qualitative richness.

How to eliminate wrong answers

Option A is wrong because focus groups require assembling participants in one place or time, which is impractical and costly for geographically dispersed stakeholders. Option B is wrong because one-on-one interviews are time-intensive and expensive, scaling poorly to a large stakeholder group. Option D is wrong because observation requires the analyst to be physically present and is used to understand workflows, not to collect stated preferences from many people.

Practice this question →

28

MCQmedium

A business analyst is conducting a stakeholder analysis and discovers that a key stakeholder has high power but low interest in the project. According to the Power/Interest Grid, what is the recommended engagement strategy for this stakeholder?

A.Manage closely

B.Keep satisfied

C.Monitor

D.Keep informed

AnswerB

High power with low interest maps to the Keep Satisfied quadrant, so the analyst engages enough to prevent the stakeholder blocking the project without overloading them with detail. This matches the grid's prescribed strategy for that power/interest combination.

Why this answer

The Keep Satisfied strategy is recommended for stakeholders with high power and low interest to ensure their needs are met without over-engagement.

Practice this question →

29

MCQhard

A business analyst is facilitating a workshop to define the scope of a new customer relationship management (CRM) system. The project manager insists on including a feature that automates email campaigns, but the BA has identified that this feature is outside the agreed budget and timeline. The product owner supports the feature because it was requested by a key customer. What should the BA do first?

A.Facilitate a prioritization session with all stakeholders to discuss trade-offs.

B.Reject the feature because it exceeds the budget.

C.Add the feature to the backlog but flag it as out of scope.

D.Request a budget increase from the project sponsor.

AnswerA

Prioritisation with all stakeholders exposes the budget and timeline trade-offs, letting the group decide whether the email automation feature displaces other scope. This directly addresses the constraint conflict between the project manager, product owner and agreed baseline before any scope change is accepted.

Why this answer

The BA should first facilitate a prioritization session with all stakeholders to discuss trade-offs because this aligns with the business analysis framework's emphasis on collaborative decision-making when scope conflicts arise. By engaging stakeholders, the BA can evaluate the feature's value against budget and timeline constraints, ensuring informed trade-offs rather than unilateral rejection or escalation. This approach maintains stakeholder alignment and avoids premature scope changes without consensus.

Exam trap

The trap here is that candidates may assume the BA should immediately escalate or reject out-of-scope features, but the CAPM exam tests the BA's role as a neutral facilitator who first seeks consensus through prioritization before taking unilateral actions.

How to eliminate wrong answers

Option B is wrong because rejecting the feature outright without stakeholder input violates the BA's role as a facilitator and ignores the product owner's justification of customer demand, which could lead to missed business value. Option C is wrong because adding the feature to the backlog without addressing the budget and timeline impact creates scope creep and undermines the agreed constraints, as the BA should first resolve the conflict through prioritization. Option D is wrong because requesting a budget increase is premature without first exploring trade-offs or reprioritizing existing features, which could avoid unnecessary financial escalation.

Practice this question →

30

MCQeasy

In an Agile framework, when should the business analyst perform backlog refinement?

A.During the sprint review

B.Only when requested by the product owner

C.Only at the start

D.Continuously throughout the project

AnswerD

Backlog refinement is an ongoing, continuous activity in Agile, not a phase-gated event. Performing it throughout the project keeps the backlog ordered, estimated and ready for upcoming sprints, directly satisfying the stem's Agile framework constraint. This continuous cadence ensures the team always has sufficient refined items to pull into the next iteration.

Why this answer

In Agile frameworks, backlog refinement is an ongoing activity that occurs continuously throughout the project. It involves regularly reviewing and updating the product backlog to ensure items are ready for upcoming sprints. This continuous process allows the team to adapt to changing requirements and maintain a healthy backlog.

The business analyst, as a key stakeholder, should participate in these sessions as needed, not just at specific events like sprint review or only when requested.

Exam trap

CAPM often tests the misconception that backlog refinement is a one-time event or only occurs during specific ceremonies, when in fact it is a continuous activity.

How to eliminate wrong answers

Option A is wrong because backlog refinement is not limited to the sprint review; the sprint review is for inspecting the increment and gathering feedback, not for refining the backlog. Option B is wrong because refinement should be proactive and continuous, not solely triggered by the product owner's requests. Option C is wrong because refinement is not a one-time activity at the start; it must be ongoing to keep the backlog relevant and prioritized.

Practice this question →

31

MCQmedium

Based on the exhibit, which requirement is not yet linked to a test case?

A.None of the above

B.R001

C.R002

D.R003

AnswerA

All requirements have associated test cases.

Why this answer

The exhibit shows that requirements R001, R002, and R003 are each linked to at least one test case. Since all listed requirements already have test case associations, the correct answer is 'None of the above' — no requirement remains unlinked.

Exam trap

The trap here is that candidates may assume a requirement is unlinked if they misread the matrix or overlook a connection arrow, but the exhibit clearly shows each requirement has a corresponding test case.

How to eliminate wrong answers

Option B is wrong because R001 is shown linked to test case TC-001 in the exhibit. Option C is wrong because R002 is linked to test case TC-002. Option D is wrong because R003 is linked to test case TC-003.

Practice this question →

32

Multi-Selecthard

A business analyst is preparing for a requirements review meeting with stakeholders from various departments. The BA wants to ensure the review is effective and that the requirements are validated. Which two actions should the BA take to prepare for the review? (Choose two.)

Select 2 answers

A.Define clear entry and exit criteria for the review, such as requirements being complete and testable.

B.Invite all stakeholders who might be affected by the requirements, regardless of their role.

C.Ask each reviewer to come prepared to defend their departmental requirements against challenges.

D.Distribute the requirements document to reviewers at least two business days before the meeting.

E.Focus the meeting on finding as many defects as possible, even if they are minor.

AnswersA, D

Establishing entry and exit criteria ensures that the review has a clear purpose and measurable outcomes. Entry criteria might include that requirements are documented and internally consistent, while exit criteria might be that all critical issues are resolved or logged. This structure prevents the review from becoming a free-form discussion and helps the BA measure its success. It is a key technique for effective requirements validation.

Why this answer

Effective requirements reviews require preparation. Distributing the document in advance ensures reviewers are ready to engage meaningfully. Defining entry and exit criteria provides structure and measurable goals, preventing the meeting from drifting.

Together, these actions help the BA facilitate a focused, productive review that validates requirements and builds consensus, rather than getting bogged down in logistics or conflict.

Exam trap

The trap here is thinking that inviting everyone affected or encouraging defensive debate leads to a thorough review, when in fact it often causes inefficiency and conflict.

Practice this question →

33

MCQmedium

A project manager is leading a software development project. The business analyst has identified that the current requirements gathering process does not align with the enterprise's business analysis framework. The team is experiencing frequent scope changes and rework. What should the project manager do first to address this issue?

A.Immediately implement a change control process to manage scope changes.

B.Train the business analyst on the project's requirements gathering techniques.

C.Review the enterprise's business analysis framework and adjust the requirements process to comply with it.

D.Update the requirements documentation to include a traceability matrix.

AnswerC

Realigning the requirements process with the enterprise's business analysis framework addresses the root cause of the scope changes and rework. Reviewing the framework and adjusting the process to comply restores consistency with organisational standards before further requirements work proceeds, which is the appropriate first corrective action.

Why this answer

The project manager must first ensure the requirements gathering process aligns with the enterprise's business analysis framework. This alignment is a foundational step to reduce scope changes and rework, as the framework defines standard practices, templates, and governance for requirements management. Without compliance, any change control or documentation updates will be ineffective because the underlying process itself is non-conforming.

Exam trap

The trap here is that candidates often jump to implementing a change control process (Option A) because it directly addresses scope changes, but the CAPM exam tests the principle of first aligning with enterprise standards before applying corrective actions.

How to eliminate wrong answers

Option A is wrong because immediately implementing a change control process treats the symptom (scope changes) without addressing the root cause—the misaligned requirements gathering process. Option B is wrong because training the business analyst on the project's techniques does not resolve the misalignment with the enterprise framework; the process itself must be adjusted to comply with the enterprise standard. Option D is wrong because updating requirements documentation with a traceability matrix is a tactical improvement that does not fix the fundamental process misalignment causing the frequent changes and rework.

Practice this question →

34

MCQmedium

A business analyst is assessing the feasibility of a proposed new online ordering system for a restaurant chain. The BA needs to evaluate whether the system can be developed with the available technology and skills within the organization. Which type of feasibility is the BA primarily assessing?

A.Operational feasibility

B.Legal feasibility

C.Technical feasibility

D.Economic feasibility

AnswerC

Technical feasibility evaluates whether the organization has the technical resources, expertise, and infrastructure to build and maintain the proposed system. The scenario explicitly asks about evaluating technology and skills, which are core aspects of technical feasibility. The BA is assessing if the online ordering system can be developed with current capabilities, making technical feasibility the correct focus.

Why this answer

Technical feasibility is concerned with the organization's ability to develop and support the proposed solution using existing or obtainable technology and skills. Since the BA is evaluating whether the system can be built with available technology and skills, this directly aligns with technical feasibility. Other feasibility types address different aspects, such as financial, operational, or legal considerations, which are not the focus of this scenario.

Exam trap

The trap here is confusing technical feasibility with operational feasibility, which deals with how well the system fits organizational processes and user needs.

Practice this question →

35

MCQmedium

A business analyst is evaluating whether a proposed project aligns with the organization’s strategic goals. Which framework is best suited for this purpose?

A.SWOT Analysis

B.Requirements Traceability Matrix

C.Business Case

D.Stakeholder Register

AnswerC

A business case documents the justification for a project, linking expected benefits, costs and risks directly to strategic objectives. It satisfies the stem's alignment constraint by evidencing how the proposed project delivers organisational goals, giving decision-makers the rationale to approve, reject or reprioritise the investment.

Why this answer

A business case is the document that justifies a project by linking it to organizational strategy, including costs, benefits, risks, and alignment with strategic goals. It is the primary tool for evaluating whether a project aligns with strategic objectives.

Exam trap

CAPM often tests the confusion between tools like SWOT and business case, and candidates may pick SWOT because it sounds strategic, but the business case is the formal document for strategic alignment.

How to eliminate wrong answers

Option A is wrong because SWOT analysis is a strategic planning tool to assess strengths, weaknesses, opportunities, and threats, but it does not directly evaluate project alignment with strategic goals. Option B is wrong because a Requirements Traceability Matrix tracks requirements throughout the project lifecycle, not strategic alignment. Option D is wrong because a Stakeholder Register identifies and documents stakeholders, not strategic fit.

Practice this question →

36

MCQmedium

In a requirements prioritization session, the team uses MoSCoW. A feature that is important but not critical, and could be postponed without major impact, should be classified as:

A.Should have

B.Could have

C.Must have

D.Won't have

AnswerA

MoSCoW's Should-have category covers requirements that are important and valuable but not vital; they can be deferred to a later release without breaking core functionality. This satisfies the stem's constraint of a feature that is postponable without major impact, unlike Must-have items.

Why this answer

In MoSCoW, 'Should have' requirements are important and add significant value but are not critical to the release — they can be worked around or deferred if time or budget runs short. This matches the scenario of a feature that is important but postponable without major impact.

Exam trap

CAPM often tests the fine line between 'Should have' and 'Could have,' catching candidates who equate 'important' with 'critical' and incorrectly choose Must have.

How to eliminate wrong answers

Option B is wrong because 'Could have' represents nice-to-have features with minimal impact if omitted — the scenario describes something more important than that. Option C is wrong because 'Must have' requirements are non-negotiable; without them the release is considered a failure, which contradicts the 'could be postponed' description. Option D is wrong because 'Won't have' means the requirement is explicitly excluded from the current release scope, not merely deferrable.

Practice this question →

37

MCQmedium

You are the business analyst for a project developing a mobile banking application. The project is in the requirements elicitation phase. One of the key stakeholders, the head of security, is on an extended leave and will not be available for three weeks. The project timeline is aggressive, and the project manager insists on completing requirements gathering within two weeks to stay on schedule. You have held initial interviews with other stakeholders, but the security requirements are critical because the app will handle sensitive financial data. The quality assurance lead suggests using a survey to collect security requirements from the security team, but the security team members are reluctant to provide input without their manager's approval. What should you do?

A.Delay all requirements elicitation until the head of security returns to ensure complete and accurate security requirements.

B.Use existing security policies and industry standards as a proxy for the security requirements without further elicitation.

C.Document assumptions about the security requirements and proceed with the rest of the elicitation, planning to validate with the head of security upon their return.

D.Conduct a survey of the security team members to gather their requirements despite their reluctance.

AnswerC

Recording assumptions preserves momentum on the aggressive timeline while flagging the security gap explicitly. The assumptions log documents that security requirements remain unvalidated, and the head of security reviews them on return, satisfying both the two-week deadline and the need for authoritative sign-off on sensitive financial data controls.

Why this answer

The best course of action is to document assumptions about the security requirements and proceed with the rest of the elicitation, planning to validate with the head of security upon their return. This balances the project timeline constraints with the need for security requirements. By documenting assumptions, the business analyst acknowledges the gap and creates a plan to validate later, reducing the risk of rework.

It also allows other elicitation activities to continue, keeping the project on schedule.

Exam trap

CAPM often tests the balance between project constraints and stakeholder availability, leading candidates to choose extreme options like delaying everything or proceeding without validation, rather than a balanced approach with assumptions.

How to eliminate wrong answers

Option A is wrong because delaying all elicitation would jeopardize the project timeline and is unnecessary since other requirements can be gathered. Option B is wrong because using existing policies and standards as a proxy without further elicitation may miss project-specific security needs and does not involve stakeholders. Option D is wrong because conducting a survey despite the team's reluctance could yield incomplete or inaccurate information and may damage stakeholder relationships; it is better to wait for approval or use assumptions.

Practice this question →

38

MCQhard

A business analyst is defining the requirements for a new online banking feature that allows customers to transfer funds between accounts. The security team insists that the feature must comply with multi-factor authentication (MFA) regulations. The marketing team wants to minimize steps to improve user experience. Which type of requirement best describes the MFA compliance mandate?

A.Business requirement

B.Non-functional requirement

C.Functional requirement

D.Transition requirement

AnswerB

Non-functional requirements describe constraints or quality attributes that the system must meet, such as security, performance, or usability. The MFA compliance mandate is a security constraint imposed by regulations, so it is a non-functional requirement. It defines a condition the system must satisfy rather than a specific behavior like transferring funds. In this scenario, the BA must document it as a non-functional requirement to ensure compliance while balancing user experience.

Why this answer

Non-functional requirements specify constraints or quality attributes, such as security, that the system must satisfy. The MFA compliance mandate is a regulatory security constraint, so it is correctly classified as a non-functional requirement. This classification helps the BA ensure that the solution meets compliance while addressing the marketing team's usability concerns separately as other non-functional requirements.

Exam trap

The trap here is misclassifying a security constraint as a functional requirement because it involves authentication, but functional requirements describe behaviors, not constraints.

Practice this question →

39

MCQhard

A business analyst is defining the solution scope for a project to automate a manual approval process. The project sponsor wants to ensure that the solution will meet the business need without including unnecessary features. Which technique should the BA use to clearly define what is in and out of scope for the solution?

A.Data modeling

B.Interface analysis

C.Risk analysis

D.Scope modeling

AnswerD

Scope modeling is a technique used to represent the boundaries of a solution, including what is included and excluded. It helps stakeholders visualize the scope and agree on what the solution will deliver. In this scenario, the sponsor wants to avoid unnecessary features, so scope modeling directly supports defining and communicating the solution boundaries, making it the correct technique.

Why this answer

Scope modeling is the technique designed to define and communicate the boundaries of a solution. It helps stakeholders understand what will be delivered and what will not, preventing scope creep and unnecessary features. Data modeling, interface analysis, and risk analysis serve different purposes and do not directly address the need to establish solution scope.

For the sponsor's goal, scope modeling is the most effective approach.

Exam trap

The trap here is choosing a technique that analyzes a specific aspect of the solution, such as data or interfaces, instead of one that defines the overall solution boundaries.

Practice this question →

40

MCQmedium

A business analyst is facilitating a requirements workshop for a new customer relationship management (CRM) system. Participants include sales representatives, customer service managers, and IT support staff. The BA needs to ensure that all perspectives are captured and that the group reaches a shared understanding of the requirements. Which technique is most appropriate for this purpose?

A.Observation

B.Facilitated workshops

C.Brainstorming

D.Focus groups

AnswerB

Facilitated workshops bring key stakeholders together in a structured session led by a neutral facilitator to define requirements collaboratively. They are specifically designed to build shared understanding, resolve conflicts, and produce a agreed-upon set of requirements. In this scenario, with diverse participants, a facilitated workshop enables cross-functional input and real-time validation, making it the most appropriate technique for capturing all perspectives and reaching consensus.

Why this answer

A facilitated workshop is the most effective technique for bringing together cross-functional stakeholders to elicit, analyze, and agree on requirements. It provides a structured environment where the BA can guide discussions, ensure all voices are heard, and resolve differences in real time. Unlike brainstorming or focus groups, it is explicitly designed to produce a shared deliverable, such as a prioritized requirements list, making it ideal for this scenario.

Exam trap

The trap here is assuming that any group discussion technique, such as brainstorming or focus groups, will automatically lead to consensus and comprehensive requirements, when in fact only a facilitated workshop provides the structured facilitation needed to align diverse stakeholders.

Practice this question →

41

MCQhard

A business analyst is evaluating the performance of a business analysis framework after project completion. Which metric best indicates the effectiveness of the requirements management process?

A.Schedule variance

B.Number of requirements defects found post-implementation

C.Number of requirements traced to test cases

D.Stakeholder satisfaction survey results

AnswerB

Post-implementation requirements defects directly measure how well requirements were elicited, documented and managed, since each defect traces back to a missed, ambiguous or unvalidated requirement. This satisfies the stem's demand for an effectiveness metric by quantifying escaped errors rather than activity volume, giving the analyst concrete evidence of process performance after project completion.

Why this answer

The number of requirements defects found post-implementation directly reflects the quality and completeness of the requirements management process. A high number of defects indicates that requirements were poorly defined, ambiguous, or missed during elicitation and validation, making it the most relevant metric for evaluating the effectiveness of that process.

Exam trap

The trap here is that candidates confuse traceability (Option C) with quality, assuming that if a requirement is traced to a test case, it must be well-managed, but traceability only proves coverage, not correctness or completeness.

How to eliminate wrong answers

Option A is wrong because schedule variance measures project timeline performance (earned value management), not the quality or effectiveness of requirements management. Option C is wrong because the number of requirements traced to test cases indicates traceability coverage, not the correctness or completeness of the requirements themselves; a requirement can be traced but still be defective. Option D is wrong because stakeholder satisfaction survey results are subjective and influenced by many factors beyond requirements quality (e.g., communication, delivery speed), so they are not a precise metric for the requirements management process effectiveness.

Practice this question →

42

MCQhard

A business analyst is using a requirements management tool to store and track requirements. During a review, the BA notices that two stakeholders have conflicting requirements for the same system feature. What is the best approach to resolve this conflict?

A.Choose the requirement from the stakeholder with higher authority.

B.Document both requirements and let the development team decide.

C.Facilitate a meeting with both stakeholders to discuss and reach a consensus.

D.Escalate the conflict to the project sponsor immediately.

AnswerC

Facilitating a meeting lets both stakeholders articulate their needs and negotiate a mutually acceptable resolution, addressing the conflict at its source. The business analyst mediates rather than unilaterally deciding, preserving stakeholder buy-in and ensuring the requirement reflects agreed priorities.

Why this answer

The business analyst's role includes facilitating stakeholder collaboration to resolve conflicts, ensuring that requirements are aligned with business needs. Using a requirements management tool to track conflicting requirements is insufficient; the BA must actively mediate a discussion to reach consensus, as this is a core competency in business analysis frameworks like the BABOK.

Exam trap

The trap here is that candidates may assume escalation or documentation is sufficient, but CAPM emphasizes the BA's role as a facilitator to resolve conflicts through collaboration, not through authority or deferral.

How to eliminate wrong answers

Option A is wrong because choosing based on authority ignores the principle of stakeholder consensus and may lead to unresolved issues that impact project success. Option B is wrong because documenting both requirements and deferring to the development team abdicates the BA's responsibility to resolve conflicts within the business domain, potentially causing rework or scope creep. Option D is wrong because escalating to the project sponsor immediately bypasses the BA's role in facilitating resolution and may be premature unless the conflict cannot be resolved at the stakeholder level.

Practice this question →

43

MCQmedium

During requirements elicitation, a stakeholder suggests a feature that is out of scope and would significantly increase project cost. What is the best action for the business analyst?

A.Immediately update the project scope statement

B.Reject the idea and explain it is out of scope

C.Ask the project sponsor for approval to include the feature

D.Record the suggestion in the issue log and continue with planned elicitation

AnswerD

Recording the suggestion in the issue log preserves the out-of-scope request without expanding scope or cost, satisfying the constraint that the feature would significantly increase project cost. Elicitation then continues against the approved requirements, and the logged item is escalated later through integrated change control for a formal decision.

Why this answer

The business analyst should document out-of-scope suggestions in the issue log for future consideration, keeping the focus on the current scope and avoiding disruption of the elicitation session. Option A is incorrect as it prematurely changes scope without proper assessment; Option B is too dismissive and may discourage stakeholder input; Option C is premature because the sponsor should only be involved after a proper evaluation.

Practice this question →

44

Multi-Selectmedium

Which THREE of the following are typical components of a business case?

Select 3 answers

A.Project Charter

B.Work Breakdown Structure

C.Alternative Analysis

D.Financial Analysis

E.Risk Assessment

AnswersC, D, E

A business case compares viable options to demonstrate the chosen approach delivers best value, so Alternative Analysis is a standard component. It records the options considered, their relative costs and benefits, and the rationale for selection, satisfying the stem's requirement for typical business case content.

Why this answer

A business case typically includes an Alternative Analysis (C), which compares viable options (e.g., build vs. buy vs. do nothing) against criteria such as cost, benefit, and feasibility to justify the recommended solution. It also includes a Financial Analysis (D), covering metrics like ROI, NPV, payback period, and cost-benefit analysis that quantify the investment's value. A Risk Assessment (E) is likewise a standard component, identifying potential risks, their probability and impact, and mitigation strategies that affect the decision.

By contrast, the Project Charter (A) is a separate authorization document created after the business case is approved, and the Work Breakdown Structure (B) is a project-planning deliverable that decomposes scope into work packages, not a business case element.

Exam trap

CAPM often tests the distinction between pre-project documents (business case) and project authorization documents (project charter), so candidates who pick the charter as a business case component fall for the sequencing trap.

Practice this question →

45

MCQhard

A business analyst is preparing a business case for a project with intangible benefits. How should the intangible benefits be presented to support the business case?

A.List intangible benefits without explanation to keep the business case concise

B.Quantify intangible benefits using the cost-benefit ratio

C.Assign a monetary value to each intangible benefit

D.Provide a qualitative description with supporting evidence such as customer surveys

AnswerD

Intangible benefits resist reliable monetary quantification, so a qualitative description backed by evidence such as customer surveys supports the business case without fabricating financial figures. This satisfies the stem's requirement to present intangible benefits credibly, letting decision-makers weigh non-financial value alongside measurable returns.

Why this answer

Intangible benefits cannot be reliably quantified in monetary terms, so the business case should present them qualitatively with supporting evidence such as customer surveys, market research, or expert opinions. This provides decision-makers with context without forcing false precision. The PMBOK Guide and CAPM emphasize that intangible benefits are described, not monetized.

Exam trap

CAPM often tests the misconception that all benefits must be monetized; candidates may incorrectly choose to assign monetary values to intangibles rather than describing them qualitatively.

How to eliminate wrong answers

Option A is wrong because listing intangible benefits without explanation fails to communicate their value and weakens the business case. Option B is wrong because the cost-benefit ratio requires monetary values for benefits, which cannot be accurately assigned to intangibles. Option C is wrong because assigning a monetary value to intangibles is subjective and can mislead stakeholders; it is not a recommended practice.

Practice this question →

46

MCQeasy

A business analyst is facilitating a requirements workshop. Which technique is best for generating a large number of ideas in a short time?

A.Multi-voting

B.Nominal group technique

C.Affinity diagram

D.Brainstorming

AnswerD

Brainstorming is a group creativity technique designed to generate many ideas rapidly by encouraging free contribution without immediate criticism. It directly satisfies the goal of producing a large volume of ideas within a short workshop timeframe.

Why this answer

Brainstorming is specifically designed to generate a large volume of ideas quickly by encouraging free-form contributions without immediate criticism or evaluation. It is the standard technique for divergent thinking in a requirements workshop. Other listed techniques are used for organizing, ranking, or refining ideas after they have been generated.

Exam trap

CAPM often tests the distinction between divergent techniques (brainstorming) and convergent techniques (multi-voting, affinity diagrams), catching candidates who pick a prioritization tool for an idea-generation question.

How to eliminate wrong answers

Option A is wrong because multi-voting is a convergent technique used to narrow down and prioritize an existing list of ideas, not to generate new ones. Option B is wrong because nominal group technique is a structured variant that includes silent idea generation followed by discussion and ranking — it is slower and more controlled than brainstorming. Option C is wrong because an affinity diagram is used to group and organize ideas into themes after generation, not to produce them.

Practice this question →

47

MCQeasy

In business analysis, what is the purpose of a stakeholder analysis?

A.Determine the communication needs and influence of stakeholders.

B.Create a project schedule.

C.Identify all project risks.

D.Assign team roles and responsibilities.

AnswerA

Stakeholder analysis maps each party's interest, influence and impact on the project, which directly determines their information requirements and preferred communication channels. This lets the BA tailor engagement and reporting to the constraint of differing stakeholder power, rather than treating all parties identically.

Why this answer

Stakeholder analysis is a core business analysis technique used to identify stakeholders, assess their interests, influence, and expectations, and determine how to engage them effectively. Option A is correct because understanding communication needs and influence is the primary purpose, enabling the business analyst to tailor engagement strategies and ensure stakeholder requirements are captured and managed.

Exam trap

PMI often tests the distinction between stakeholder analysis (which focuses on influence and communication needs) and other planning processes like risk identification or role assignment, tempting candidates to confuse stakeholder analysis with broader project planning activities.

How to eliminate wrong answers

Option B is wrong because creating a project schedule is a project management activity under Time Management, not a purpose of stakeholder analysis. Option C is wrong because identifying all project risks is the purpose of risk management processes, not stakeholder analysis, though stakeholder analysis can inform risk identification. Option D is wrong because assigning team roles and responsibilities is part of Human Resource Management or project team planning, not the direct output of stakeholder analysis.

Practice this question →

48

MCQmedium

A business analyst is evaluating the success of a recently completed project. The project delivered all requirements on time and within budget, but end-users are dissatisfied with the functionality. Which business analysis technique should the analyst use to assess this discrepancy?

A.SWOT analysis

B.Lessons learned

C.Root cause analysis

D.Cost-benefit analysis

AnswerC

Root cause analysis investigates why delivered requirements failed to satisfy users despite meeting scope, schedule and budget, exposing gaps between stated requirements and actual needs. This technique directly assesses the discrepancy between project outputs and user expectations.

Why this answer

Root cause analysis is the technique used to dig past the symptom (user dissatisfaction) to the underlying causes — such as poorly elicited requirements, missing stakeholder validation, or a gap between stated and actual needs. Since the project met time and budget but missed the actual business need, the discrepancy is a quality/requirements problem, and RCA (e.g., 5 Whys, fishbone) is the correct diagnostic tool.

Exam trap

CAPM often tests the confusion between lessons learned (documenting for the future) and root cause analysis (diagnosing the present problem), so candidates pick 'lessons learned' because it sounds like the natural post-project activity.

How to eliminate wrong answers

Option A is wrong because SWOT analysis assesses strategic Strengths, Weaknesses, Opportunities, and Threats of an organization or initiative — it is a planning tool, not a post-mortem diagnostic for requirement failures. Option B is wrong because lessons learned captures what went well and what did not for future projects, but it does not systematically identify the causal chain behind this specific discrepancy. Option D is wrong because cost-benefit analysis evaluates whether the investment was financially justified; here the project was on budget, so cost is not the issue — the functionality gap is.

Practice this question →

49

MCQmedium

A business analyst is creating a requirements traceability matrix. Which purpose does this serve?

A.Link requirements to business objectives and deliverables.

B.Track the status of requirement approval.

C.Document the rationale for requirement changes.

D.Ensure each requirement maps to a test case.

AnswerA

A requirements traceability matrix maps each requirement to its originating business objective and the deliverables that satisfy it, ensuring scope alignment and preventing orphaned requirements. This directly fulfils the purpose of linking requirements to business objectives and deliverables throughout the project lifecycle.

Why this answer

The requirements traceability matrix (RTM) is a tool used to trace requirements throughout the project lifecycle. Its primary purpose is to link requirements to business objectives and deliverables, ensuring that every requirement contributes to the project's goals and can be traced forward to deliverables and backward to origin. Option A correctly identifies this purpose.

Option B is incorrect because tracking the status of requirement approval is a function of a requirements status report, not the RTM. Option C is incorrect because documenting the rationale for requirement changes is typically done in a change log or requirements management plan. Option D is incorrect while mapping requirements to test cases is a common use of the RTM, it is not its primary purpose.

Practice this question →

50

MCQeasy

A BA is conducting a feasibility study. Which factor is assessed to determine if the project aligns with strategic goals?

A.Technical feasibility

B.Schedule feasibility

C.Organizational feasibility

D.Economic feasibility

AnswerC

Organizational feasibility examines whether the project supports the company's strategic objectives, available resources and stakeholder alignment. This directly satisfies the stem's requirement to assess alignment with strategic goals, distinguishing it from technical or economic feasibility, which address capability and cost instead.

Why this answer

Organizational feasibility assesses whether the project aligns with the strategic goals of the organization by evaluating factors such as management support, stakeholder buy-in, and cultural fit. This ensures the project supports the overall business strategy and has the necessary organizational commitment to succeed.

Exam trap

The trap here is that candidates often confuse economic feasibility (cost-benefit analysis) with strategic alignment, but economic feasibility focuses on financial viability, not whether the project supports the organization's strategic direction.

How to eliminate wrong answers

Option A is wrong because technical feasibility evaluates whether the required technology and technical resources exist to implement the solution, not alignment with strategic goals. Option B is wrong because schedule feasibility assesses whether the project can be completed within the required timeframes, not strategic alignment. Option D is wrong because economic feasibility (cost-benefit analysis) determines if the project provides financial value, but does not directly assess alignment with strategic goals.

Practice this question →

51

MCQhard

You are a business analyst on a project to replace the legacy inventory system with a cloud-based solution. The project is using a predictive lifecycle, and the requirements specification has been baselined. During the design phase, the vendor informs you that a key feature (real-time reporting) cannot be implemented within the current budget because it requires additional licensing. The feature is critical to the business case's expected cost savings. The project manager wants to descope the feature to stay within budget. As the business analyst, what is the most appropriate action?

A.Escalate the issue to the program manager and ask for a decision.

B.Agree to descope the feature and update the requirements document accordingly.

C.Request additional budget from the sponsor to cover the extra licensing cost.

D.Perform a cost-benefit analysis of including the feature versus descoping it, and present options to the sponsor.

AnswerD

With baselined requirements and a critical feature at risk, the business analyst must evaluate the trade-off rather than silently descope. A cost-benefit analysis comparing inclusion against descoping, presented to the sponsor, preserves the business case's cost savings and lets the authority decide.

Why this answer

As a business analyst in a predictive lifecycle with baselined requirements, any change to scope must go through formal change control. The most appropriate action is to perform a cost-benefit analysis that evaluates the impact of including the feature versus descoping it, and present the options to the sponsor for a decision. This ensures that the business case's expected cost savings are considered and that the sponsor, who owns the budget, makes an informed choice.

Exam trap

The trap is assuming the business analyst should simply escalate or agree to descope without performing analysis; the exam tests whether you recognize the need for a cost-benefit analysis before a scope change decision.

How to eliminate wrong answers

Option A is wrong because escalating to the program manager bypasses the sponsor's authority over budget and scope decisions; the sponsor is the correct stakeholder. Option B is wrong because unilaterally agreeing to descope a critical feature without analyzing the impact on the business case violates change control and could undermine the project's benefits. Option C is wrong because requesting additional budget without first providing a cost-benefit analysis and options is premature and does not give the sponsor the necessary information to decide.

Practice this question →

52

MCQmedium

A business analyst is working on a project to develop a new inventory management system. The project sponsor wants to ensure that all requirements are testable and verifiable. Which characteristic of effective requirements is most directly supported by writing requirements in a structured, consistent format with clear acceptance criteria?

A.Verifiability

B.Traceability

C.Atomicity

D.Prioritization

AnswerA

Verifiability means that a requirement can be tested or measured to confirm it has been met. Writing requirements with clear acceptance criteria and a structured format directly supports verifiability by providing objective conditions for testing. In this scenario, the BA can ensure that each requirement for the inventory system includes specific criteria, such as performance thresholds or functional outcomes, that can be verified during testing.

Why this answer

Verifiability is the characteristic that ensures a requirement can be tested or measured. By writing requirements in a consistent format with clear acceptance criteria, the BA provides the means to verify that the solution meets the requirement. This directly addresses the sponsor's concern for testable and verifiable requirements in the inventory management system project.

Exam trap

The trap here is confusing verifiability with traceability or atomicity, but acceptance criteria specifically enable testing, which is the essence of verifiability.

Practice this question →

53

MCQeasy

A business analyst is defining the scope of a project to develop a new employee onboarding system. The project sponsor asks for a high-level view of the solution's features and their relationships. Which business analysis technique should the business analyst use to provide this view?

A.Use case diagram

B.Feature model

C.Organizational chart

D.Mind map

AnswerB

A feature model is a hierarchical diagram that decomposes a solution into features and sub-features, showing their relationships and optionality. It provides a high-level view of the solution's capabilities, which directly addresses the sponsor's request for features and their relationships.

Why this answer

A feature model is specifically designed to show a solution's features in a hierarchical structure, including mandatory, optional, and alternative features. It gives the sponsor a clear, high-level view of what the system will do and how features relate to each other, which is ideal for scope definition and communication.

Exam trap

The trap here is confusing a use case diagram with a feature model; use cases describe interactions, while feature models describe the decomposition of solution capabilities.

Practice this question →

54

MCQhard

During requirements elicitation, a business analyst (BA) observes that key stakeholders are reluctant to share information due to a previous project's failure. The BA needs to build trust. Which technique should the BA use to encourage open communication?

A.Facilitate a workshop with ground rules to ensure respectful dialogue.

B.Conduct one-on-one interviews to gather individual perspectives.

C.Distribute a survey to collect anonymous feedback.

D.Organize a brainstorming session to generate ideas freely.

AnswerA

A facilitated workshop with agreed ground rules creates a psychologically safe, structured setting where stakeholders can speak without fear of blame, directly addressing the distrust left by the earlier failed project. This satisfies the need to encourage open communication during requirements elicitation.

Why this answer

Facilitating a workshop with ground rules establishes a structured, respectful environment that directly addresses trust issues. Ground rules create psychological safety by setting clear expectations for behavior, which encourages reluctant stakeholders to share information openly. This technique is specifically designed to rebuild trust in a group setting after a project failure.

Exam trap

PMI often tests the distinction between techniques that gather information (like surveys or interviews) versus those that build trust and collaboration (like facilitated workshops with ground rules) in sensitive stakeholder situations.

How to eliminate wrong answers

Option B is wrong because one-on-one interviews, while useful for gathering individual perspectives, do not actively rebuild group trust or address the collective reluctance stemming from a previous failure. Option C is wrong because distributing an anonymous survey collects feedback without fostering open dialogue or trust-building interaction among stakeholders. Option D is wrong because a brainstorming session, though free-flowing, lacks the structured ground rules needed to manage sensitive dynamics and ensure respectful communication after a trust breakdown.

Practice this question →

55

MCQmedium

You are a business analyst on a project to replace a legacy claims processing system. Executive management wants to understand the expected benefits and costs before authorizing the project. Which document should you prepare to present the justification for the investment?

A.Business case

B.Requirements traceability matrix

C.Project charter

D.Work breakdown structure

AnswerA

A business case is the formal document that justifies initiating a project by comparing expected benefits, costs, risks, and strategic alignment. Executive management uses it to decide whether to authorize funding. It directly addresses the need to evaluate financial viability and expected value before project approval, making it the appropriate deliverable for this scenario.

Why this answer

A business case is the standard artifact for justifying a project investment. It captures the problem or opportunity, expected benefits, cost estimates, risks, and alignment with organizational strategy. Executives rely on it to make an informed go/no-go decision.

The other artifacts serve different purposes: authorizing work, tracing requirements, or decomposing scope, and none replaces the business case for investment justification.

Exam trap

The trap here is confusing the project charter, which authorizes the project, with the business case, which justifies the investment before authorization.

Practice this question →

56

MCQeasy

A business analyst has completed elicitation for a customer portal project and now has a long list of raw stakeholder statements. Before the statements can be used as requirements, the analyst must distinguish which are true requirements. Which characteristic must a well-formed requirement exhibit?

A.It must describe a capability or condition the solution needs to satisfy.

B.It must be approved by every stakeholder who attended the elicitation session.

C.It must specify the technology platform on which the capability will be delivered.

D.It must be traceable to a specific line item in the project budget.

AnswerA

A requirement states a capability or condition that the solution must meet to deliver value to stakeholders. This distinguishes genuine requirements from opinions, background information, and design decisions collected during elicitation. Applying this characteristic lets the analyst separate statements that constrain the solution from commentary that merely describes the current environment or a stakeholder preference for the portal project.

Why this answer

The defining test of a requirement is that it expresses a capability or condition the solution must satisfy to deliver value. Raw elicitation notes mix true requirements with opinions, context, and design ideas, so the analyst filters statements through this characteristic. Traceability, unanimous approval, and platform prescription are either governance artifacts or design constraints, not properties that make a statement a requirement.

Exam trap

The trap here is confusing governance or design attributes, such as budget linkage or platform choice, with the fundamental nature of a requirement as a needed capability or condition.

Practice this question →

57

MCQmedium

After a change request is approved, a business analyst must update the requirements documentation. What is the most important step to ensure traceability?

A.Update the requirements traceability matrix

B.Revise the project schedule to reflect the change

C.Communicate the change to the development team

D.Archive the previous version of the requirements document

AnswerA

Updating the requirements traceability matrix directly satisfies the traceability constraint by linking the approved change to its originating requirement, affected deliverables and test cases. The matrix is the designated artefact for recording these relationships, so revising it after approval keeps the audit trail complete and verifiable.

Why this answer

The requirements traceability matrix (RTM) is the artifact that links each requirement to its source, design, code, and test cases, so updating it after an approved change is what preserves end-to-end traceability. Without updating the RTM, the change would be invisible to downstream verification and impact analysis. This is the BA's primary mechanism for maintaining traceability across the requirements lifecycle.

Exam trap

CAPM often tests the confusion between updating the RTM (the traceability artifact) and other valid but non-traceability actions like scheduling, communication, or archiving.

How to eliminate wrong answers

Option B is wrong because revising the schedule addresses timing and effort, not traceability of requirements to their sources and downstream artifacts. Option C is wrong because communicating the change to developers is a coordination step, not a traceability control — it does not record the linkage between the changed requirement and its origin or tests. Option D is wrong because archiving the previous version supports version control and audit history but does not establish traceability links; the RTM is the tool that actually maps requirements to their sources and deliverables.

Practice this question →

58

MCQeasy

You are a business analyst on a project to develop a new online banking portal. The project is using a hybrid approach with both predictive and adaptive elements. The requirements have been documented in a functional specification, but during development, the product owner requests significant changes based on user feedback. The change control board (CCB) is slow to approve changes, causing delays. The project manager wants to minimize rework while still incorporating valuable feedback. As the business analyst, what is the best course of action?

A.Implement a stricter change control process requiring more documentation.

B.Use requirements traceability to evaluate the impact of each change and prioritize accordingly.

C.Freeze the requirements and defer all changes to a future release.

D.Allow the product owner to approve changes directly to speed up the process.

AnswerB

Traceability links each requested change to affected requirements, designs and tests, so the business analyst can quantify rework and dependencies before the CCB decides. This directly satisfies the stem's constraint of minimising rework while still incorporating valuable user feedback.

Why this answer

Requirements traceability allows the business analyst to assess the impact of each requested change on existing requirements, test cases, and deliverables. This enables informed prioritization, minimizing rework while incorporating valuable feedback. Option A (stricter change control) would further slow down the process, contrary to the goal.

Option C (freezing requirements) ignores user feedback and may lead to a product that doesn't meet needs. Option D (allowing the product owner to approve directly) bypasses governance and could introduce uncontrolled changes, causing rework.

Practice this question →

59

MCQmedium

A business analyst is assigned to a project that aims to streamline the supply chain process in a manufacturing company. The project has a tight deadline, and the project sponsor wants to use a proven framework to ensure efficiency. During the initial analysis, the analyst finds that the current process has many manual handoffs and inconsistent data formats. Several cross-functional teams have conflicting priorities. The sponsor asks for a recommendation that balances structure with flexibility. As the business analyst, which approach should you recommend?

A.Adopt a Six Sigma DMAIC approach to reduce defects and standardize processes.

B.Use the BABOK guide as a framework to define business analysis activities and deliverables.

C.Follow the Prince2 methodology for project management and business analysis.

D.Implement a pure Waterfall approach with strict phase gates.

AnswerB

The BABOK guide provides a structured knowledge framework covering elicitation, requirements analysis and stakeholder engagement, letting the analyst define activities and deliverables while adapting techniques to conflicting cross-functional priorities. This satisfies the sponsor's demand for a proven framework that still balances structure with flexibility under a tight deadline.

Why this answer

The BABOK (Business Analysis Body of Knowledge) guide is the definitive framework for business analysis, providing a flexible structure of knowledge areas, tasks, techniques, and competencies that can be tailored to any project context. It directly addresses the analyst's need to define business analysis activities and deliverables while balancing structure with flexibility, as it is methodology-agnostic and can be adapted to tight deadlines and cross-functional conflicts. Unlike Six Sigma, PRINCE2, or Waterfall, BABOK is specifically designed for the business analysis role, making it the most appropriate recommendation for the sponsor.

Exam trap

CAPM often tests the distinction between business analysis frameworks and project management or quality methodologies, trapping candidates who confuse Six Sigma or PRINCE2 with business analysis standards like BABOK.

How to eliminate wrong answers

Option A is wrong because Six Sigma DMAIC is a quality improvement methodology focused on reducing defects and process variation, not a business analysis framework; it would not address conflicting priorities or define analysis deliverables. Option C is wrong because PRINCE2 is a project management methodology, not a business analysis framework, and it does not provide guidance on business analysis tasks such as elicitation, requirements analysis, or solution evaluation. Option D is wrong because a pure Waterfall approach with strict phase gates is a project management lifecycle that lacks the flexibility needed to handle evolving requirements and cross-functional conflicts, and it does not offer business analysis-specific guidance.

Practice this question →

60

MCQhard

A business analyst is performing a cost-benefit analysis for a proposed system upgrade. The upgrade costs $50,000 upfront and saves $15,000 per year in operational costs. The project has a 5-year horizon. What is the payback period in years?

A.5.00 years

B.4.00 years

C.3.33 years

D.0.33 years

AnswerC

Payback period divides the initial outlay by the annual net saving: $50,000 ÷ $15,000 = 3.33 years. The 5-year horizon is irrelevant to this calculation, since payback measures only the time required to recover the upfront investment from cumulative savings.

Why this answer

The payback period is the upfront cost divided by the annual savings: $50,000 ÷ $15,000 = 3.33 years. This is the time required for cumulative savings to equal the initial investment. It is a simple, undiscounted measure that ignores the time value of money and any cash flows beyond the payback point.

Exam trap

The trap is the distractor 0.33, which is the reciprocal of the correct answer — candidates who invert the formula (savings ÷ cost) instead of cost ÷ savings will pick it.

How to eliminate wrong answers

Option A is wrong because 5.00 years is the full project horizon, not the break-even point — the investment is recovered well before the horizon ends. Option B is wrong because 4.00 years would require annual savings of $12,500, not $15,000. Option D is wrong because 0.33 years is the reciprocal of the correct answer (15,000/50,000), which represents the fraction of the investment recovered per year, not the payback period.

Practice this question →

61

MCQeasy

A business analyst needs to document the relationships between requirements, design, and test cases. Which artifact is best for this purpose?

A.Use Case Diagram

B.Work Breakdown Structure

C.Business Requirements Document

D.Requirements Traceability Matrix

AnswerD

A Requirements Traceability Matrix (RTM) is a formal document (often a table) that links each requirement to its source, design specification, test case, and verification status, making it the ideal artifact for tracking relationships throughout the project lifecycle.

Why this answer

A Requirements Traceability Matrix (RTM) is specifically designed to map requirements to design elements, test cases, and other artifacts, ensuring bidirectional traceability. It documents relationships and helps verify that all requirements are covered by tests and design. This directly matches the business analyst's need.

Exam trap

CAPM often tests confusion between documents that capture requirements (BRD) and the matrix that traces them — candidates may pick BRD thinking it covers traceability, but only the RTM provides the mapping.

How to eliminate wrong answers

Option A is wrong because a Use Case Diagram models interactions between actors and a system, not traceability between requirements, design, and tests. Option B is wrong because a Work Breakdown Structure decomposes project deliverables, not requirement relationships. Option C is wrong because a Business Requirements Document captures requirements but does not provide the traceability mapping across design and test cases.

Practice this question →

62

MCQhard

During a requirements workshop, two key stakeholders disagree on a critical requirement. The project manager asks the business analyst to facilitate a resolution. Which approach is most effective?

A.Ask the project sponsor to decide.

B.Document both requirements and proceed with both.

C.Hold a vote among all stakeholders.

D.Use a prioritization matrix to evaluate trade-offs.

AnswerD

A prioritisation matrix scores competing requirements against agreed criteria such as value, cost and risk, exposing trade-offs objectively. This lets the two stakeholders see which requirement delivers most benefit, resolving their disagreement on evidence rather than opinion or escalation.

Why this answer

A prioritization matrix enables objective comparison of requirements based on predefined criteria such as value, cost, and urgency, facilitating a data-driven consensus. Option A is wrong: asking the sponsor to decide bypasses stakeholder collaboration and may not address the underlying disagreement. Option B is wrong: proceeding with both requirements can lead to scope creep and resource conflicts.

Option C is wrong: a vote may not resolve deep disagreements and can alienate minority stakeholders.

Practice this question →

63

Multi-Selectmedium

A BA is prioritizing a large number of requirements. Which TWO techniques are best suited for this scenario?

Select 2 answers

A.Benchmarking

B.Focus group

C.Kano model

D.MoSCoW analysis

E.Observation

AnswersC, D

The Kano model classifies requirements by how their presence affects satisfaction: basic, performance, delighter, indifferent and reverse. With a large backlog, it identifies which requirements genuinely drive customer satisfaction, letting the BA prioritise by value impact rather than by stakeholder volume alone.

Why this answer

The Kano model (C) is correct because it classifies requirements by their effect on customer satisfaction (must-be, performance, attractive, indifferent, reverse), which directly supports prioritization by revealing which features deliver the greatest satisfaction impact. MoSCoW analysis (D) is correct because it sorts requirements into Must have, Should have, Could have, and Won't have categories, giving a clear, stakeholder-agreed ranking for large requirement backlogs. Benchmarking (A) is not a prioritization technique; it compares organizational practices or performance against competitors or best-in-class standards.

A focus group (B) is an elicitation technique that gathers qualitative feedback from selected participants, not a method for ranking requirements. Observation (E) is also an elicitation technique used to watch users perform tasks and uncover tacit requirements, not to prioritize them.

Exam trap

CAPM often tests the confusion between elicitation techniques (focus groups, observation) and prioritization techniques (Kano, MoSCoW), catching candidates who pick a data-gathering tool for a ranking task.

Practice this question →

64

Multi-Selectmedium

Which THREE of the following are components typically included in a business case?

Select 3 answers

A.Stakeholder Register

B.Cost-Benefit Analysis

C.Work Breakdown Structure

D.Risk Assessment

E.Executive Summary

AnswersB, D, E

Cost-benefit analysis quantifies expected financial returns against projected outlays, directly satisfying the business case's need to justify investment viability. It compares total costs with anticipated benefits, enabling stakeholders to assess whether the initiative delivers sufficient value. This financial comparison is a standard business case component, alongside expected outcomes and risks.

Why this answer

A business case typically includes an Executive Summary (E), which concisely presents the problem, proposed solution, and recommendation to decision-makers at the top of the document. It also includes a Cost-Benefit Analysis (B), which quantifies expected costs against projected benefits (e.g., ROI, NPV, payback period) to justify the investment. A Risk Assessment (D) is also standard, identifying potential risks, their likelihood and impact, and mitigation strategies that could affect the initiative's viability.

By contrast, a Stakeholder Register (A) is a project stakeholder management artifact produced during project initiation, not a core business case component, and a Work Breakdown Structure (C) is a scope decomposition tool created during project planning, so neither belongs in the business case itself.

Exam trap

CAPM often tests the boundary between pre-project artifacts (business case, benefits management plan) and project artifacts (stakeholder register, WBS) — candidates pick WBS or stakeholder register because they sound 'project-y' without checking which phase produces them.

Practice this question →

65

MCQmedium

A business analyst is managing requirements for a software upgrade project. The project sponsor wants to ensure that every requirement can be traced back to a business need. What is the primary purpose of requirements traceability?

A.To ensure each requirement meets a business need

B.To document system architecture

C.To assign requirements to team members

D.To estimate project costs

AnswerA

Traceability links each requirement backwards to its originating business need and stakeholder, confirming that no requirement exists without justification. This directly satisfies the sponsor's constraint that every requirement be traceable to a business need, exposing gaps or gold-plating during scope validation.

Why this answer

Requirements traceability ensures that each requirement is linked to a business need, helping to validate scope, manage changes, and confirm value. It also helps in identifying the impact of changes.

Practice this question →

66

MCQhard

In a requirements gathering workshop, two stakeholders have differing opinions on the system interface design. The business analyst decides to use a technique that involves listing pros and cons of each option. Which technique is being used?

A.Prototyping

B.Decision Analysis

C.Interface Analysis

D.Brainstorming

AnswerB

Decision Analysis compares alternatives by weighing their advantages and disadvantages against defined criteria, producing a reasoned recommendation. This satisfies the stem's requirement because listing pros and cons of each interface design option is the defining activity of that technique.

Why this answer

Decision Analysis is a technique used to evaluate and compare multiple options by systematically listing the advantages (pros) and disadvantages (cons) of each. In this scenario, the business analyst is facilitating a structured comparison of two interface design alternatives, which is the core of Decision Analysis. This technique helps stakeholders make informed choices by weighing the trade-offs objectively.

Exam trap

CAPM often tests the confusion between Decision Analysis and Brainstorming, as both are group techniques, but Decision Analysis is for evaluating options while Brainstorming is for generating ideas.

How to eliminate wrong answers

Option A is wrong because Prototyping involves creating a preliminary working model of the system to elicit feedback and clarify requirements, not listing pros and cons. Option C is wrong because Interface Analysis focuses on identifying and defining the interactions between systems or components, not on comparing options via pros and cons. Option D is wrong because Brainstorming is a group creativity technique to generate a large number of ideas, not to evaluate them by listing pros and cons.

Practice this question →

67

MCQhard

A business analyst is verifying that all requirements have corresponding test cases. They find a requirement that has no linked test case. What should the BA do first?

A.Ask the project manager to approve the missing test.

B.Ignore it as it may not be critical.

C.Request a test case to be created for that requirement.

D.Remove the requirement if it cannot be tested.

AnswerC

Raising a request for the missing test case closes the traceability gap identified during verification, ensuring the requirement gains coverage. This is the immediate corrective step; escalating or altering the requirement comes only after the coverage shortfall is formally addressed.

Why this answer

Request a test case to be created for that requirement. In business analysis, traceability ensures every requirement has a corresponding test case to verify it is implemented correctly. When a requirement lacks a test case, the BA should first request one to maintain coverage.

Option A is incorrect because the project manager does not typically authorize test cases; the BA or QA team handles them. Option B is incorrect because ignoring the issue violates traceability best practices. Option D is incorrect because removing the requirement is premature without analysis; the BA should first try to create a test case.

Practice this question →

68

Multi-Selectmedium

Which THREE items are typically included in a business analysis plan? (Choose three.)

Select 3 answers

A.Deliverables and artifacts

B.Stakeholder list and roles

C.Requirements prioritization criteria

D.Budget estimates

E.Detailed project schedule

AnswersA, B, C

Deliverables and artifacts specify what the business analysis effort will produce, such as models, specifications and matrices, giving the plan its scope. Listing them satisfies the stem's requirement for a typical business analysis plan component by defining tangible outputs.

Why this answer

A business analysis plan typically defines the deliverables and artifacts that the BA will produce (e.g., requirements documents, models, traceability matrices), so option A is correct because it scopes the tangible outputs of the BA work. Option B is correct because identifying the stakeholder list and their roles is essential to plan engagement, communication, and elicitation activities throughout the initiative. Option C is correct because requirements prioritization criteria (such as MoSCoW, value/risk ranking, or business value scoring) must be agreed upon in the plan to guide how requirements are ranked and approved.

Option D is not typically part of the BA plan because budget estimates belong to the project manager's cost management and business case, not the BA work plan. Option E is also not included, since the detailed project schedule is a project management artifact (e.g., developed with scheduling tools like MS Project) rather than a component of the business analysis plan.

Exam trap

The trap is confusing the business analysis plan with the project management plan; candidates pick budget or schedule because those are 'plans,' but they belong to project management, not business analysis.

Practice this question →

69

MCQeasy

A business analyst is tasked with modeling the logical data requirements for a new customer relationship management (CRM) system. Which artifact should the BA create to show the relationships between customer entities and their attributes?

A.A context diagram

B.An entity-relationship diagram

C.A user story map

D.A use case diagram

AnswerB

Entity-relationship diagrams model logical data structures by depicting entities, their attributes and the cardinality relationships between them, directly satisfying the requirement to show how customer entities relate. Unlike physical schemas or class diagrams, ERDs are technology-agnostic and capture exactly the logical data requirements the BA must document.

Why this answer

The entity-relationship diagram (ERD) is the correct artifact because it specifically models logical data requirements by showing entities (e.g., Customer, Order) and their attributes (e.g., CustomerID, Name) along with the relationships between them (e.g., one-to-many). This directly addresses the task of modeling data for a CRM system, where understanding how customer data relates to other entities is critical.

Exam trap

The trap here is confusing a data modeling artifact (ERD) with process or interaction models (context diagram, use case diagram) or agile planning tools (user story map), leading candidates to pick a diagram that shows 'what the system does' rather than 'how data is structured'.

How to eliminate wrong answers

Option A is wrong because a context diagram shows the system's boundaries and external interactions (actors), not internal data structures or entity relationships. Option C is wrong because a user story map organizes user stories by functionality and release iterations, focusing on workflow and value delivery, not data modeling. Option D is wrong because a use case diagram captures functional requirements by showing actors and use cases, but it does not depict data entities, attributes, or their relationships.

Practice this question →

70

MCQmedium

A business analyst is gathering requirements for a new reporting system. The stakeholders are located in different time zones and have conflicting availability. Which elicitation technique would be most effective for this situation?

A.Document analysis

B.Interviews

C.Facilitated workshops

D.Surveys

AnswerD

Surveys let stakeholders in different time zones respond asynchronously, removing the need for simultaneous availability. This directly satisfies the conflicting-schedule constraint, whereas interviews, workshops and focus groups demand real-time participation. Surveys also scale to dispersed groups, gathering structured input efficiently when synchronous elicitation is impractical.

Why this answer

Surveys are the most effective technique for geographically dispersed stakeholders with conflicting schedules because they can be distributed asynchronously, allowing each stakeholder to respond at their convenience. Unlike interviews or workshops, surveys do not require real-time coordination across time zones. Document analysis is not an elicitation technique for gathering new requirements from stakeholders.

Exam trap

CAPM often tests the assumption that interviews or workshops are always best for gathering detailed requirements, but the key differentiator here is the logistical constraint of time zones and conflicting availability, which makes asynchronous techniques like surveys the correct choice.

How to eliminate wrong answers

Option A is wrong because document analysis examines existing artifacts rather than actively eliciting requirements from stakeholders, and it does not address the time zone challenge. Option B is wrong because interviews require one-on-one synchronous sessions, which are difficult to schedule across conflicting time zones. Option C is wrong because facilitated workshops demand simultaneous participation, making them impractical when stakeholders have conflicting availability across different time zones.

Practice this question →

71

MCQhard

A business analyst is validating requirements and discovers that several requirements conflict with each other. The project sponsor insists on including all conflicting requirements to satisfy different stakeholders. What is the best course of action for the BA?

A.Escalate the issue to the project sponsor and ask for a decision.

B.Facilitate a meeting with stakeholders to discuss trade-offs and prioritize requirements.

C.Remove the conflicting requirements and proceed with the remaining ones.

D.Include all requirements as requested and let the development team resolve conflicts during implementation.

AnswerB

Facilitating a stakeholder meeting exposes the conflicts openly, letting the group weigh trade-offs and agree priorities rather than forcing every requirement in. This resolves the conflict while preserving sponsor and stakeholder buy-in, which unilateral decisions would undermine.

Why this answer

The business analyst's role includes facilitating stakeholder collaboration to resolve conflicts through trade-off analysis and prioritization. This aligns with the BABOK guide's requirement management process, where the BA helps stakeholders understand the impact of conflicting requirements and negotiate a prioritized set that delivers the most value within project constraints.

Exam trap

PMI often tests the misconception that the BA should defer all decisions to the sponsor or development team, when in fact the BA must actively facilitate conflict resolution using structured analysis techniques.

How to eliminate wrong answers

Option A is wrong because escalating to the project sponsor without first facilitating a discussion abdicates the BA's responsibility to analyze and resolve conflicts collaboratively; the sponsor may not have the detailed understanding needed for a decision. Option C is wrong because removing conflicting requirements unilaterally ignores stakeholder needs and may eliminate critical functionality, violating the principle of stakeholder engagement. Option D is wrong because including all conflicting requirements and deferring resolution to development risks significant rework, integration failures, and scope creep, as conflicts often involve incompatible business rules or technical constraints that cannot be resolved during implementation.

Practice this question →

72

MCQmedium

A business analyst is facilitating a requirements elicitation session for a new customer relationship management system. Several stakeholders from sales, marketing, and customer support are present, but the discussion keeps drifting into unrelated operational complaints. Which facilitation technique should the business analyst use to keep the session focused on gathering requirements?

A.Immediately end the session and schedule a follow-up with only the key decision makers.

B.Use a parking lot to capture off-topic issues and return to the agenda.

C.Ask each stakeholder to submit written requirements after the meeting instead of discussing them.

D.Switch to a round-robin format where each participant speaks in turn.

AnswerB

A parking lot is a facilitation tool that visibly records off-topic but potentially important issues on a separate list, allowing the group to acknowledge them without derailing the current discussion. It respects stakeholder concerns while keeping the session aligned to the elicitation objectives, and the captured items can be addressed later.

Why this answer

A parking lot is a lightweight facilitation technique that captures off-topic items in a visible list so the group can acknowledge them without losing focus. It allows the business analyst to maintain momentum on the agenda while assuring stakeholders that their concerns are recorded. This keeps the elicitation session productive and respects all input, which is essential for effective requirements gathering.

Exam trap

The trap here is assuming that any structured turn-taking method, such as round-robin, will automatically keep a meeting on topic when the real issue is unmanaged digressions.

Practice this question →

73

MCQmedium

A business analyst is using the MoSCoW technique to prioritize requirements. A feature is determined to be important but not critical for the first release. How should it be categorized?

A.Could have

B.Should have

C.Must have

D.Won't have

AnswerB

MoSCoW's Should-have category covers requirements that are important and expected but not vital for the first release. This matches the stem exactly: the feature matters yet can be deferred without breaking the initial delivery, unlike Must-have items.

Why this answer

In MoSCoW prioritization, 'Should have' represents requirements that are important but not critical for the first release; they can be worked around if omitted, but are high priority. 'Must have' is reserved for critical, non-negotiable features. Therefore, a feature that is important but not critical is categorized as 'Should have'.

Exam trap

CAPM often tests the confusion between 'Should have' and 'Could have'—candidates must remember that 'Should have' is important but not critical, while 'Could have' is merely desirable.

How to eliminate wrong answers

Option A is wrong because 'Could have' represents nice-to-have features that are desirable but not important; they are lower priority than 'Should have'. Option C is wrong because 'Must have' is for critical requirements that are mandatory for the release; the question states the feature is not critical. Option D is wrong because 'Won't have' means the feature is explicitly excluded from the current release, which contradicts it being important.

Practice this question →

74

MCQeasy

A business analyst is using a context diagram to model the scope of a system. What does a context diagram primarily show?

A.Internal architecture of the system

B.Sequence of interactions between objects

C.The system boundary and external entities that interact with it

D.Detailed system processes and data flows

AnswerC

A context diagram places the system at the centre and depicts only its boundary plus the external entities (people, organisations, other systems) that exchange inputs and outputs with it. It deliberately omits internal processes and data stores, so it satisfies the scope-modelling constraint by showing what lies inside versus outside the system.

Why this answer

A context diagram shows the system as a single process (or bubble) and depicts the external entities that interact with it, along with the data flows across the system boundary. It defines the scope of the system by making explicit what is inside and what is outside. This is the primary purpose of a context diagram in structured analysis.

Exam trap

CAPM often tests the distinction between a context diagram and a detailed data flow diagram, and candidates may incorrectly select an option describing internal processes or data stores.

How to eliminate wrong answers

Option A is wrong because internal architecture is not shown in a context diagram; it is a high-level view that treats the system as a black box. Option B is wrong because sequence of interactions between objects is depicted in sequence diagrams, not context diagrams. Option D is wrong because detailed system processes and data flows are shown in lower-level data flow diagrams (DFDs), not in the context diagram, which only shows the single system process and external entities.

Practice this question →

75

MCQeasy

A BA is conducting a needs assessment for a new system. Which activity is performed first?

A.Identify stakeholders

B.Create business case

C.Gather requirements

D.Define business needs

AnswerD

Defining business needs comes first in needs assessment, establishing the problem or opportunity and desired outcomes before any solution options are evaluated. Subsequent activities such as gap analysis and recommending solutions depend on this initial articulation of what the business requires.

Why this answer

Defining business needs is the first activity in a needs assessment because it establishes the problem or opportunity the project must address. Only after the need is defined can stakeholders be identified, a business case built, and requirements gathered. This sequence ensures all subsequent work is anchored to a validated business need.

Exam trap

CAPM often tests the sequencing of needs assessment activities, and candidates frequently pick 'identify stakeholders' first because it feels foundational, when defining the business need logically precedes it.

How to eliminate wrong answers

Option A is wrong because identifying stakeholders, while early, follows the initial definition of the business need — you need to know what problem you are solving before determining who is affected. Option B is wrong because creating a business case comes after the need is defined and typically after some stakeholder and solution analysis; the business case justifies investment in addressing the need. Option C is wrong because gathering requirements occurs after the need is defined and stakeholders are engaged; requirements are derived from the need, not the other way around.

Practice this question →

Page 1 of 2 · 141 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Business Analysis Frameworks questions.

Start 20-question session