View Full IIBA CBAP Exam Dumps and Practice Test Dumps

 

Question 21. A business analyst is asked to investigate a business problem, but different stakeholders describe the problem in completely different ways. What should the business analyst do first?

1. Define the solution requirements
2. Identify and analyze the underlying business need
3. Select the stakeholder with the greatest authority
4. Begin designing possible solutions

Correct Answer: 2. Identify and analyze the underlying business need

Explanation:

When stakeholders describe a problem differently, the business analyst should seek to understand the underlying business need rather than immediately accepting one stakeholder’s interpretation. The analyst should explore the symptoms, desired outcomes, causes, and organizational context through appropriate elicitation and analysis activities. This helps distinguish the actual business problem from individual perceptions or proposed solutions. Once the underlying need is understood, the analyst can establish a shared problem statement and determine what information is needed to define appropriate requirements. Starting with solution design too early can reinforce an incorrect understanding of the problem and potentially lead to an ineffective solution.

Question 22. A business analyst is determining which individuals and groups may affect or be affected by a proposed organizational change. Which activity is being performed?

1. Stakeholder identification
2. Solution evaluation
3. Requirements verification
4. Business process analysis

Correct Answer: 1. Stakeholder identification

Explanation:

Stakeholder identification involves determining the individuals, groups, or organizations that may influence, be affected by, or have an interest in a change. Identifying stakeholders early helps the business analyst understand whose perspectives, requirements, concerns, authority, and information needs should be considered. Stakeholders may include customers, employees, managers, suppliers, regulators, sponsors, or other parties depending on the initiative. Once identified, stakeholders can be analyzed further to understand their roles, influence, interests, and engagement needs. Effective stakeholder identification reduces the risk of overlooking important perspectives and supports more complete requirements and better-informed business decisions.

Question 23. A business analyst is comparing the current state of an organization with a desired future state to determine what must change to achieve the target. Which technique is most appropriate?

1. Root cause analysis
2. Decision analysis
3. Gap analysis
4. Interface analysis

Correct Answer: 3. Gap analysis

Explanation:

Gap analysis compares a current state with a desired future state to identify differences that must be addressed. The gaps may involve capabilities, processes, technology, skills, information, organizational structures, or other areas relevant to the business change. The business analyst can use the identified gaps to determine potential requirements and change needs. Root cause analysis instead investigates why a problem occurs, while decision analysis supports evaluation among alternatives. Interface analysis focuses on interactions between people, systems, or components. Gap analysis is especially useful during strategic planning, organizational transformation, and solution definition.

Question 24. A stakeholder says, “The system must be easy to use.” The development team interprets this statement differently from the business users. What should the business analyst do?

1. Accept the statement because the stakeholder provided it
2. Remove the requirement because usability cannot be measured
3. Convert the requirement directly into a technical design
4. Clarify the requirement and establish measurable acceptance criteria

Correct Answer: 4. Clarify the requirement and establish measurable acceptance criteria

Explanation:

A statement such as “easy to use” is subjective and can be interpreted differently by different stakeholders. The business analyst should clarify what usability means in the specific context and work with stakeholders to define measurable or testable criteria. These could address factors such as task completion time, number of errors, training requirements, or user satisfaction, depending on the solution. Clear acceptance criteria establish a shared understanding of what must be achieved. Simply accepting the vague statement can create disagreements during development and evaluation. Converting it directly into technical design would also be premature before the business need is sufficiently understood.

Question 25. During elicitation, a stakeholder provides information that conflicts with an existing organizational policy. What should the business analyst do?

1. Ignore the stakeholder’s information
2. Investigate the conflict and validate the information with appropriate stakeholders
3. Automatically replace the policy with the stakeholder’s preference
4. Remove the stakeholder from the analysis

Correct Answer: 2. Investigate the conflict and validate the information with appropriate stakeholders

Explanation:

Conflicting information should be investigated rather than automatically accepting one source. The business analyst should understand why the stakeholder’s information differs from the documented policy and determine whether the policy is current, whether an exception exists, or whether organizational practices have changed. Appropriate stakeholders or policy owners should be involved in validating the information. This approach helps distinguish between an actual business requirement, an operational practice, an exception, and outdated documentation. Resolving discrepancies through evidence and stakeholder confirmation improves the reliability of the analysis and prevents requirements from being based on incorrect assumptions.

Question 26. A business analyst needs to determine which proposed solution provides the greatest overall value while considering benefits, costs, risks, and other relevant factors. Which technique is most appropriate?

1. Decision analysis
2. Observation
3. Stakeholder mapping
4. Process modeling

Correct Answer: 1. Decision analysis

Explanation:

Decision analysis supports the structured evaluation of alternatives using defined criteria. A business analyst can consider factors such as expected benefits, costs, risks, feasibility, strategic alignment, and stakeholder priorities when comparing potential solutions. The purpose is to provide a transparent basis for making a decision rather than relying solely on personal preference or the opinion of one stakeholder. Observation is primarily an elicitation technique, stakeholder mapping analyzes stakeholder characteristics, and process modeling represents how activities are performed. Decision analysis is particularly useful when multiple solution alternatives exist and stakeholders need objective information to support selection.

Question 27. A business analyst is reviewing requirements and finds that two requirements describe overlapping functionality. What should the analyst do?

1. Implement both requirements without further analysis
2. Delete both requirements
3. Analyze the overlap and clarify or consolidate the requirements as appropriate
4. Give priority to the requirement written first

Correct Answer: 3. Analyze the overlap and clarify or consolidate the requirements as appropriate

Explanation:

Overlapping requirements can create duplication, conflicting interpretations, unnecessary functionality, and increased implementation costs. The business analyst should examine the relationship between the requirements and determine whether they represent the same need, related needs, or intentionally separate capabilities. Stakeholders should be consulted to clarify the intended outcomes. If the requirements are redundant, they may be consolidated or one may be removed through the appropriate requirements management process. Automatically implementing both can introduce unnecessary scope, while deleting both could remove legitimate business needs. Careful analysis preserves required functionality while improving clarity and consistency.

Question 28. A business analyst is working with several stakeholder groups that use different business processes for similar activities. What should the analyst do to understand the differences before recommending a change?

1. Standardize all processes immediately
2. Document only the process used by senior management
3. Select the process that appears fastest
4. Model and analyze the current processes and their variations

Correct Answer: 4. Model and analyze the current processes and their variations

Explanation:

When similar activities are performed differently, the analyst should first understand the current state and the reasons for the variations. Modeling the processes can reveal differences in activities, decisions, roles, inputs, outputs, controls, and exceptions. Stakeholder discussions can then help explain why particular variations exist and whether they are intentional or caused by inefficiencies. Standardizing processes before understanding them may eliminate necessary differences or create unintended problems. An evidence-based current-state analysis provides a stronger foundation for determining whether process standardization, improvement, automation, or another change is appropriate.

Question 29. A business analyst wants to identify the fundamental reason a recurring business problem occurs rather than simply documenting its symptoms. Which technique should be used?

1. Root cause analysis
2. Stakeholder analysis
3. Benchmarking
4. Interface analysis

Correct Answer: 1. Root cause analysis

Explanation:

Root cause analysis is used to identify the fundamental causes underlying a problem rather than focusing only on its visible symptoms. The analyst may use techniques such as the five whys, cause-and-effect diagrams, data analysis, or process investigation to determine contributing factors. Understanding the root cause is important because addressing only symptoms may allow the problem to recur. Stakeholder analysis focuses on people and groups, benchmarking compares performance or practices, and interface analysis examines interactions. Root cause analysis helps ensure that proposed requirements and solutions address the actual source of a business problem.

Question 30. A business analyst needs to determine whether stakeholders agree on the meaning of several important business terms. What should the analyst create or establish?

1. Project schedule
2. Shared glossary or terminology definitions
3. Risk response plan
4. Solution architecture

Correct Answer: 2. Shared glossary or terminology definitions

Explanation:

A shared glossary or set of agreed terminology definitions helps stakeholders use consistent language throughout business analysis activities. Organizations often have terms that vary across departments or have multiple meanings depending on context. Establishing common definitions reduces ambiguity and improves communication when requirements, models, processes, and acceptance criteria are discussed. The glossary should be developed and validated with appropriate subject matter experts and stakeholders. A project schedule, risk response plan, or solution architecture serves different purposes. Clear terminology is particularly important when requirements cross organizational boundaries or involve multiple business functions.

Question 31. A business analyst is evaluating whether an existing solution continues to meet business needs after several external conditions have changed. Which factor should be examined?

1. Only the original project schedule
2. Only the development team’s preferences
3. Current performance, business needs, constraints, and environmental changes
4. Only the original requirements document

Correct Answer: 3. Current performance, business needs, constraints, and environmental changes

Explanation:

Solution evaluation should consider the current context rather than relying solely on information from the original implementation. Changes in regulations, market conditions, organizational strategy, customer expectations, technology, costs, or operating conditions can affect whether a solution remains valuable and appropriate. The analyst should assess current performance against relevant business needs and evaluation criteria while considering new constraints and environmental factors. Reviewing only the original requirements may miss changes that occurred after implementation. A broader evaluation helps identify whether the solution continues to deliver expected value or whether improvements, modifications, replacement, or other actions should be considered.

Question 32. A business analyst is asked to prioritize a large set of requirements. Stakeholders agree that some requirements are mandatory because of legal obligations. How should these requirements generally be treated during prioritization?

1. Consider their mandatory nature as a key prioritization factor
2. Ignore them until development begins
3. Rank them below optional features
4. Remove them from the requirements list

Correct Answer: 1. Consider their mandatory nature as a key prioritization factor

Explanation:

Legal or regulatory requirements can impose mandatory obligations on an organization and therefore should be treated as significant prioritization factors. The analyst should identify the applicable obligations, understand their implications, and ensure that the requirements are appropriately represented and validated. Mandatory requirements may affect solution scope, design, processes, controls, and acceptance criteria. This does not mean every regulatory-related statement automatically becomes a requirement without analysis; the specific obligation and organizational context should be understood. Ignoring mandatory requirements or treating them as optional can expose the organization to compliance, operational, financial, or legal consequences.

Question 33. A business analyst wants to understand how a change to one requirement may affect several related requirements and solution components. Which practice is most useful?

1. Brainstorming
2. Observation
3. Requirements traceability and impact analysis
4. Stakeholder identification

Correct Answer: 3. Requirements traceability and impact analysis

Explanation:

Requirements traceability helps establish relationships among requirements and other elements of the solution, while impact analysis examines the consequences of changing one element. Together, these practices allow the business analyst to identify dependencies, affected requirements, processes, interfaces, test cases, and other solution components. This is especially valuable when requirements are interconnected and a change could produce unintended consequences. Brainstorming and observation may support elicitation but do not by themselves provide systematic dependency information. Stakeholder identification determines who is involved or affected. Traceability combined with impact analysis supports informed requirements change decisions.

Question 34. A business analyst conducts interviews with several stakeholders and receives contradictory information about the same process. What should the analyst do next?

1. Choose the response from the most senior stakeholder
2. Ignore the contradictory information
3. Average the responses to create one requirement
4. Investigate the differences and validate the process information

Correct Answer: 4. Investigate the differences and validate the process information

Explanation:

Contradictory information can indicate that stakeholders have different perspectives, that processes vary by situation, or that some information is inaccurate or outdated. The analyst should investigate the differences rather than simply selecting one response or averaging the statements. Additional interviews, observation, process modeling, document review, or other elicitation techniques may help establish what actually occurs and why. Appropriate stakeholders should then validate the resulting understanding. This approach helps distinguish legitimate process variations from misunderstandings and ensures that requirements are based on an accurate understanding of business operations.

Question 35. A business analyst is assessing whether a proposed change is aligned with the organization’s strategic direction. Which question is most relevant?

1. Does the change contribute to the organization’s strategic objectives?
2. Which developer can implement the change fastest?
3. Which stakeholder requested the change first?
4. Does the change require the fewest meetings?

Correct Answer: 1. Does the change contribute to the organization’s strategic objectives?

Explanation:

Strategic alignment examines whether a proposed change supports the organization’s broader goals, objectives, and direction. A change may provide local benefits but still be inappropriate if it conflicts with strategic priorities or consumes resources needed for more important objectives. The business analyst should therefore examine how the proposed change contributes to desired outcomes and organizational value. Implementation speed, stakeholder seniority, or the number of meetings required may be relevant considerations but do not establish strategic alignment. Evaluating alignment helps organizations direct resources toward initiatives and solutions that support their intended future state.

Question 36. During requirements review, stakeholders identify a requirement that cannot be tested or objectively verified. What should the business analyst do?

1. Accept it because stakeholders agree with it
2. Clarify the requirement and define verifiable acceptance criteria
3. Remove all related requirements
4. Leave testing decisions to the development team

Correct Answer: 2. Clarify the requirement and define verifiable acceptance criteria

Explanation:

A requirement should provide enough clarity to determine whether the intended outcome has been achieved. If it cannot be objectively verified, stakeholders and the solution team may disagree about whether the requirement has been satisfied. The business analyst should clarify the requirement and work with stakeholders to establish measurable or otherwise verifiable acceptance criteria. This does not necessarily mean every requirement must be expressed as a numerical measurement; the appropriate verification method depends on the requirement. Leaving verification entirely to developers can result in inconsistent interpretations. Clear acceptance criteria support validation, testing, and stakeholder acceptance.

Question 37. A business analyst is comparing an organization’s performance with that of similar organizations to identify potential improvement opportunities. Which technique is being used?

1. Benchmarking
2. Prototyping
3. Brainstorming
4. Observation

Correct Answer: 1. Benchmarking

Explanation:

Benchmarking involves comparing an organization’s performance, practices, capabilities, or processes with those of comparable organizations or recognized standards. The purpose is to identify performance gaps, improvement opportunities, or practices that may provide useful insights. Benchmarking does not mean copying another organization’s approach without analysis. Differences in strategy, context, regulations, customers, and resources should be considered before drawing conclusions. Prototyping helps explore or validate potential solutions, brainstorming generates ideas, and observation gathers information about actual behavior or work practices. Benchmarking can provide valuable external evidence when assessing current performance and identifying potential future-state improvements.

Question 38. A stakeholder requests a detailed requirement, but the business analyst determines that the stakeholder is describing a preferred solution rather than the underlying need. What should the analyst do?

1. Document the preferred solution exactly as stated
2. Reject the stakeholder’s input
3. Explore the underlying need and determine the desired outcome
4. Ask the technical team to implement the proposed solution

Correct Answer: 3. Explore the underlying need and determine the desired outcome

Explanation:

Stakeholders frequently express needs in terms of a solution they believe will address their problem. The business analyst should explore the underlying need, desired outcome, constraints, and reasons behind the request before treating the proposed solution as a requirement. This helps prevent premature commitment to a particular approach and allows alternative solutions to be considered. The stakeholder’s proposal remains valuable information and should not simply be rejected. Understanding the underlying need gives the analyst a stronger basis for defining appropriate requirements and evaluating potential solutions against the actual business objective.

Question 39. A business analyst is preparing an analysis for senior executives who need to make a strategic decision. Which approach is most appropriate for presenting the information?

1. Present every elicitation note in chronological order
2. Provide only technical implementation details
3. Focus on relevant business outcomes, options, impacts, risks, and recommendations supported by evidence
4. Avoid discussing uncertainties or assumptions

Correct Answer: 3. Focus on relevant business outcomes, options, impacts, risks, and recommendations supported by evidence

Explanation:

Information should be tailored to the audience and the decision they need to make. Senior executives generally require concise information focused on business outcomes, strategic alignment, significant impacts, risks, costs, alternatives, and supporting evidence. Providing every elicitation note or excessive technical detail can obscure the information needed for decision-making. Important uncertainties and assumptions should not be hidden; they should be presented appropriately so decision-makers understand the limitations of the analysis. The business analyst’s role is to provide relevant, accurate, and understandable information that enables stakeholders to make informed decisions.

Question 40. A business analyst has identified several possible causes of a performance problem. The analyst wants to determine which causes contribute most significantly to the overall problem. Which technique could help prioritize the major contributing causes?

1. Stakeholder register
2. Pareto analysis
3. Requirements workshop
4. Context diagram

Correct Answer: 2. Pareto analysis

Explanation:

Pareto analysis helps identify the relatively small number of causes that account for a large proportion of an observed problem. It is based on the principle that problems may often be concentrated among a limited number of significant contributing factors. A business analyst can use available data to categorize causes, measure their frequency or impact, and focus attention on the most significant contributors. This can help stakeholders prioritize improvement efforts. A stakeholder register identifies stakeholders, a requirements workshop supports collaborative elicitation, and a context diagram shows system or solution boundaries and interactions. Pareto analysis is therefore useful when evidence is available to compare contributing causes.