CAPM Business Analysis Frameworks Practice Test 11 — 15 Questions

Question 1

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?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Root cause analysis. 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.

Answer

SWOT analysis

Answer

Lessons learned

Answer

Cost-benefit analysis

Question 2

A startup is developing a mobile application with rapidly changing requirements. The team needs to deliver value quickly and adapt to user feedback. Which business analysis approach is most appropriate?

Accepted Answer

Agile. Agile is designed for rapid iteration and adaptability to changing requirements.

Answer

V-Model

Answer

Spiral

Answer

Waterfall

Question 3

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?

Accepted Answer

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

Answer

Manage closely

Answer

Monitor

Answer

Keep informed

Question 4

A business analyst is facilitating a requirements prioritization session for a new e-commerce platform. The project has a strict deadline and limited resources. Which prioritization technique should be used to maximize value delivered within constraints?

Accepted Answer

MoSCoW. MoSCoW is a prioritization technique that categorizes requirements into Must have, Should have, Could have, and Won't have. It is particularly effective when there are strict deadlines and limited resources because it helps stakeholders agree on the most critical features that must be delivered, while allowing flexibility for less important ones. By focusing on Must-haves first, the team can maximize value within constraints. Other techniques like weighted scoring or Kano model are more complex and time-consuming, and timeboxing is a scheduling technique, not a prioritization method.

Answer

Weighted scoring

Answer

Timeboxing

Answer

Kano model

Question 5

Refer to the exhibit. A business analyst is reviewing the requirements status in a JSON export from a requirements management tool. The analyst notices that REQ02 is still in 'Draft' while REQ01 is 'Approved'. What should the analyst do next?

Accepted Answer

Facilitate a review meeting for REQ02. A requirement in draft status needs to be reviewed and approved by stakeholders before proceeding, so facilitating a review meeting is the appropriate action.

Answer

Update the traceability matrix

Answer

Approve REQ02 immediately

Answer

Request closure for REQ02

Question 6

Refer to the exhibit. A business analyst is troubleshooting a performance issue reported by users. The ping and traceroute show successful connectivity to the server at 10.0.0.1. Despite this, the application response is slow. Which analysis step should the analyst take next?

Accepted Answer

Check the server CPU utilization. Since network connectivity is confirmed, the next step is to investigate server-side performance, such as CPU utilization, to identify bottlenecks.

Answer

Reboot the server

Answer

Increase bandwidth

Answer

Verify DNS resolution

Question 7

A business analyst is conducting a needs assessment for a new software system. Which of the following is the primary purpose of this activity?

Accepted Answer

To identify the gap between current and desired business states. A needs assessment in business analysis is performed to understand the current state, define the desired future state, and identify the gap between them. This gap analysis is the foundation for justifying and scoping a solution.

Answer

To design the technical architecture of the proposed solution

Answer

To validate that the solution meets business requirements

Answer

To prioritize projects based on return on investment

Question 8

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?

Accepted Answer

Record the suggestion in the issue log and continue with planned elicitation. 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.

Answer

Immediately update the project scope statement

Answer

Reject the idea and explain it is out of scope

Answer

Ask the project sponsor for approval to include the feature

Question 9

A business analyst is creating a business case for a new project. Which of the following is a key component that must be included in the business case?

Accepted Answer

Cost-benefit analysis and financial metrics. A business case is the document that justifies the investment in a project, and its core component is the cost-benefit analysis with financial metrics such as ROI, NPV, IRR, and payback period. These quantify whether the project is worth funding and are the primary decision-making input for stakeholders.

Answer

User stories and acceptance criteria

Answer

Project milestones and deliverables

Answer

Risk register and risk responses

Question 10

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

Accepted Answer

Brainstorming. 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.

Answer

Multi-voting

Answer

Nominal group technique

Answer

Affinity diagram

Question 11

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

Accepted Answer

Update the requirements traceability matrix. 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.

Answer

Revise the project schedule to reflect the change

Answer

Communicate the change to the development team

Answer

Archive the previous version of the requirements document

Question 12

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

Accepted Answer

The system boundary and external entities that interact with it. 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.

Answer

Internal architecture of the system

Answer

Sequence of interactions between objects

Answer

Detailed system processes and data flows

Question 13

A business analyst discovers that two requirements conflict with each other. What is the best strategy to resolve this conflict?

Accepted Answer

Facilitate a meeting with the key stakeholders to negotiate a resolution. When two requirements conflict, the best strategy is to bring the key stakeholders together and facilitate a negotiation to resolve the conflict collaboratively. This aligns with PMI/CAPM principles of stakeholder engagement, conflict resolution, and collaborative problem-solving rather than unilateral escalation or deferral. The business analyst or PM facilitates, but the stakeholders own the decision.

Answer

Ask the project sponsor to choose which requirement to keep

Answer

Document both requirements and let the development team decide

Answer

Include both requirements and add a third requirement to reconcile them

Question 14

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?

Accepted Answer

Provide a qualitative description with supporting evidence such as customer surveys. 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.

Answer

List intangible benefits without explanation to keep the business case concise

Answer

Quantify intangible benefits using the cost-benefit ratio

Answer

Assign a monetary value to each intangible benefit

Question 15

During a project, multiple stakeholders have conflicting requirements for a new software feature. The business analyst needs to prioritize the requirements to ensure the most critical ones are delivered first. Which technique is most appropriate for prioritizing requirements?

Accepted Answer

MoSCoW. MoSCoW (Must have, Should have, Could have, Won't have) is a prioritization technique that helps categorize requirements based on importance. Brainstorming, interviews, and observation are elicitation, not prioritization, techniques.

Answer

Interview

Answer

Brainstorming

Answer

Observation