CAPM Business Analysis Frameworks Practice Test 4 — 15 Questions

Question 1

During requirements elicitation, a business analyst is facing difficulty getting detailed requirements from a busy stakeholder. Which technique is most effective for quickly capturing high-level needs?

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

Accepted Answer

Prototyping. Prototyping is the most effective technique for quickly capturing high-level needs from a busy stakeholder because it provides a tangible visual model that stakeholders can react to immediately, reducing the cognitive effort required to articulate abstract requirements. A prototype (even a low-fidelity mockup) lets the stakeholder say 'yes, like that' or 'no, change this' in minutes rather than hours of discussion.

Answer

Document analysis

Answer

Brainstorming

Answer

Focus groups

Question 2

A business analyst is tasked with verifying that the solution meets the defined requirements. Which activity is part of the verification process?

Accepted Answer

Testing. Testing is a core verification activity because it evaluates whether the solution meets the specified requirements by executing it and comparing actual results to expected outcomes. Verification focuses on building the solution correctly, and testing provides objective evidence that requirements are satisfied. Peer review, quality assurance, and validation are related but not the specific activity of verifying requirements through execution.

Answer

Peer review

Answer

Quality assurance

Answer

Validation

Question 3

A business analyst is using the BABOK guide to design the business analysis approach. Which TWO of the following are key principles of the BABOK guide?

Accepted Answer

Business analysis is context-specific. BABOK principles include focusing on stakeholder collaboration and recognizing that business analysis is context-specific.

Answer

Use of a single methodology

Answer

Iterative development

Answer

Value delivery

Question 4

A business analyst is selecting a requirements elicitation technique for a complex project. Which THREE of the following are considered active elicitation techniques?

Accepted Answer

Observation. Active elicitation techniques involve direct interaction with stakeholders, such as interviews, observation, and prototyping.

Answer

Document analysis

Answer

Brainstorming

Question 5

A business analyst is planning the traceability process. According to best practices, which THREE of the following should be traced?

Accepted Answer

Requirements to test cases. Option B is correct because traceability best practice links each requirement to the test cases that verify it, ensuring every requirement is validated and coverage gaps are detectable. Option C is correct because requirements must be traced back to business objectives, demonstrating that each requirement delivers business value and aligns with the organization's goals. Option D is correct because tracing requirements to their source documents (such as the business case, stakeholder requests, or regulations) establishes the origin and rationale for each requirement, supporting change impact analysis. Options A and E are not among the standard traceability relationships emphasized by best practices: linking requirements to the project schedule is a planning activity rather than a core traceability link, and while requirements can be associated with risks, the risk register is not one of the three primary traceability targets specified here.

Answer

Requirements to project schedule

Answer

Requirements to risk register

Question 6

Refer to the exhibit. A business analyst is analyzing system failures during user acceptance testing. The error log indicates a database connection problem. Which root cause should the analyst investigate first?

Accepted Answer

Network connectivity issue. The 'Communications link failure' error typically indicates a network issue between the application and database server, so network connectivity should be checked first.

Answer

Application server overload

Answer

Incorrect JDBC driver

Answer

Database server is down

Question 7

A business analyst is evaluating a proposed solution and needs to determine if it delivers the expected business value. Which tool is most appropriate for this analysis?

Accepted Answer

Benefits realization plan. A benefits realization plan defines how and when the expected business value of a solution will be measured after delivery, making it the appropriate tool to determine whether the solution actually delivers the intended benefits. It links benefits to metrics, owners, and timelines for post-implementation evaluation.

Answer

Decision matrix

Answer

Requirements traceability matrix

Answer

Cost-benefit analysis

Question 8

Which TWO of the following are considered business analysis planning activities?

Accepted Answer

Conducting stakeholder analysis. Conducting stakeholder analysis (D) is a business analysis planning activity because it identifies the stakeholders, their influence, and their needs, which determines how they will be engaged throughout the initiative. Selecting elicitation techniques (E) is also a planning activity since it decides in advance which methods (interviews, workshops, surveys, observation, etc.) will be used to gather requirements. In contrast, conducting interviews to gather requirements (A) is an elicitation execution activity, not planning. Developing wireframes for the user interface (B) is a design activity, and defining project success criteria (C) is a project management or business case activity rather than a core business analysis planning task.

Answer

Conducting interviews to gather requirements

Answer

Developing wireframes for the user interface

Answer

Defining project success criteria

Question 9

Which TWO of the following are outputs of the requirements management process?

Accepted Answer

Requirements management plan. The requirements management process produces the requirements management plan (C), which documents how requirements will be elicited, analyzed, documented, prioritized, and controlled throughout the project, and the requirements traceability matrix (D), which links each requirement to its source and tracks it through design, development, and testing to ensure coverage and manage changes. Both are standard outputs of the PMBOK-aligned requirements management effort, since planning how to manage requirements and then tracing them are core deliverables of that process. The solution design specification (A) belongs to design/development activities rather than requirements management, the project scope statement (B) is an output of scope definition (part of project scope management, not the requirements management process itself), and the business case (E) is a pre-project document created during project initiation to justify the investment, not an output of requirements management.

Answer

Solution design specification

Answer

Project scope statement

Answer

Business case

Question 10

Which THREE of the following are characteristics of effective business requirements?

Accepted Answer

Unambiguous. Option C (Unambiguous) is correct because an effective business requirement must have only one possible interpretation, so stakeholders, analysts, and developers all understand the same intended outcome without guessing. Option D (Consistent across other requirements) is correct because requirements must not conflict with one another; a requirement that contradicts another requirement creates scope confusion and cannot be implemented reliably. Option E (Testable) is correct because a requirement must be verifiable through a defined test, acceptance criterion, or measurable condition so that completion can be objectively confirmed. Option A (Atomic) is not marked correct here even though atomicity is often desirable, because the question's intended answer set does not include it. Option B (Feasible within project constraints) is also not marked correct, since feasibility is a validation concern but is not one of the three characteristics selected in this scenario.

Answer

Atomic (cannot be broken further)

Answer

Feasible within project constraints

Question 11

Based on the exhibit, which requirement poses the greatest risk to the project if not addressed?

Accepted Answer

REQ-002, because it is still in Draft status. Requirements still in Draft status have not been baselined or approved, meaning their scope, acceptance criteria, and feasibility are unsettled — this uncertainty poses the greatest risk to the project. Verified requirements have already been validated, and unverified requirements are less risky than draft ones because they are at least defined. Therefore REQ-002 in Draft status is the greatest risk.

Answer

REQ-001, because it is not verified

Answer

REQ-003, because it is already verified

Answer

All requirements are equally risky

Question 12

According to the stakeholder analysis exhibit, which stakeholder should the business analyst involve in detailed requirements reviews?

Accepted Answer

Jane Doe. The stakeholder analysis exhibit identifies Jane Doe as the stakeholder with the appropriate interest/influence profile for detailed requirements reviews. Detailed requirements reviews require a stakeholder who is both highly interested and highly influential in the requirements domain, which the exhibit attributes to Jane Doe. Alice Jones and Bob Smith have profiles that make them unsuitable for this level of engagement.

Answer

Alice Jones

Answer

Bob Smith

Answer

All three

Question 13

A global retail company is implementing a new e-commerce platform to replace a legacy system. The business analysis team has identified the following: The legacy system has been customized over 10 years, resulting in many undocumented business rules. The project timeline is aggressive (6 months), and the budget is fixed. The project sponsor insists on using an agile methodology to deliver quickly. The core team includes business analysts, developers, and testers, but the key business stakeholders (e.g., from merchandising, logistics, and customer service) are only available for one hour per week due to their operational roles. After the first sprint review, stakeholders expressed dissatisfaction that the delivered features do not match their expectations. The product owner is overwhelmed and struggles to prioritize the backlog. The business analysts notice that many requirements are still ambiguous and that the stakeholder feedback is inconsistent across different departments. The project is at risk of delivering a solution that does not meet business needs. What is the most effective course of action for the business analysts to take at this point?

Accepted Answer

Negotiate with the sponsor and stakeholders to extend the sprint duration to two weeks and require a minimum of three hours per week from key stakeholders. The core issue is insufficient stakeholder availability and unclear requirements, which led to misalignment. Extending sprint duration and requiring more stakeholder time directly addresses the root cause by improving communication and feedback loops. This is the most effective action because it enables the team to clarify ambiguous requirements and align with business expectations, which is critical in an agile project with fixed budget and timeline.

Answer

Immediately reduce the project scope to the most essential features and accelerate the next sprint

Answer

Conduct a series of observation sessions in the stores and warehouses to uncover undocumented business rules

Answer

Request that the project sponsor approve a shift to a predictive (waterfall) lifecycle to define all requirements upfront

Question 14

A company is considering implementing a new customer relationship management (CRM) system. The business analyst conducts a needs assessment to identify business gaps and opportunities. What is the primary output of a needs assessment?

Accepted Answer

Business case. The primary output of a needs assessment is the business case, which documents the justification for the proposed change by identifying business gaps and opportunities. The needs assessment feeds directly into the business case, which then supports the decision to initiate a project. Stakeholder register, project charter, and requirements documentation are downstream artifacts created after the business case is approved.

Answer

Stakeholder register

Answer

Project charter

Answer

Requirements documentation

Question 15

A project manager and a business analyst disagree on the level of detail required for requirements documentation. The project manager wants high-level user stories, while the business analyst insists on detailed functional specifications. Which document should define the approach for requirements management?

Accepted Answer

Business analysis plan. The business analysis plan (or requirements management plan) defines the level of detail and approach for requirements activities. The project management plan is broader, scope statement defines what is in scope, and the requirements traceability matrix is a tool, not a plan.

Answer

Project management plan

Answer

Requirements traceability matrix

Answer

Scope statement