CAPM Business Analysis Frameworks Practice Test 3 — 15 Questions

Question 1

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?

Accepted Answer

An entity-relationship diagram. 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.

Answer

A context diagram

Answer

A user story map

Answer

A use case diagram

Question 2

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?

Accepted Answer

Facilitate a meeting with stakeholders to discuss trade-offs and prioritize requirements.. Option B is correct because 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.

Answer

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

Answer

Remove the conflicting requirements and proceed with the remaining ones.

Answer

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

Question 3

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

Accepted Answer

Business rules catalog. The business rules catalog is a key technique for requirements traceability because it documents and links business rules to their origin, implementation, and validation points, ensuring each rule can be traced back to a stakeholder need or regulatory requirement. This supports impact analysis and compliance verification throughout the project lifecycle.

Answer

Data flow diagram

Answer

Use case description

Answer

User stories

Question 4

Which THREE factors should a business analyst consider when selecting an elicitation technique for a project?

Accepted Answer

Availability of stakeholders. A is correct because stakeholder availability directly impacts the feasibility of scheduling and conducting elicitation activities such as interviews, workshops, or focus groups. If key stakeholders are unavailable, the chosen technique may be impractical or yield incomplete information, making this a primary logistical consideration in technique selection.

Answer

Project manager's preference

Answer

Cost of the technique

Question 5

A project involves upgrading a legacy financial reporting system. The business analyst (BA) has been assigned to elicit requirements. The BA schedules a series of one-on-one interviews with key stakeholders, but after three interviews, the BA notices that stakeholders are providing inconsistent information. The BA suspects that some stakeholders have hidden agendas and are reluctant to share complete details. The BA recalls that the project sponsor emphasized the need for a comprehensive and accurate requirements set. The BA has limited time and budget. What should the BA do next?

Accepted Answer

Organize a facilitated workshop with all stakeholders to discuss requirements collaboratively.. A facilitated workshop is the best approach because it creates a collaborative environment where stakeholders can discuss requirements openly, helping to surface hidden agendas and resolve inconsistencies. This technique is more efficient than one-on-one interviews for building consensus and ensuring comprehensive requirements, especially given the limited time and budget.

Answer

Continue with one-on-one interviews but ask more probing questions.

Answer

Escalate the issue to the project sponsor and ask for direction.

Answer

Review existing documentation such as the system design specification to infer requirements.

Question 6

A business analyst is working on a project to develop a mobile banking application. During the requirements analysis phase, the BA creates a set of user stories and acceptance criteria. The BA then conducts a peer review with the development team. The team points out that the stories are too large and vague to estimate. The BA needs to refine the requirements to make them actionable. The project is using an agile methodology with two-week sprints. What should the BA do?

Accepted Answer

Split the large user stories into smaller, more specific stories with acceptance criteria.. In agile methodologies, user stories must be small enough to fit within a single sprint and provide clear, testable acceptance criteria for estimation and development. Splitting large, vague stories into smaller, specific stories with acceptance criteria directly addresses the team's inability to estimate, enabling accurate sprint planning and incremental delivery. This aligns with the INVEST principle (Independent, Negotiable, Valuable, Estimable, Small, Testable) for effective user stories.

Answer

Add more detail to the existing user stories and acceptance criteria.

Answer

Create a prototype to clarify requirements and then rewrite stories.

Answer

Ask the development team to re-estimate the stories as they are.

Question 7

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

Accepted Answer

Agile framework. The Agile framework is the correct choice because it emphasizes iterative development, frequent stakeholder collaboration, and adaptive planning, which are ideal for a project with distributed stakeholders across time zones. Agile practices such as daily stand-ups, sprint reviews, and backlog refinement allow for efficient requirements elicitation and ensure all stakeholders can provide input asynchronously or during synchronized ceremonies, accommodating varying availability.

Answer

Lean framework

Answer

Six Sigma framework

Answer

Waterfall framework

Question 8

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

Question 9

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

Question 10

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

Question 11

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

Question 12

Match each knowledge area to its primary process.

Question 13

Match each earned value management term to its formula.

Question 14

Match each risk response strategy to its action.

Question 15

Match each communication method to its characteristic.