View Full IIBA CBAP Exam Dumps and Practice Test Dumps

 

Question 121. A business analyst is planning an initiative with highly uncertain requirements and frequent stakeholder feedback. Which approach is most appropriate for managing requirements?

1. Define every requirement in full before any stakeholder feedback
2. Establish an approach that allows requirements to evolve through frequent feedback and reassessment
3. Prevent changes after the initial requirements workshop
4. Delay stakeholder involvement until implementation

Correct Answer: 2. Establish an approach that allows requirements to evolve through frequent feedback and reassessment

Explanation:
When requirements are uncertain and expected to evolve, the business analysis approach should support iterative learning and stakeholder feedback. Requirements can be progressively elaborated as more information becomes available. Frequent review allows stakeholders to validate assumptions, clarify needs, and adjust priorities based on emerging knowledge. Attempting to define everything upfront may create unnecessary rework when assumptions change. Preventing changes or delaying stakeholder involvement also increases the risk that the solution will not reflect current business needs.

Question 122. A business analyst is identifying stakeholders who may be affected by a proposed organizational change. Which information is most useful for stakeholder analysis?

1. Their potential impact, influence, interests, and relationship to the change
2. Their preferred office location
3. The length of their employment contracts
4. Their preferred documentation software

Correct Answer: 1. Their potential impact, influence, interests, and relationship to the change

Explanation:
Stakeholder analysis considers characteristics that help determine how individuals or groups may affect or be affected by an initiative. Relevant factors can include influence, interest, impact, authority, attitude, responsibilities, and relationship to the change. This information helps the business analyst determine appropriate engagement and communication approaches. Office location, employment contract length, or software preferences generally do not establish the stakeholder’s role in the initiative. A structured stakeholder analysis helps ensure that important perspectives are identified and appropriately addressed throughout the initiative.

Question 123. A business analyst is reviewing a proposed solution and finds that it satisfies the documented requirements but does not produce the expected business outcome. What should the analyst investigate?

1. Only whether the developers followed the design
2. Whether the requirements correctly represented the underlying business need and expected outcome
3. Whether the requirements document used the correct template
4. Whether additional features can be added immediately

Correct Answer: 2. Whether the requirements correctly represented the underlying business need and expected outcome

Explanation:
A solution can satisfy documented requirements while still failing to deliver the intended business value if the requirements did not adequately represent the underlying need. The business analyst should investigate the relationship between the original business need, expected outcomes, requirements, and implemented solution. This can reveal gaps in requirements analysis, incorrect assumptions, environmental changes, or adoption issues. Immediately adding features may not address the actual problem. Evaluating the connection between requirements and business outcomes is essential for understanding why expected value was not achieved.

Question 124. A business analyst is documenting rules that determine whether an insurance claim is approved, rejected, or sent for additional review based on multiple conditions. Which technique is most appropriate?

1. Decision table
2. Stakeholder map
3. Capability model
4. Context diagram

Correct Answer: 1. Decision table

Explanation:
A decision table is particularly useful when business rules involve multiple conditions and corresponding actions or outcomes. It provides a structured way to represent combinations of conditions and verify that relevant scenarios are covered. For an insurance claim process, a decision table could show how claim amount, policy status, documentation, and other conditions influence the resulting decision. Stakeholder maps, capability models, and context diagrams represent different types of information and would not provide the same level of clarity for complex conditional rules.

Question 125. A stakeholder says that a proposed solution must comply with a newly introduced regulation. What should the business analyst determine?

1. Whether the regulation creates new requirements or constraints for the solution
2. Whether the development team prefers the regulation
3. Whether the project schedule can ignore the regulation
4. Whether the regulation can be removed from project documentation

Correct Answer: 1. Whether the regulation creates new requirements or constraints for the solution

Explanation:
New regulations may introduce mandatory requirements or constraints that affect processes, data, controls, security, reporting, or other aspects of a solution. The business analyst should understand the applicable regulatory obligations and determine how they affect the initiative. Regulations should not be treated as optional based on team preference or schedule pressure. The analyst should also assess impacts on existing requirements and determine whether approved requirements need to change. Regulatory changes can therefore trigger requirements analysis, impact assessment, prioritization, and controlled change management.

Question 126. A business analyst is comparing the current performance of a process with its desired future performance. What type of analysis is being performed?

1. Stakeholder analysis
2. Gap analysis
3. Interface analysis
4. Organizational hierarchy analysis

Correct Answer: 2. Gap analysis

Explanation:
Gap analysis compares the current state with a desired future state to identify differences that must be addressed. In process improvement, this may involve comparing current performance, capabilities, activities, or outcomes with target conditions. The identified gaps can then help determine requirements, changes, capabilities, or initiatives needed to move toward the desired state. Stakeholder analysis focuses on people and groups, interface analysis examines interactions, and organizational hierarchy analysis examines structural relationships. Gap analysis therefore directly addresses the difference between current and desired performance.

Question 127. A business analyst is asked to identify which requirements are most critical to the success of an initiative when resources are limited. What should guide prioritization?

1. The order in which requirements were received
2. The number of words in each requirement
3. Agreed criteria such as business value, risk, urgency, dependencies, and constraints
4. The personal preference of the business analyst

Correct Answer: 3. Agreed criteria such as business value, risk, urgency, dependencies, and constraints

Explanation:
Requirements prioritization should be based on agreed criteria that reflect the organization’s objectives and the initiative’s context. Business value, risk, urgency, dependencies, regulatory obligations, cost, and implementation constraints can all influence priority. Using the order in which requirements were submitted or their length provides no meaningful indication of importance. The business analyst should facilitate agreement on prioritization criteria and apply them consistently. This creates a transparent basis for deciding which requirements should receive attention when resources, time, or capacity are limited.

Question 128. A business analyst needs to understand what information is produced, consumed, and transformed during a business process. What should the analyst examine?

1. Organizational job titles
2. Information flows associated with the process
3. Project team seating arrangements
4. Stakeholder meeting preferences

Correct Answer: 2. Information flows associated with the process

Explanation:
Understanding information flows helps the business analyst identify what information enters a process, how it is transformed or used, and what information is produced as an output. This can reveal dependencies, information gaps, duplication, quality issues, and opportunities for improvement. Organizational job titles and meeting preferences do not explain how information moves through a process. Analyzing information flows can also support data requirements, process modeling, interface analysis, and solution design by showing how information must be available at different points in the business workflow.

Question 129. A business analyst is evaluating whether a solution’s benefits justify its ongoing operating costs. Which information should be compared?

1. Expected benefits and relevant life-cycle or operating costs
2. Number of project meetings and number of developers
3. Requirements document length and testing duration
4. Stakeholder job titles and organizational levels

Correct Answer: 1. Expected benefits and relevant life-cycle or operating costs

Explanation:
Evaluating ongoing solution value requires consideration of benefits and the costs associated with operating and maintaining the solution. Relevant costs may include support, licensing, infrastructure, staffing, maintenance, training, or other recurring expenses. Comparing only initial implementation cost may provide an incomplete view of long-term value. Meeting counts, document length, and stakeholder hierarchy do not establish economic performance. A benefits and cost assessment should use appropriate assumptions and measures so decision-makers can understand whether the solution continues to provide sufficient value relative to its ongoing costs.

Question 130. A business analyst is facilitating a workshop in which participants repeatedly discuss unrelated topics. What should the analyst do?

1. Allow the discussion to continue without structure
2. End the workshop immediately
3. Redirect the discussion to the agreed objectives and capture unrelated issues for later follow-up
4. Allow only the most senior participant to speak

Correct Answer: 3. Redirect the discussion to the agreed objectives and capture unrelated issues for later follow-up

Explanation:
Effective facilitation keeps a workshop focused on its agreed objectives while ensuring valuable information is not lost. When unrelated topics arise, the business analyst can acknowledge them, record them for later investigation, and redirect participants toward the current agenda. Allowing unrestricted discussion can prevent important objectives from being completed, while ending the workshop unnecessarily loses opportunities for collaboration. Giving control to the most senior participant also undermines balanced participation. Structured facilitation helps maintain focus while preserving useful issues for appropriate follow-up.

Question 131. A business analyst is reviewing a requirement that describes a desired business result but does not specify how the solution will achieve it. What type of requirement is this most likely to represent?

1. Business requirement
2. Interface requirement
3. Transition requirement
4. Technical design constraint

Correct Answer: 1. Business requirement

Explanation:
Business requirements describe goals, objectives, or outcomes that the organization wants to achieve. They generally focus on the business need rather than prescribing a specific solution implementation. A requirement describing a desired result without specifying how it should be achieved is therefore consistent with a business-level requirement. Interface requirements describe interactions, transition requirements address temporary capabilities needed during movement between states, and technical constraints limit implementation choices. Keeping business requirements outcome-focused helps prevent premature commitment to a particular solution design.

Question 132. A business analyst is asked to determine whether a proposed change could create new operational risks. Which analysis should be performed?

1. Risk analysis
2. Font analysis
3. Stakeholder directory analysis
4. Document formatting analysis

Correct Answer: 1. Risk analysis

Explanation:
Risk analysis identifies potential uncertain events or conditions that could affect objectives and evaluates their possible consequences. For a proposed change, the business analyst should examine whether the change introduces new risks, increases existing risks, or reduces current risks. Relevant factors may include probability, impact, controls, dependencies, and mitigation options. Formatting and directory information do not establish operational risk. Risk analysis should be integrated with change and solution evaluation so decision-makers understand potential consequences before approving significant changes.

Question 133. A business analyst is working with stakeholders who disagree about the meaning of an important business term. What should the analyst establish?

1. A shared and agreed definition of the term
2. Separate definitions for every stakeholder
3. A technical implementation of the term
4. A new project schedule

Correct Answer: 1. A shared and agreed definition of the term

Explanation:
Inconsistent terminology can create ambiguity and lead to conflicting interpretations of requirements. The business analyst should facilitate discussion among relevant stakeholders and establish a shared definition that reflects the organization’s intended meaning. Where appropriate, the definition can be documented in a glossary or other business analysis information repository. Creating separate definitions without resolving the underlying disagreement can perpetuate confusion. Technical implementation should not determine the business meaning of a term, and project scheduling does not address the semantic issue.

Question 134. A proposed feature is technically possible but would require major changes to several established business processes. What should the business analyst assess?

1. Only whether developers can code the feature
2. The organizational and process impacts of introducing the feature
3. Only the feature’s visual appearance
4. Whether the feature has the longest requirement description

Correct Answer: 2. The organizational and process impacts of introducing the feature

Explanation:
Technical feasibility alone does not establish whether a feature is appropriate for the organization. A feature that significantly changes established processes may affect roles, procedures, training, controls, performance, stakeholder responsibilities, and organizational readiness. The business analyst should assess these impacts and determine whether the expected value justifies the change. Focusing only on coding feasibility or visual design overlooks important business consequences. Organizational and process impact analysis provides decision-makers with a more complete understanding of what adoption would require.

Question 135. A business analyst wants to ensure that requirements remain accessible, current, and understandable throughout the initiative. What should be established?

1. A requirements information management approach
2. A new development language
3. A stakeholder ranking system based on seniority
4. A separate marketing campaign

Correct Answer: 1. A requirements information management approach

Explanation:
Requirements information management defines how business analysis information is stored, maintained, accessed, updated, secured, and communicated. An effective approach helps stakeholders locate the appropriate version of requirements and understand their status and relationships. It may address repositories, access controls, naming conventions, versioning, traceability, and maintenance responsibilities. Development language and marketing activities do not provide requirements governance. A suitable information management approach reduces confusion, supports collaboration, and helps preserve the integrity of business analysis information throughout the initiative.

Question 136. A business analyst discovers that a requirement has changed several times because stakeholders continue to learn more about the problem. What should the analyst recognize?

1. Requirement volatility
2. Requirement approval
3. Requirement duplication
4. Requirement traceability

Correct Answer: 1. Requirement volatility

Explanation:
Requirement volatility describes the degree to which requirements are expected to change over time. Frequent changes caused by increasing stakeholder understanding, evolving business conditions, or newly discovered information are indicators of volatility. Recognizing volatility helps the business analyst choose an appropriate approach for managing requirements and stakeholder collaboration. It may also influence prioritization, planning, traceability, and change assessment. Volatility does not mean that requirements are invalid; rather, it indicates that the requirements should be managed with an approach appropriate to their expected level of change.

Question 137. A business analyst is determining whether a solution can be supported by the organization’s existing infrastructure and operational capabilities. What should be evaluated?

1. Operational feasibility
2. Requirement wording length
3. Stakeholder meeting frequency
4. Document formatting standards

Correct Answer: 1. Operational feasibility

Explanation:
Operational feasibility considers whether an organization can operate, support, maintain, and use a proposed solution effectively within its existing or planned environment. This can include infrastructure, staffing, skills, support processes, policies, procedures, and organizational capabilities. A solution may be technically possible but operationally unsuitable if the organization cannot support it effectively. Requirement length, meeting frequency, and document formatting do not establish operational feasibility. Assessing this factor helps identify capability gaps and transition needs before significant implementation commitments are made.

Question 138. A business analyst needs to identify all parties that can influence a decision about a major solution investment. What should the analyst identify?

1. Only the end users
2. Decision stakeholders and their authority or influence
3. Only the technical architects
4. Only external vendors

Correct Answer: 2. Decision stakeholders and their authority or influence

Explanation:
Decision stakeholders include individuals or groups who have authority, influence, accountability, or a significant interest in a decision. Identifying them helps the business analyst understand who must provide input, who can approve the decision, and who may be affected by it. Limiting analysis to end users, technical architects, or vendors can overlook important governance and business perspectives. Understanding decision authority also supports appropriate communication, approval processes, escalation, and stakeholder engagement throughout the decision-making process.

Question 139. A business analyst is validating whether a proposed solution addresses the original problem identified at the beginning of the initiative. Which relationship should be examined?

1. The relationship between the business need, requirements, solution, and expected outcomes
2. The relationship between employee birthdays and project milestones
3. The relationship between document length and meeting duration
4. The relationship between developer preferences and office location

Correct Answer: 1. The relationship between the business need, requirements, solution, and expected outcomes

Explanation:
Solution validation should consider whether the implemented or proposed solution addresses the original business need and contributes to the intended outcomes. Examining the relationship between the business need, requirements, solution components, and expected results helps identify gaps or misalignment. This also supports traceability and solution evaluation. Unrelated administrative relationships do not provide evidence about whether the solution solves the original problem. Maintaining this connection throughout the initiative helps prevent requirements from becoming detached from the business purpose they were intended to support.

Question 140. A business analyst is closing an initiative and wants to preserve useful business analysis information for future work. What should be considered?

1. Discarding all requirements after implementation
2. Retaining relevant requirements, decisions, lessons learned, and other information according to organizational practices
3. Keeping only the project schedule
4. Keeping only unresolved issues

Correct Answer: 2. Retaining relevant requirements, decisions, lessons learned, and other information according to organizational practices

Explanation:
Business analysis information may remain valuable after an initiative is completed. Requirements, decisions, assumptions, models, lessons learned, and other relevant information can support future enhancements, audits, maintenance, new initiatives, and organizational learning. Information should be retained according to the organization’s information management, security, retention, and governance practices. Discarding everything after implementation can result in the loss of valuable institutional knowledge. Preserving appropriate information also improves traceability and provides historical context for future business analysis activities.