CAPM Business Analysis Frameworks — Timed 15 Questions

Question 1

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

Accepted Answer

Identify Stakeholders, then Plan Stakeholder Engagement, then Analyze Stakeholders, then Manage Stakeholder Engagement, then Monitor Stakeholder Engagement. According to the PMBOK Guide, the correct sequence for stakeholder engagement is: Identify Stakeholders, Plan Stakeholder Engagement, Manage Stakeholder Engagement, Monitor Stakeholder Engagement. 'Analyze Stakeholders' is not a separate PMBOK process; analysis is part of Identify Stakeholders. Among the given options, option B has Identify and Plan in the correct order, with Analyze inserted after Plan. Although Analyze is not a standard process, option B best represents the PMBOK order, making it the correct choice.

Answer

Identify Stakeholders, then Analyze Stakeholders, then Plan Stakeholder Engagement, then Manage Stakeholder Engagement, then Monitor Stakeholder Engagement

Answer

Identify Stakeholders, then Manage Stakeholder Engagement, then Plan Stakeholder Engagement, then Monitor Stakeholder Engagement, then Analyze Stakeholders

Answer

Plan Stakeholder Engagement, then Identify Stakeholders, then Analyze Stakeholders, then Manage Stakeholder Engagement, then Monitor Stakeholder Engagement

Question 2

A BA is validating requirements with the customer. The customer agrees the requirements meet their needs, but later during development, the customer realizes a gap. What is the most likely cause?

Accepted Answer

Inadequate verification. Verification ensures that the requirements are correctly specified and complete. In this scenario, the customer validated the requirements (they agreed they meet their needs), but a gap was found later during development. This gap indicates that the requirements were not fully and accurately documented or defined, which is a verification failure. Inadequate verification means the requirements were not properly checked for correctness and completeness before sign-off, leading to the gap. The customer's agreement shows validation was successful, but the underlying specifications were flawed.

Answer

Lack of traceability

Answer

Incorrect prioritization

Answer

Poor elicitation technique

Question 3

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

Accepted Answer

Cost-benefit analysis. 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.

Answer

Requirements traceability matrix

Answer

Stakeholder register

Answer

Work breakdown structure

Question 4

A project is experiencing scope creep because the BA did not properly manage requirements. What is the most likely root cause?

Accepted Answer

Poor change control process. Scope creep often results from a poor change control process that allows unauthorized changes. Option A is incorrect because inadequate requirements prioritization is not the root cause; scope creep occurs when changes are made without proper control. Option B is incorrect because lack of stakeholder identification can lead to missing requirements, but the root cause of scope creep is the lack of a formal change control process. Option D is incorrect because insufficient testing detects defects, but it does not directly cause scope creep.

Answer

Inadequate requirements prioritization

Answer

Lack of stakeholder identification

Answer

Insufficient testing

Question 5

A large organization is implementing a new customer relationship management system. The business analysis team has identified that multiple departments have conflicting requirements due to differing processes. The project sponsor insists on using a predictive approach. Which business analysis framework should the team adopt to manage these conflicts effectively?

Accepted Answer

Disciplined Agile. Disciplined Agile (DA) is a hybrid framework that can be tailored to a predictive approach when the project sponsor insists on such. It provides a toolkit of practices and decision points to manage conflicting requirements through its process goals, making it suitable for this scenario. RUP is an iterative framework, not predictive, and is not part of the PMI-CAPM syllabus.

Answer

Scrum

Answer

Six Sigma

Answer

Rational Unified Process (RUP)

Question 6

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. The primary purpose of a needs assessment is to identify the gap between current and desired business states, which is Option A. Option B (designing technical architecture) is a design activity, not a needs assessment activity. Option C (validating solution meets requirements) is part of solution evaluation. Option D (prioritizing projects based on ROI) is project selection, not needs assessment.

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 7

You are a business analyst on a project to upgrade the customer relationship management (CRM) system in a mid-sized company. During the needs assessment, you discover that the sales team wants a mobile app, while the support team prefers a web-based interface. The IT department insists on using a cloud platform, but the finance department is concerned about recurring costs. The project manager asks you to recommend a business analysis framework to handle these conflicting interests. The project is time-sensitive and requires quick decisions. As the business analyst, what should you do?

Accepted Answer

Recommend an Agile framework with regular stakeholder feedback sessions to prioritize features.. Agile frameworks involve regular stakeholder feedback and iterative prioritization, which effectively addresses conflicting interests in a time-sensitive environment. Option A (RACI matrix) clarifies roles but does not prioritize conflicting needs. Option B (cost-benefit analysis) is a single analysis tool, not a framework for ongoing engagement. Option D (Waterfall) locks in requirements early, which is too inflexible for resolving conflicts quickly.

Answer

Create a RACI matrix to clarify stakeholders' roles and responsibilities.

Answer

Perform a detailed cost-benefit analysis to determine the best technical solution.

Answer

Propose a Waterfall approach to finalize all requirements upfront and avoid changes.

Question 8

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?

Accepted Answer

Review the enterprise's business analysis framework and adjust the requirements process to comply with it.. 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.

Answer

Immediately implement a change control process to manage scope changes.

Answer

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

Answer

Update the requirements documentation to include a traceability matrix.

Question 9

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

Accepted Answer

Context diagram. The context diagram is the most appropriate artifact for documenting the high-level boundaries and capabilities of a solution during the planning phase. It visually represents the system as a single process, its external entities (actors), and the data flows between them, clearly defining what is inside and outside the solution scope. This aligns with the business analyst's need to capture the solution's scope boundaries without detailing internal processes.

Answer

User stories

Answer

Business case

Answer

Work breakdown structure (WBS)

Question 10

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

Accepted Answer

Conduct a feasibility study to evaluate trade-offs and present options.. Conducting a feasibility study allows the business analyst to objectively evaluate trade-offs between Requirement X (regulatory compliance) and Requirement Y (user efficiency) within the tight timeline. This approach provides data-driven options (e.g., scope adjustments, resource reallocation) to the project sponsor, enabling an informed decision without prematurely sacrificing either requirement or escalating unnecessarily. It aligns with the BABOK® Guide's principle of collaborative decision-making through analysis rather than assumption.

Answer

Prioritize Requirement X because it is regulatory, and defer Requirement Y.

Answer

Escalate to the steering committee for a decision.

Answer

Include both requirements and extend the project deadline.

Question 11

A business analyst is using a business analysis framework to identify stakeholders. Which technique is most effective for ensuring all affected parties are considered?

Accepted Answer

Creating a stakeholder map and validating with experts. Stakeholder mapping, when validated with experts, systematically identifies all affected parties by visually representing relationships, influence, and impact. This technique leverages expert judgment to cross-check the map against organizational knowledge, ensuring no stakeholder group is overlooked. It is more comprehensive than ad-hoc methods because it follows a structured framework (e.g., PMI's stakeholder identification process) and incorporates validation to fill gaps.

Answer

Brainstorming with the project team

Answer

Conducting one-on-one interviews with known stakeholders

Answer

Distributing a questionnaire to the organization

Question 12

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

Accepted Answer

Document the conflict, analyze trade-offs, and facilitate a decision with stakeholders.. The business analyst's role in requirements validation includes documenting conflicts, analyzing trade-offs (e.g., cost, schedule, technical feasibility), and facilitating a decision among stakeholders. This aligns with the BABOK® Guide's requirement for collaborative decision-making, ensuring that the project manager's desire to meet customer expectations is balanced against the system constraint through an informed, consensus-driven process.

Answer

Escalate directly to the project sponsor.

Answer

Modify the requirement to avoid the constraint without informing stakeholders.

Answer

Accept the project manager's decision and proceed.

Question 13

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?

Accepted Answer

Number of requirements defects found post-implementation. 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.

Answer

Schedule variance

Answer

Number of requirements traced to test cases

Answer

Stakeholder satisfaction survey results

Question 14

A business analyst is selecting a business analysis framework for a small project with limited budget. Which framework characteristic is most important to consider?

Accepted Answer

Scalability to fit the project size and complexity. For a small project with a limited budget, the most important characteristic of a business analysis framework is scalability, because it allows the framework to be tailored to the project's size and complexity without incurring unnecessary overhead or costs. A framework that is too rigid or comprehensive would waste resources on activities that do not add value for a small project, while a scalable approach ensures that only essential analysis tasks are performed. This directly aligns with the principle of 'just enough' business analysis, which is critical when budget constraints are tight.

Answer

Alignment with industry standards

Answer

Comprehensiveness to cover all possible scenarios

Answer

Integration with existing project management tools

Question 15

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

Accepted Answer

Business analysis planning and monitoring. According to PMI's Business Analysis for Practitioners: A Practice Guide, the core components of a business analysis framework are the five domains: Business Analysis Planning and Monitoring, Elicitation and Collaboration, Requirements Life Cycle Management, Strategy Analysis, and Requirements Analysis and Design Definition. Option A is correct because Business Analysis Planning and Monitoring is the domain that defines how business analysis activities will be executed, including stakeholder analysis, planning deliverables, and establishing governance. Option C is correct because Requirements Life Cycle Management covers the management of requirements from creation through retirement, including traceability, prioritization, and change control.

Answer

Stakeholder engagement

Answer

Procurement management

Answer

Risk management