View Full IIBA CBAP Exam Dumps and Practice Test Dumps

 

Question 261. A business analyst is planning elicitation for a complex initiative involving executives, operational users, and technical specialists. What should primarily determine the elicitation approach?

1. The analyst’s preferred elicitation technique
2. The number of requirements expected
3. Stakeholder characteristics, objectives, context, and information needs
4. The order in which stakeholders were identified

Correct Answer: 3. Stakeholder characteristics, objectives, context, and information needs

Explanation:
Elicitation should be planned according to the nature of the information needed and the characteristics of the stakeholders who possess or use that information. Executives, operational users, and technical specialists may require different approaches because their knowledge, responsibilities, availability, and communication preferences differ. The analyst should consider the elicitation objective, complexity, context, stakeholder expertise, and risks when selecting techniques. Using one preferred technique for everyone may produce incomplete or biased information. A tailored approach increases the likelihood that relevant information is obtained efficiently and validated appropriately.

Question 262. A stakeholder provides a requirement that describes a specific software feature but cannot explain what business problem it is intended to solve. What should the business analyst explore?

1. The underlying business need and expected outcome
2. The developer’s preferred implementation language
3. The visual appearance of the feature
4. The number of screens required

Correct Answer: 1. The underlying business need and expected outcome

Explanation:
A requested feature may represent a stakeholder’s proposed solution rather than the actual business need. The analyst should explore what problem the stakeholder is trying to address, what outcome is expected, and what value the feature is intended to provide. Understanding the underlying need allows alternative solutions to be considered and reduces the risk of prematurely committing to a particular implementation. Technical details may become relevant later, but they should not replace understanding the business purpose. Connecting requested capabilities to desired outcomes also supports prioritization and solution evaluation.

Question 263. A business analyst is reviewing a requirement that contains several unrelated business needs combined into one statement. What quality concern should be addressed?

1. The requirement’s stakeholder priority
2. The requirement’s atomicity and clarity
3. The solution’s technical architecture
4. The project’s budget approval

Correct Answer: 2. The requirement’s atomicity and clarity

Explanation:
Combining several unrelated needs into a single requirement can make it difficult to understand, prioritize, validate, trace, test, and manage changes. The analyst should determine whether the statement should be separated into distinct requirements that each express a coherent need or condition. Atomic requirements are easier to analyze because stakeholders can assess each independently. Clarity is also important so that each requirement has a consistent interpretation. Technical architecture and budget approval address other concerns and do not resolve the underlying quality problem in the requirement statement.

Question 264. A business analyst is evaluating whether a proposed solution can be supported by the organization’s existing operational staff after implementation. What should be examined?

1. Only the solution’s purchase price
2. Only the number of features
3. Operational capabilities, resources, skills, support processes, and ongoing constraints
4. Only the project completion date

Correct Answer: 3. Operational capabilities, resources, skills, support processes, and ongoing constraints

Explanation:
A solution may be technically implementable but difficult to operate or support in the organization’s environment. Operational feasibility requires examination of the resources, skills, support processes, responsibilities, infrastructure, service expectations, and ongoing constraints needed to sustain the solution. Purchase price and feature count do not establish whether the organization can operate the solution effectively. The analyst should identify capability gaps and determine whether additional training, staffing, process changes, or support arrangements will be required. This analysis helps ensure that the future solution remains viable beyond initial implementation.

Question 265. During requirements elicitation, two stakeholders describe the same process differently. What should the business analyst do first?

1. Select the description provided by the more senior stakeholder
2. Document both descriptions as final requirements
3. Investigate the differences and determine the actual process using appropriate evidence
4. Remove the process from scope

Correct Answer: 3. Investigate the differences and determine the actual process using appropriate evidence

Explanation:
Different descriptions may result from different roles, process variations, outdated knowledge, or misunderstandings. The analyst should investigate the discrepancy rather than deciding based solely on stakeholder seniority. Additional elicitation, observation, process documentation, data, or other evidence can help establish how the process actually operates and whether legitimate variations exist. Recording conflicting statements as final requirements would preserve the inconsistency rather than resolve it. Understanding the source of the difference is essential before defining future-state requirements or recommending process changes.

Question 266. A business analyst needs to understand how information moves between departments during a business process. Which aspect should be examined?

1. Information inputs, outputs, transformations, and handoffs
2. Only department reporting structures
3. Only employee job titles
4. Only the number of meetings between departments

Correct Answer: 1. Information inputs, outputs, transformations, and handoffs

Explanation:
Information flow analysis focuses on how information is created, received, transformed, transferred, stored, and consumed throughout a process. Examining inputs, outputs, transformations, and handoffs can reveal missing information, duplication, delays, ownership issues, and opportunities for improvement. Organizational structures and job titles may provide context but do not directly describe the movement of information. Understanding information flows is particularly important when defining requirements for integrations, data management, automation, reporting, and process controls.

Question 267. A business analyst is asked to prioritize a large set of requirements, but stakeholders have not agreed on how priorities should be determined. What should the analyst do?

1. Rank requirements alphabetically
2. Establish or facilitate agreement on prioritization criteria
3. Prioritize requirements according to document order
4. Give every requirement the same priority

Correct Answer: 2. Establish or facilitate agreement on prioritization criteria

Explanation:
Prioritization is more meaningful when stakeholders understand and agree on the criteria used to compare requirements. Criteria may include business value, strategic alignment, urgency, risk, regulatory obligations, dependencies, cost, feasibility, or implementation constraints. Without agreed criteria, different stakeholders may apply inconsistent assumptions and produce conflicting priorities. The analyst should facilitate discussion and help establish a suitable prioritization approach. Alphabetical order, document order, or assigning identical priority does not reflect the relative importance or consequences of requirements.

Question 268. A proposed solution introduces a new process that requires employees to acquire skills they do not currently possess. What should the business analyst identify?

1. A capability or readiness gap requiring transition support
2. A new strategic objective
3. A replacement for all existing requirements
4. A reason to eliminate stakeholder participation

Correct Answer: 1. A capability or readiness gap requiring transition support

Explanation:
When a future solution requires skills that employees do not currently possess, the organization has a capability or readiness gap. The analyst should identify the affected roles, required skills, training needs, support arrangements, and other transition considerations. This information can become part of the transition requirements and organizational readiness activities. The existence of a skills gap does not automatically mean the solution should be rejected. Instead, understanding the gap allows stakeholders to assess the effort, cost, risks, and support needed to achieve successful adoption.

Question 269. A business analyst is evaluating whether a solution continues to provide value several months after implementation. Which evidence is most relevant?

1. The number of original project meetings
2. Current performance measures, stakeholder needs, environmental conditions, and expected outcomes
3. The number of pages in the original business case
4. The original development team’s size

Correct Answer: 2. Current performance measures, stakeholder needs, environmental conditions, and expected outcomes

Explanation:
Solution value can change over time as business conditions, stakeholder needs, regulations, technology, and organizational priorities change. Ongoing evaluation should therefore consider current performance against expected outcomes and examine whether the solution still addresses relevant needs. Historical project activity may provide context but does not demonstrate current value. The analyst should also investigate external factors that may have affected results. This approach helps determine whether the solution continues to provide expected benefits or whether changes, enhancements, process adjustments, or other actions may be required.

Question 270. A business analyst is examining a requirement that is technically precise but does not explain why the organization needs it. What should the analyst seek to establish?

1. A relationship to the business need, objective, or expected outcome
2. A longer technical description
3. A new programming specification
4. A larger stakeholder list

Correct Answer: 1. A relationship to the business need, objective, or expected outcome

Explanation:
Technical precision does not by itself establish business justification. The analyst should determine what need, objective, or expected outcome the requirement supports. Establishing this relationship improves traceability and helps stakeholders evaluate whether the requirement remains relevant when priorities, constraints, or solution options change. A longer technical description may add detail without explaining value. Connecting requirements to business outcomes also supports prioritization, impact analysis, and solution evaluation. Requirements that lack a clear business rationale may require further investigation before they are accepted or prioritized.

Question 271. A business analyst is creating a model to show the external organizations and systems that interact with a proposed solution. Which representation is most appropriate?

1. Organizational hierarchy
2. Context diagram
3. Decision table
4. Responsibility matrix

Correct Answer: 2. Context diagram

Explanation:
A context diagram provides a high-level representation of a solution and the external entities that interact with it. It can show systems, organizations, users, or other external parties and the information or interactions crossing the solution boundary. This helps stakeholders understand scope, interfaces, dependencies, and external relationships without requiring detailed internal design. Organizational hierarchies describe reporting relationships, decision tables represent business rules, and responsibility matrices focus on roles. The appropriate model should match the information the stakeholders need to understand and validate.

Question 272. A business analyst is assessing a proposed solution that would require a new regulatory approval before it can operate. How should this approval be treated?

1. As an optional stakeholder preference
2. As a compliance constraint that can affect feasibility and timing
3. As a user interface requirement only
4. As an implementation detail with no business impact

Correct Answer: 2. As a compliance constraint that can affect feasibility and timing

Explanation:
Required regulatory approval can affect whether and when a solution may legally or operationally be introduced. The analyst should identify the applicable obligation, approval process, evidence required, responsible parties, timing, and potential consequences of noncompliance. Treating regulatory approval as an optional preference could expose the organization to unacceptable risk. It may also influence solution feasibility, requirements, project sequencing, and transition planning. Compliance constraints should therefore be considered as part of the overall analysis rather than treated as a purely technical implementation detail.

Question 273. A business analyst is reviewing a requirement and finds that its acceptance conditions cannot be objectively verified. What should be improved?

1. The requirement’s measurable and observable acceptance criteria
2. The project logo
3. The number of stakeholders
4. The software vendor selection

Correct Answer: 1. The requirement’s measurable and observable acceptance criteria

Explanation:
Acceptance conditions should provide a basis for determining objectively whether a requirement has been satisfied. If conditions cannot be verified, the analyst should clarify the expected behavior, quality level, outcome, or other observable characteristics. Measurable criteria reduce ambiguity and support validation and testing. Project branding, stakeholder count, and vendor selection do not address the problem. The appropriate form of measurement depends on the requirement, but it should be sufficiently precise for relevant stakeholders to reach a consistent conclusion about whether the expected result has been achieved.

Question 274. A business analyst is evaluating two solution alternatives with different implementation costs and different expected benefits. What should be compared?

1. Only the initial implementation cost
2. Benefits, costs, risks, constraints, and relevant life-cycle considerations
3. Only the number of features
4. Only the option preferred by technical staff

Correct Answer: 2. Benefits, costs, risks, constraints, and relevant life-cycle considerations

Explanation:
Solution alternatives should be evaluated using factors that reflect the objectives and context of the decision. Initial implementation cost is important but may not represent the total economic or operational impact. The analyst should consider expected benefits, implementation and ongoing costs, risks, constraints, feasibility, operational effects, dependencies, and other relevant life-cycle factors. Feature count alone does not establish value, and technical preference should be considered as evidence rather than treated as the sole decision criterion. A structured comparison provides decision-makers with a clearer understanding of trade-offs.

Question 275. A business analyst discovers that a proposed requirement depends on a capability that will not be available until a later release. What should be documented?

1. The dependency and its effect on timing, scope, and implementation
2. A new business objective unrelated to the dependency
3. The analyst’s personal preference for release order
4. A requirement to remove the later release

Correct Answer: 1. The dependency and its effect on timing, scope, and implementation

Explanation:
Dependencies between requirements, capabilities, or releases can influence sequencing and implementation decisions. The analyst should document the dependency and assess its effects on timing, scope, risks, priorities, and potential alternatives. This information helps stakeholders understand whether the dependent requirement can be delivered independently or must wait for another capability. Personal preference should not determine sequencing, and removing another release without analysis could create unnecessary consequences. Explicit dependency information supports planning, traceability, impact assessment, and informed release decisions.

Question 276. A business analyst is investigating repeated customer complaints about a service. The complaints mention different symptoms, but many occur after the same process step. What should the analyst investigate?

1. Potential common causes associated with that process step
2. Only the wording of the complaints
3. Only the customer demographic information
4. Whether the complaints should be deleted from the analysis

Correct Answer: 1. Potential common causes associated with that process step

Explanation:
When different symptoms appear after the same process step, that step may represent a common contributing factor, although further evidence is required before concluding it is the root cause. The analyst should examine process behavior, inputs, rules, resources, system interactions, timing, and available performance or complaint data around that point. Looking only at wording or demographic information may miss process-related causes. Cause analysis should distinguish correlation from causation and identify evidence that supports or challenges potential explanations before changes are recommended.

Question 277. A business analyst is determining whether a requirement remains valid after the organization’s strategic priorities have changed. What should be reviewed?

1. The requirement’s continued relationship to current objectives, needs, and expected value
2. Only the date when the requirement was originally written
3. Only the number of times the requirement was approved
4. Only the original author’s job title

Correct Answer: 1. The requirement’s continued relationship to current objectives, needs, and expected value

Explanation:
Requirements should remain relevant to the current business context. When strategic priorities change, the analyst should revalidate whether the requirement still supports current objectives, stakeholder needs, expected outcomes, or other legitimate business drivers. The original approval date or author does not establish continued validity. A requirement that was appropriate previously may need to be modified, reprioritized, deferred, or removed if circumstances have changed. Revalidation helps prevent organizations from continuing to invest in requirements that no longer provide sufficient business value.

Question 278. A business analyst is preparing to communicate a complex analysis to stakeholders with very different levels of technical knowledge. What should the analyst do?

1. Use identical technical detail for every stakeholder
2. Tailor the presentation while preserving consistent underlying information
3. Provide only technical documentation
4. Exclude stakeholders who lack technical expertise

Correct Answer: 2. Tailor the presentation while preserving consistent underlying information

Explanation:
Stakeholders may require different levels of detail and different forms of communication depending on their responsibilities, knowledge, decisions, and information needs. The analyst should tailor terminology, examples, visualizations, and level of detail while preserving the accuracy and consistency of the underlying analysis. Providing identical technical detail to every audience may make the information inaccessible or unnecessarily complex. Excluding stakeholders because they lack technical expertise can omit important business perspectives. Effective communication adapts the presentation without changing the substantive meaning of the information.

Question 279. A business analyst is reviewing a proposed change that may affect requirements, processes, systems, stakeholders, costs, and risks. Which technique should be used to understand the overall consequences?

1. Impact analysis
2. Brainstorming only
3. Glossary development
4. Stakeholder scheduling

Correct Answer: 1. Impact analysis

Explanation:
Impact analysis examines the consequences of a proposed change across relevant business and solution elements. Depending on the initiative, this may include requirements, processes, systems, stakeholders, data, costs, schedules, risks, dependencies, and expected outcomes. Traceability information can provide important inputs to this analysis by showing relationships among affected elements. Brainstorming may support idea generation but does not by itself provide a structured assessment of consequences. Understanding the full impact allows stakeholders to make informed decisions about whether and how the change should proceed.

Question 280. A business analyst is closing an initiative and wants to preserve information that could help future analysts avoid recurring problems. What should be captured?

1. Only the final number of requirements
2. Lessons learned, effective practices, challenges, decisions, and improvement opportunities
3. Only the project completion date
4. Only the names of the development team

Correct Answer: 2. Lessons learned, effective practices, challenges, decisions, and improvement opportunities

Explanation:
Closing business analysis work should include meaningful organizational learning. Lessons learned can capture what worked well, what created difficulties, how decisions were made, which practices were effective, and what should be improved in future initiatives. This information can help analysts reuse successful approaches and avoid repeating known problems. Administrative information such as completion dates or requirement counts may be useful for reporting but does not explain the experiences behind the initiative. Preserving relevant lessons supports continuous improvement of business analysis practices and organizational effectiveness.