CAPM Business Analysis Frameworks Practice Test 11 — 15 Questions

Question 1

A business analyst is planning stakeholder engagement for a new regulatory compliance project. To ensure stakeholder buy-in and minimize risks, when should the business analyst involve key stakeholders?

Accepted Answer

Early and continuously throughout the project. Engaging stakeholders early and often is a best practice to gather accurate requirements, manage expectations, and reduce risks. Involving them only at sign-off or after development leads to rework and dissatisfaction.

Answer

Only during requirements gathering

Answer

Only at project sign-off

Answer

After the solution is developed

Question 2

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?

Accepted Answer

To ensure each requirement meets a business need. 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.

Answer

To document system architecture

Answer

To assign requirements to team members

Answer

To estimate project costs

Question 3

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?

Accepted Answer

Validation. Validation ensures the right product is built, often through demonstration and feedback. Verification checks if the product is built correctly. Prototyping is a validation technique to confirm requirements meet user needs.

Answer

Quality assurance

Answer

Peer review

Answer

Verification

Question 4

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?

Accepted Answer

Survey / Questionnaire. Surveys are cost-effective for collecting data from many stakeholders across locations. Focus groups and interviews are more resource-intensive and work better with smaller groups. Observation requires physical presence.

Answer

Focus groups

Answer

One-on-one interviews

Answer

Observation

Question 5

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?

Accepted Answer

It provides a structured approach to business analysis. A framework provides a structured, consistent approach to business analysis activities, improving quality, communication, and alignment with project goals. It does not guarantee faster delivery or eliminate all risks, and it is not limited to large projects.

Answer

It guarantees faster project delivery

Answer

It is only useful for large-scale projects

Answer

It eliminates the need for stakeholder communication

Question 6

Before approving a major IT system upgrade, the steering committee wants to understand whether the proposed solution is technically feasible and aligns with the organization's strategic goals. The business analyst should recommend conducting which type of analysis?

Accepted Answer

Feasibility study. A feasibility study assesses technical, economic, and operational viability before committing to a project. A business case is built after feasibility; ROI analysis is part of the business case; SWOT analysis is for strategic positioning.

Answer

Business case development

Answer

Return on investment (ROI) analysis

Answer

SWOT analysis

Question 7

Which TWO of the following are techniques used for requirements elicitation?

Accepted Answer

Benchmarking. Benchmarking and focus groups are both elicitation techniques used to gather requirements from stakeholders. Pareto analysis and decision tree are used for analysis, and SWOT is for strategic planning.

Answer

Pareto analysis

Answer

Decision tree

Answer

SWOT analysis

Question 8

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

Accepted Answer

Alternatives analysis. A business case includes the problem statement, cost-benefit analysis, and alternatives analysis to justify the project. Risk register and stakeholder list are separate documents that inform but are not core parts of the business case.

Answer

Stakeholder list

Answer

Risk register

Question 9

Which TWO of the following are key elements of a requirements management plan?

Accepted Answer

Change control process for requirements. The requirements management plan includes the traceability matrix and the change control process to manage requirements throughout the project. System design documents, test cases, and user stories are outputs or artifacts, not elements of the plan itself.

Answer

User stories

Answer

System design documents

Answer

Test cases

Question 10

You are a business analyst assigned to a project that aims to streamline the inventory management process for a mid-sized retail company. The project sponsor has verbally described the need for a new system but has not provided any formal documentation. During the kickoff meeting, the project manager asks you to start eliciting requirements immediately. However, you notice that there is no business case or project charter. The sponsor is not available to provide additional information until next week. The project manager is eager to show progress to stakeholders and wants to begin gathering requirements from users today. What should you do first?

Accepted Answer

Develop a business case based on the initial discussion with the sponsor and present it for approval before proceeding with requirements elicitation.. Without a business case, there is no justification or scope for the project. The business analyst should develop a business case based on the initial discussion to ensure the project aligns with organizational goals. Starting requirements without a business case risks scope creep and wasted effort. Asking the sponsor again may delay, but the sponsor is unavailable. Starting requirements immediately is premature. Escalating to the project manager is not productive as they already want to start.

Answer

Begin requirements elicitation with users as requested, and document assumptions about the business case for later validation.

Answer

Ask the project manager to obtain the business case from the sponsor before starting any requirements work.

Answer

Escalate the issue to the steering committee for a decision on whether to proceed without a business case.

Question 11

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?

Accepted Answer

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.. When a key stakeholder is unavailable, it is a recognized practice to document assumptions about their requirements and plan to validate later. This keeps the project on schedule while acknowledging the risk. Conducting a survey may face resistance, delaying elicitation. Delaying the entire project is not justified for one stakeholder. Using existing documentation is useful but may not capture all needs.

Answer

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

Answer

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

Answer

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

Question 12

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?

Accepted Answer

Document the conflict and escalate to the steering committee for a decision on how to resolve the inconsistency.. 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.

Answer

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

Answer

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

Answer

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

Question 13

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?

Accepted Answer

Agile (Scrum). Agile (Option C) is correct because it accommodates changing requirements through iterative development and continuous feedback. Waterfall (A) assumes fixed requirements, Six Sigma (B) focuses on process improvement, and PRINCE2 (D) is a project management method, not a business analysis framework.

Answer

Waterfall

Answer

PRINCE2

Answer

Six Sigma

Question 14

A business analyst is working on a regulatory compliance project with many diverse stakeholders. The analyst needs to categorize stakeholders based on their interest and influence to prioritize engagement. Which tool should the analyst use?

Accepted Answer

Power/Interest Grid. The Power/Interest Grid (Option A) is correct as it classifies stakeholders by power and interest to tailor engagement. RACI (B) defines roles, Stakeholder Register (C) lists stakeholders without categorization, and SWOT (D) analyzes strengths, weaknesses, opportunities, threats.

Answer

SWOT Analysis

Answer

RACI Matrix

Answer

Stakeholder Register

Question 15

Which TWO of the following are commonly used requirements elicitation techniques?

Accepted Answer

Prototyping. Brainstorming and Prototyping are direct elicitation techniques. Variance Analysis, Monte Carlo Simulation, and Parametric Estimating are from other knowledge areas (monitoring, risk, cost).

Answer

Monte Carlo Simulation

Answer

Parametric Estimating

Answer

Variance Analysis