29 of 179 questions · Page 3/3 · Business Analysis Frameworks topic · Answers revealed
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?
Agile supports iterative delivery and quick adaptation.
Why this answer
Agile is designed for rapid iteration and adaptability to changing requirements.
Which TWO statements accurately describe the role of a business analyst in requirements management?
Aligning requirements to business goals is a key BA responsibility.
Why this answer
Option B is correct because the business analyst (BA) is responsible for ensuring that each requirement directly supports the stated business objectives and strategic goals. This alignment is a core function of requirements management within the BABOK framework, as it prevents scope creep and ensures that delivered features provide measurable business value.
Exam trap
PMI often tests the distinction between the BA's role in eliciting and managing requirements versus the authority to approve or design technical solutions, leading candidates to incorrectly select options that conflate these responsibilities.
Refer to the exhibit. Which critical element is missing from this business case?
Alternatives analysis is essential to demonstrate that other options were evaluated.
Why this answer
The business case is missing a comparison of alternatives considered. A business case must justify why the selected approach is the best option, which requires evaluating at least one alternative (e.g., build vs. buy, different technical solutions). Without this, stakeholders cannot assess whether the recommended solution is optimal or cost-effective.
Exam trap
PMI often tests the misconception that a business case is just a high-level summary, but PMI requires it to include alternatives considered to demonstrate objective decision-making.
How to eliminate wrong answers
Option A is wrong because the project sponsor is typically identified later in the project charter, not as a required element of the business case; the business case focuses on justification, not governance roles. Option B is wrong because a detailed schedule belongs to the project management plan, not the business case; the business case only needs high-level timeframes or milestones. Option D is wrong because a risk mitigation plan is part of risk management planning, not the business case; the business case may mention key risks but does not require a full mitigation plan.
During requirements elicitation, the team discovers conflicting needs from two key stakeholders. The project manager asks the business analyst to use a prioritization technique that allows stakeholders to vote anonymously to reach consensus. Which technique should be used?
Correct: Delphi uses anonymous rounds to build consensus.
Why this answer
The Delphi Technique involves anonymous voting rounds to achieve consensus. MoSCoW is a prioritization but not anonymous, Multi-criteria Decision Analysis does not involve voting, and Voting (Roman Vote) is open.
Which of the following is a key output of the needs assessment process?
Correct: Business case is the main output of needs assessment.
Why this answer
The needs assessment process results in a business case that defines the business need and recommended solution. Project Charter authorizes the project, Requirements Documentation details requirements, and Stakeholder Register lists stakeholders.
During a requirements elicitation meeting, stakeholders provide conflicting information about the desired functionality. What is the best course of action for the business analyst?
Facilitation helps clarify and resolve conflicting requirements.
Why this answer
Option C is correct because the business analyst's primary role is to facilitate stakeholder collaboration and resolve conflicts through structured discussion, ensuring that requirements are accurate and agreed upon before development begins. This aligns with the BABOK guide's emphasis on using techniques like workshops or brainstorming to achieve consensus, which prevents costly rework later.
Exam trap
The trap here is that candidates often confuse the business analyst's role with that of a project manager or decision-maker, assuming escalation or authoritative resolution is appropriate, when in fact the BA must facilitate consensus among stakeholders.
How to eliminate wrong answers
Option A is wrong because documenting conflicting information without resolution leads to ambiguous requirements, causing development to proceed on unstable foundations and likely resulting in a product that fails to meet stakeholder needs. Option B is wrong because escalating to senior management bypasses the business analyst's responsibility to facilitate resolution at the stakeholder level, and senior management may lack the detailed domain knowledge to make informed decisions about functionality. Option D is wrong because asking the project manager to decide which stakeholder is correct undermines collaborative decision-making and may create resentment, as the project manager is not typically a domain expert in the specific functionality being discussed.
During stakeholder analysis, a business analyst identifies a key stakeholder who rarely speaks in meetings but provides detailed written feedback. Which engagement strategy is most appropriate?
Surveys allow the stakeholder to provide detailed feedback in writing, matching their preference.
Why this answer
Option C is correct because this stakeholder prefers asynchronous communication. Option A is wrong because one-on-one meetings might be intimidating. Option B is wrong because ignoring them loses valuable input.
Option D is wrong because email-only may not be sufficient for complex topics.
A business analyst is working on a project to implement a new inventory management system. The project charter has been approved, and the project manager has asked the analyst to begin requirements elicitation. The analyst notices that the business case did not include a clear problem statement or measurable objectives. Several stakeholders are uncertain about the project's purpose and expected outcomes. The project sponsor is eager to move forward. As the business analyst, what should you do first?
A solid business case provides direction and success criteria for all subsequent activities.
Why this answer
Option B is correct because a clear problem statement and measurable objectives are foundational; revisiting the business case ensures alignment before elicitation. Option A skips essential groundwork. Option C is premature without objectives.
Option D focuses on team roles, not the core issue.
Which THREE techniques are commonly used for requirements elicitation?
Surveys can gather requirements from a large number of stakeholders.
Why this answer
Surveys are a common requirements elicitation technique because they allow the business analyst to collect information from a large number of stakeholders efficiently, especially when stakeholders are geographically dispersed. They are structured and can include both closed-ended and open-ended questions to gather quantitative and qualitative data.
Exam trap
PMI often tests the distinction between requirements elicitation techniques and project management tools, so candidates mistakenly select SWOT analysis or Gantt charts because they are familiar terms, even though they are not used for eliciting requirements.
A BA is identifying stakeholders. Which TWO techniques are commonly used for stakeholder analysis?
Classifies stakeholders by power and interest.
Why this answer
Options A and C are correct because power/interest grid and influence/impact grid are stakeholder classification techniques. Option B is incorrect because traceability matrix is for requirements. Option D is incorrect because WBS is for scope decomposition.
Option E is incorrect because mind mapping is for brainstorming.
After solution implementation, the business analyst discovers that a key performance indicator (KPI) has not improved as expected. What is the most appropriate next step?
Root cause analysis guides corrective actions.
Why this answer
Option B is correct because root cause analysis helps identify why the solution is underperforming. Option A is wrong documenting in lessons learned without action is inadequate. Option C is wrong escalation without analysis is premature.
Option D is wrong requesting budget for a new solution is not justified without understanding the issue.
Which THREE elements should be included in a needs assessment? (Choose three.)
Needs must align with goals.
Why this answer
Correct are A (Current state analysis), C (Business goals), and D (Problem statement). B is a solution, not needs assessment. E is a requirement detail.
A business analyst is tasked with verifying that the solution meets the defined requirements. Which activity is part of the verification process?
Testing directly verifies that the solution meets requirements.
Why this answer
Testing is a key verification activity that checks if the solution conforms to specified requirements.
A project manager is leading a business analysis effort to define the requirements for a new inventory management system. The stakeholders have conflicting needs regarding real-time data updates versus batch processing. Which business analysis technique should the PM use to facilitate a decision?
Decision trees evaluate consequences of different decisions, helping stakeholders choose.
Why this answer
Option C is correct because a decision tree is a structured business analysis technique that evaluates the trade-offs between conflicting stakeholder requirements—in this case, real-time data updates versus batch processing—by quantifying the impact of each approach on project cost and timeline. This enables the project manager to facilitate an objective, data-driven decision rather than relying on subjective preferences.
Exam trap
The trap here is that candidates confuse requirement elicitation or documentation techniques (like process flow diagrams or validation workshops) with analytical decision-making tools, assuming any stakeholder conflict is resolved by gathering more requirements rather than by quantitatively comparing the impacts of each option.
How to eliminate wrong answers
Option A is wrong because developing a process flow diagram maps the current inventory process, which documents existing workflows but does not analyze the cost or schedule implications of the two conflicting technical approaches. Option B is wrong because a Gantt chart is a project scheduling tool used to plan and track requirement gathering activities, not a technique for evaluating trade-offs between real-time and batch processing. Option D is wrong because a requirements validation workshop reviews and confirms that requirements are complete and correct, but it does not provide a quantitative analysis of cost and timeline impacts needed to resolve the conflict between real-time updates and batch processing.
A business analyst is evaluating whether a proposed solution aligns with the organization's strategic goals. Which business analysis technique should be used?
SWOT analysis helps evaluate strategic alignment by examining internal and external factors.
Why this answer
SWOT analysis (Strengths, Weaknesses, Opportunities, Threats) is the correct technique because it directly evaluates how a proposed solution aligns with the organization's strategic goals by examining internal capabilities and external market factors. This technique helps the business analyst determine whether the solution leverages organizational strengths and opportunities while mitigating weaknesses and threats, ensuring strategic fit.
Exam trap
The trap here is that candidates often confuse SWOT analysis with gap analysis, assuming both assess alignment, but gap analysis focuses on performance discrepancies rather than strategic fit with organizational goals.
How to eliminate wrong answers
Option A is wrong because MoSCoW analysis (Must have, Should have, Could have, Won't have) is a prioritization technique used to categorize requirements, not to assess alignment with strategic goals. Option B is wrong because gap analysis identifies the difference between the current state and desired future state, but it does not directly evaluate strategic alignment with organizational goals. Option C is wrong because a feasibility study assesses whether a solution is technically, operationally, and economically viable, but it does not specifically measure alignment with strategic objectives.
A business analyst discovers that two requirements conflict with each other. What is the best strategy to resolve this conflict?
Collaborative negotiation is the best approach to resolve conflicts.
Why this answer
Option B is correct because involving stakeholders who own the requirements facilitates negotiation. A is wrong because ignoring leads to issues later. C is wrong because adding new requirement doesn't resolve.
D is wrong because voting may not address underlying conflict.
Refer to the exhibit. The business analyst is analyzing system requirements for a payment gateway. Based on this error log, which non-functional requirement is most likely to be updated?
Correct: Timeout is a performance attribute.
Why this answer
The error describes a transaction timeout, which relates to system performance. Therefore, the performance requirement for timeout threshold should be reviewed and potentially increased.
A project manager is defining the business analysis approach for a new software development project. The stakeholders are located in different countries and have varying levels of technical expertise. Which business analysis framework is most suitable for ensuring effective communication and collaboration?
Agile promotes continuous collaboration and adaptability.
Why this answer
Agile emphasizes iterative communication and collaboration, making it ideal for distributed teams with diverse expertise.
Which TWO of the following are commonly used requirements elicitation techniques?
Prototyping allows stakeholders to interact with a model to refine requirements.
Why this answer
Brainstorming and Prototyping are direct elicitation techniques. Variance Analysis, Monte Carlo Simulation, and Parametric Estimating are from other knowledge areas (monitoring, risk, cost).
Refer to the exhibit. A business analyst has documented the current and target states for invoice processing. What business analysis technique is being used?
Gap analysis compares current and desired states to identify differences.
Why this answer
The business analyst is comparing the current state and target state of invoice processing to identify the differences or gaps that need to be addressed. This is the core definition of gap analysis, which is a technique used to determine the steps required to move from the current state to the desired future state. The exhibit explicitly shows a 'Current State' and 'Target State' for invoice processing, making gap analysis the correct technique.
Exam trap
The trap here is that candidates may confuse gap analysis with root cause analysis because both involve analyzing problems, but gap analysis focuses on the difference between current and target states, while root cause analysis digs into the origin of a single problem.
How to eliminate wrong answers
Option A is wrong because a feasibility study assesses whether a project or solution is viable in terms of cost, time, and resources, not by comparing current and target states. Option B is wrong because SWOT analysis evaluates internal Strengths and Weaknesses and external Opportunities and Threats, not a direct comparison of current and target process states. Option D is wrong because root cause analysis is used to identify the underlying cause of a problem or defect, not to document the difference between current and target states.
Refer to the exhibit. Based on the server health check, which requirement is most likely to be triggered?
Correct: Disk usage at 92% with critical error.
Why this answer
The error message indicates a critical disk space issue on /var/log, so expanding disk space is the most likely requirement. CPU and memory are within normal ranges, and replacing the server is premature.
A business analyst is selecting a business analysis framework for a small project with limited budget. Which framework characteristic is most important to consider?
Scalability allows the framework to be adapted without waste.
Why this answer
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.
Exam trap
The trap here is that candidates often choose 'comprehensiveness' (Option C) because they assume a framework must cover all scenarios to be effective, but the CAPM exam tests the understanding that frameworks must be tailored to project constraints, and for a small budget, scalability is the key enabler of cost efficiency.
How to eliminate wrong answers
Option B is wrong because alignment with industry standards, while beneficial for consistency and interoperability, is not the most critical factor when budget is limited; a small project can still succeed without strict adherence to standards if the framework is scalable. Option C is wrong because comprehensiveness to cover all possible scenarios would introduce excessive documentation and analysis activities, driving up costs and time, which is counterproductive for a small project with a limited budget. Option D is wrong because integration with existing project management tools is a convenience feature, not a primary driver; a scalable framework can be adapted to work with minimal tooling, and forcing integration could add unnecessary expense.
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?
Splitting stories makes them estimable and sprint-ready.
Why this answer
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.
Exam trap
PMI often tests the misconception that adding more detail or creating a prototype is sufficient to make stories actionable, but the core agile requirement is that stories must be small enough to be estimable and completed within a single sprint.
How to eliminate wrong answers
Option B is wrong because simply adding more detail to existing large stories does not reduce their size; they remain too large for a two-week sprint and still cannot be reliably estimated. Option C is wrong because creating a prototype is a discovery technique that may clarify requirements but does not inherently produce actionable, estimable user stories; it adds an extra step and delays refinement. Option D is wrong because asking the team to re-estimate stories that are known to be too large and vague will yield unreliable estimates, violating the core agile principle that stories must be estimable to be planned.
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?
Feasibility study evaluates viability before significant investment.
Why this answer
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.
In a project to implement a new customer relationship management (CRM) system, the business analyst needs to understand the current workflows and identify areas for improvement. Which technique should be used?
Process modeling captures current workflows and identifies improvement opportunities.
Why this answer
Process modeling is the correct technique because it visually maps out the current workflows, showing the sequence of activities, decision points, and handoffs in the CRM system. This allows the business analyst to identify inefficiencies, bottlenecks, and areas for improvement in the existing processes before designing the new system.
Exam trap
The trap here is that candidates often confuse 'document analysis' (reviewing existing materials) with 'process modeling' (creating a visual representation of workflows), leading them to pick A when the question specifically asks for a technique to understand and improve workflows.
How to eliminate wrong answers
Option A is wrong because document analysis involves reviewing existing documentation (e.g., user manuals, process documents) to gather information, but it does not actively model or visualize workflows to identify improvement areas. Option C is wrong because benchmarking compares performance metrics against industry standards or competitors, which is useful for setting targets but not for understanding current internal workflows. Option D is wrong because root cause analysis is used to identify the underlying causes of a specific problem or defect, not to map and analyze entire workflows for improvement.
Which TWO of the following are considered business analysis planning activities?
Stakeholder analysis is a key planning activity.
Why this answer
Options A and C are correct because business analysis planning includes selecting techniques (A) and conducting stakeholder analysis (C). B is solution design, D is elicitation execution, E is project selection.
A business analyst is using a business analysis framework to identify stakeholders. Which technique is most effective for ensuring all affected parties are considered?
A stakeholder map systematically identifies and categorizes stakeholders.
Why this answer
Option C is correct because 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.
Exam trap
The trap here is that candidates confuse 'brainstorming' (Option A) as a comprehensive technique, but the CAPM exam requires a structured, validated approach (stakeholder mapping with expert validation) to ensure all affected parties are considered, not just those immediately visible.
How to eliminate wrong answers
Option A is wrong because brainstorming with the project team is unstructured and relies on the team's limited perspective, often missing stakeholders outside their immediate awareness (e.g., regulatory bodies or downstream users). Option B is wrong because one-on-one interviews with known stakeholders only capture their personal views, creating a snowball effect that may still miss indirect or marginalized stakeholders not in the interviewee's network. Option D is wrong because distributing a questionnaire to the organization is passive and relies on self-identification, which can lead to low response rates and overlook stakeholders who do not see themselves as affected (e.g., future users or external auditors).
A business analyst is working on a project to implement a new human resources software. The project is using an Agile framework with two-week sprints. After three sprints, the product owner is frustrated because the team has not delivered any working functionality that can be demoed. The business analyst realizes that the user stories lack acceptance criteria and are too large to complete in a sprint. The team is also spending too much time on documentation. As the business analyst, what should you do to improve the situation?
Smaller stories with acceptance criteria are easier to estimate and demonstrate.
Why this answer
Option B is correct because decomposing stories and adding acceptance criteria improves clarity and delivery. Option A ignores root causes. Option C lengthens sprints but doesn't fix story quality.
Option D avoids the real issue.
Which THREE factors should a business analyst consider when selecting an elicitation technique for a project?
Stakeholder availability influences technique choice (e.g., workshops vs surveys).
Why this answer
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.
Exam trap
The trap here is that candidates often confuse 'project manager's preference' or 'cost' as valid selection criteria, but the CAPM exam specifically tests the BABOK's three primary factors: stakeholder availability, type of information needed, and level of detail required.
Ready to test yourself?
Try a timed practice session using only Business Analysis Frameworks questions.