View Full IIBA CBAP Exam Dumps and Practice Test Dumps

 

Question 141. A business analyst is determining how much stakeholder participation is needed during requirements development. Which factor should be considered most carefully?

1. The stakeholder’s preferred meeting time
2. The stakeholder’s influence, interest, expertise, and relationship to the requirements
3. The number of pages in the requirements document
4. The programming language used by the solution

Correct Answer: 2. The stakeholder’s influence, interest, expertise, and relationship to the requirements

Explanation:
Stakeholder participation should be tailored to the stakeholder’s role, influence, interest, expertise, authority, and relationship to the requirements. Some stakeholders may need to participate directly in elicitation and validation, while others may only need periodic updates or decision points. Meeting preferences can affect logistics but should not determine the appropriate level of engagement. Similarly, document length and programming language do not establish stakeholder involvement. A deliberate engagement approach helps ensure that important perspectives are captured without requiring every stakeholder to participate in every activity.

Question 142. A business analyst is evaluating whether a proposed solution provides the expected improvement in customer satisfaction. Which evidence would be most useful?

1. The number of requirements approved
2. The number of development meetings
3. Customer satisfaction measures before and after implementation
4. The number of developers assigned

Correct Answer: 3. Customer satisfaction measures before and after implementation

Explanation:
Solution evaluation should use measures that demonstrate whether the expected business outcome was achieved. If customer satisfaction is the intended outcome, appropriate customer satisfaction measures collected before and after implementation can provide evidence of change. The number of requirements, meetings, or developers describes project activity rather than business performance. The measures should be relevant, reliable, and interpreted in context because other factors may also influence customer satisfaction. Comparing appropriate baseline and post-implementation information provides a stronger basis for evaluating whether the solution delivered the intended benefit.

Question 143. A business analyst is asked to determine which stakeholders should receive detailed technical requirements and which should receive business-level summaries. What should guide this decision?

1. Stakeholder information needs and communication preferences
2. Stakeholder seniority alone
3. The order in which stakeholders joined the project
4. The number of requirements assigned to each stakeholder

Correct Answer: 1. Stakeholder information needs and communication preferences

Explanation:
Business analysis communication should be tailored to the audience. Stakeholders have different responsibilities, knowledge levels, decision-making needs, and preferences for receiving information. Technical teams may need detailed functional, interface, and non-functional requirements, while executives may need concise information about outcomes, risks, costs, and decisions. Seniority alone does not determine information needs. The business analyst should understand each stakeholder group’s communication requirements and select an appropriate level of detail and format while maintaining consistency in the underlying information.

Question 144. A business analyst discovers that a proposed solution depends on an external system that is owned by another organization. What should the analyst identify?

1. Only the internal development schedule
2. The dependency, associated risks, responsibilities, and required coordination
3. The preferred user-interface design
4. The number of internal project meetings

Correct Answer: 2. The dependency, associated risks, responsibilities, and required coordination

Explanation:
External dependencies can significantly affect solution feasibility, timing, risk, and implementation. The business analyst should document the dependency and determine what responsibilities, interfaces, agreements, assumptions, and coordination are required. Risks associated with the external organization should also be considered because changes outside the initiative’s direct control may affect outcomes. Focusing only on internal schedules or interface design can overlook the dependency’s broader implications. Making external dependencies visible allows stakeholders to plan appropriate actions and monitor conditions that could affect delivery.

Question 145. A stakeholder proposes removing a requirement because it has not yet produced visible benefits. What should the business analyst examine before making a recommendation?

1. The requirement’s relationship to expected outcomes, dependencies, timing, and value
2. Only the requirement’s word count
3. Only whether the requirement was requested by an executive
4. Whether another requirement has a similar title

Correct Answer: 1. The requirement’s relationship to expected outcomes, dependencies, timing, and value

Explanation:
A requirement should not be removed solely because benefits are not immediately visible. Some benefits may occur later, depend on other requirements, or require adoption of the solution before becoming measurable. The business analyst should examine the requirement’s expected value, relationship to business objectives, dependencies, timing, and relevant performance measures. This analysis provides evidence for deciding whether the requirement remains justified. Removing it without understanding these factors may eliminate an important capability or prevent other requirements from delivering their intended outcomes.

Question 146. A business analyst is asked to identify the information needed to determine whether a solution has achieved its intended business benefits. What should be defined?

1. Benefit measures and evaluation criteria
2. Only the project team’s preferred reports
3. The number of stakeholder meetings
4. The application’s development framework

Correct Answer: 1. Benefit measures and evaluation criteria

Explanation:
Benefit evaluation requires clearly defined measures and criteria that can be used to determine whether expected outcomes have been achieved. Measures should be connected to the business objectives and may address financial, operational, customer, quality, compliance, or other relevant outcomes. Defining these measures helps establish what evidence should be collected and how results will be interpreted. Project meeting counts and development frameworks do not demonstrate business benefit. Establishing evaluation criteria early also makes later solution assessment more objective and meaningful.

Question 147. A business analyst is analyzing a business rule that contains several nested conditions and alternative outcomes. Which technique can help represent the logic in a structured way?

1. Stakeholder map
2. Decision tree
3. Capability map
4. Organization chart

Correct Answer: 2. Decision tree

Explanation:
A decision tree represents decisions and their possible outcomes through branches based on conditions. It is useful when business logic contains sequential decisions, alternatives, and multiple possible outcomes. A decision tree can help stakeholders visualize how different conditions lead to different results and can expose missing or inconsistent logic. Stakeholder maps, capability maps, and organization charts serve different purposes. When the primary concern is understanding the logical path from conditions to outcomes, a decision tree can provide a clear and structured representation.

Question 148. A business analyst is determining whether a requirement can be satisfied without violating a mandatory organizational policy. What should the analyst evaluate?

1. Compliance with the applicable policy and its impact on the requirement
2. The stakeholder’s preferred meeting format
3. The requirement’s position in the document
4. The number of developers assigned

Correct Answer: 1. Compliance with the applicable policy and its impact on the requirement

Explanation:
Organizational policies can act as constraints on requirements and solution options. The business analyst should identify the applicable policy, understand its mandatory provisions, and determine whether the requirement can be satisfied within those boundaries. If there is a conflict, the analyst should investigate the implications and involve the appropriate decision-makers or governance process. Meeting formats, document positions, and developer staffing do not establish policy compliance. Explicitly considering policy constraints helps prevent requirements from being approved that cannot legally or operationally be implemented.

Question 149. A business analyst wants to understand why a process takes significantly longer in one department than another despite having similar steps. What should the analyst investigate?

1. Only the department’s job titles
2. Differences in resources, rules, roles, inputs, systems, and process conditions
3. Only the visual appearance of process documentation
4. Only the number of stakeholders in each department

Correct Answer: 2. Differences in resources, rules, roles, inputs, systems, and process conditions

Explanation:
Similar process steps can produce different outcomes when underlying conditions differ. The business analyst should examine resources, staffing, roles, business rules, inputs, systems, handoffs, controls, workloads, and other relevant process conditions. Looking only at job titles or stakeholder counts would not explain operational performance differences. Comparing process variations helps identify the factors responsible for delays and provides evidence for improvement opportunities. The analysis should distinguish genuine process differences from differences caused by environmental or organizational factors.

Question 150. A business analyst is documenting a requirement that must be implemented because of a government regulation. How should the requirement generally be treated during prioritization?

1. As optional unless stakeholders request it again
2. According to its mandatory compliance significance
3. Based only on development team preference
4. Based only on its estimated implementation duration

Correct Answer: 2. According to its mandatory compliance significance

Explanation:
Regulatory requirements can impose mandatory obligations on an organization. Their prioritization should reflect the applicable compliance requirement, deadlines, risks, and consequences of non-compliance. Treating such requirements as optional or prioritizing them solely by development effort can create significant organizational risk. The business analyst should understand the specific regulatory obligation and communicate its implications to decision-makers. Other prioritization factors may still be relevant, but mandatory compliance obligations can impose constraints that must be addressed regardless of preference or convenience.

Question 151. A business analyst is reviewing a requirement that was written several months ago and may no longer reflect current business conditions. What should the analyst do?

1. Assume it remains valid because it was previously approved
2. Revalidate the requirement against current business needs and conditions
3. Delete it automatically
4. Ask developers to determine whether it is still needed

Correct Answer: 2. Revalidate the requirement against current business needs and conditions

Explanation:
Previously approved requirements may become less relevant when business conditions, regulations, strategies, stakeholders, or technology change. The business analyst should periodically assess whether requirements remain valid and aligned with current needs. Approval at an earlier point does not guarantee continued relevance. Revalidation may confirm that the requirement remains appropriate, reveal a need for modification, or indicate that it should be retired through the appropriate governance process. Developers can provide technical input, but business relevance should be evaluated in the appropriate business context.

Question 152. A business analyst is identifying whether an initiative requires a new organizational capability that does not currently exist. What should the analyst compare?

1. Current capabilities with the capabilities required in the future state
2. Current meeting schedules with future meeting schedules
3. Current document formats with future document formats
4. Current office locations with future office locations

Correct Answer: 1. Current capabilities with the capabilities required in the future state

Explanation:
Capability analysis examines what the organization can currently do and what it needs to be able to do in the future. Comparing current and desired capabilities reveals gaps that may require new processes, skills, technology, organizational changes, or other investments. Meeting schedules, document formats, and office locations generally do not establish whether the organization possesses the capabilities required for the future state. Capability gaps can then inform solution scope, transition requirements, organizational readiness, and strategic planning.

Question 153. A business analyst is facilitating requirements elicitation with stakeholders who have conflicting priorities. What should the analyst focus on?

1. Selecting the priority personally
2. Understanding the underlying needs and facilitating agreement using agreed criteria
3. Giving priority to the stakeholder with the highest job title
4. Ending elicitation until all stakeholders agree independently

Correct Answer: 2. Understanding the underlying needs and facilitating agreement using agreed criteria

Explanation:
Conflicting priorities should be explored rather than resolved through personal judgment or organizational seniority alone. The business analyst should understand the underlying needs, expected outcomes, constraints, risks, and value associated with each perspective. Agreed prioritization criteria can then provide a transparent basis for discussion and decision-making. The analyst facilitates the process but should not make business decisions without appropriate authority. Structured collaboration can reveal opportunities to satisfy multiple needs or identify trade-offs that require a decision from the responsible stakeholders.

Question 154. A business analyst needs to document a requirement describing what data must be retained, for how long, and under what conditions it may be deleted. What type of concern does this requirement primarily address?

1. Data retention and information management
2. Stakeholder hierarchy
3. Organizational branding
4. Project scheduling

Correct Answer: 1. Data retention and information management

Explanation:
Requirements concerning how long information must be retained, when it can be deleted, and under what conditions it must be preserved address information management and data retention concerns. Such requirements may also be influenced by legal, regulatory, security, privacy, or organizational policies. They should be analyzed carefully because they can affect storage, access, architecture, processes, and compliance. Stakeholder hierarchy, branding, and scheduling do not directly define data retention obligations. Clear retention requirements help ensure that information is managed consistently with applicable rules and business needs.

Question 155. A business analyst is determining whether a proposed solution can meet a mandatory deadline imposed by an external authority. What should be considered?

1. The deadline as a constraint and its impact on feasible solution options
2. Only the team’s preferred development method
3. Only the number of requirements
4. The analyst’s preferred delivery date

Correct Answer: 1. The deadline as a constraint and its impact on feasible solution options

Explanation:
A mandatory external deadline can constrain the solution approach, scope, sequencing, resources, and delivery strategy. The business analyst should document the deadline and assess how it affects feasibility and available alternatives. If the deadline cannot reasonably be met, that risk should be communicated to the appropriate decision-makers. Development preferences and requirement counts may influence planning but do not override an externally imposed obligation. Treating the deadline as an explicit constraint allows stakeholders to evaluate realistic options and make informed trade-offs.

Question 156. A business analyst is reviewing several requirements and notices that some are supported by multiple business objectives while others support none. What should the analyst investigate?

1. The traceability and business justification of the requirements
2. Only the requirements’ formatting
3. The number of words in each requirement
4. Whether the requirements were written on the same day

Correct Answer: 1. The traceability and business justification of the requirements

Explanation:
Requirements should have a clear relationship to business needs, objectives, stakeholder needs, or other valid sources. If a requirement supports no identifiable objective or business need, its justification may need to be investigated. Requirements supporting multiple objectives may be particularly valuable, but their relationships should still be validated rather than assumed. Traceability helps reveal these connections and supports prioritization, change analysis, and solution evaluation. Formatting, word count, and creation date do not establish whether a requirement is justified.

Question 157. A business analyst is evaluating whether a proposed solution will be accepted by employees who must use it daily. What should be assessed?

1. User acceptance and organizational readiness
2. Only the solution’s development language
3. Only the number of system modules
4. The document’s page count

Correct Answer: 1. User acceptance and organizational readiness

Explanation:
A technically functional solution may still fail to deliver value if intended users cannot or will not adopt it effectively. The business analyst should assess user acceptance, organizational readiness, usability, training needs, process impacts, support requirements, and other adoption factors. Development language and module count do not establish whether users will accept the solution. Understanding readiness before implementation can reveal barriers and transition requirements that should be addressed. User feedback and appropriate evaluation measures can also help determine whether the solution is practical and acceptable in its operational context.

Question 158. A business analyst is asked to determine whether a proposed requirement can be tested objectively after implementation. What should the analyst define?

1. Acceptance criteria that describe observable expected results
2. The stakeholder’s preferred meeting schedule
3. The analyst’s personal interpretation
4. The application’s marketing message

Correct Answer: 1. Acceptance criteria that describe observable expected results

Explanation:
Acceptance criteria establish the conditions that must be satisfied for a requirement or solution component to be accepted. Effective criteria describe observable or measurable results and provide a shared basis for verification. Without clear criteria, stakeholders may interpret satisfaction differently, creating disputes during validation or acceptance. Meeting schedules, marketing messages, and personal interpretations do not establish objective acceptance conditions. The business analyst should collaborate with appropriate stakeholders to define criteria that are sufficiently specific, testable, and aligned with the intended business need.

Question 159. A business analyst identifies that a proposed change could affect requirements owned by several different business units. What should the analyst do?

1. Analyze the cross-functional impact and involve the affected stakeholders
2. Change only the requirement owned by the requesting department
3. Allow the requesting stakeholder to approve all affected requirements
4. Ignore impacts outside the requesting department

Correct Answer: 1. Analyze the cross-functional impact and involve the affected stakeholders

Explanation:
Changes that cross organizational boundaries can create dependencies and unintended consequences in multiple business areas. The business analyst should identify affected requirements, processes, systems, roles, policies, and stakeholders and assess the broader impact. Appropriate stakeholders should be involved in reviewing the implications and making decisions within their areas of authority. Limiting analysis to the requesting department can overlook important dependencies. Cross-functional impact analysis supports coordinated decisions and helps ensure that changes do not unintentionally disrupt other parts of the organization.

Question 160. A business analyst is reviewing whether a solution continues to provide value after several external business conditions have changed. What should be evaluated?

1. Only whether the original requirements were delivered
2. Current performance, continued stakeholder needs, environmental changes, and expected value
3. Only the original project budget
4. Only the number of enhancements requested

Correct Answer: 2. Current performance, continued stakeholder needs, environmental changes, and expected value

Explanation:
Solution value can change when business conditions, regulations, markets, technology, stakeholder needs, or organizational strategies change. Continued solution evaluation should therefore consider current performance, current needs, environmental conditions, risks, and expected benefits rather than relying solely on historical requirements. A solution may still satisfy its original requirements while no longer providing the expected value. Examining current evidence helps stakeholders determine whether the solution should be maintained, improved, replaced, or otherwise adjusted in response to changing circumstances.