View Full IIBA CBAP Exam Dumps and Practice Test Dumps

 

Question 101. A business analyst is asked to determine the level of detail required in a requirements model. What should primarily influence this decision?

1. The analyst’s preferred modeling style
2. The number of developers assigned to the project
3. The complexity, purpose, audience, and risks associated with the model
4. The length of the project schedule

Correct Answer: 3. The complexity, purpose, audience, and risks associated with the model

Explanation:
The appropriate level of detail in a requirements model depends on its purpose and context. The business analyst should consider the complexity of the requirement, intended audience, risks, decisions the model must support, and how the information will be used. A highly detailed model may be appropriate for complex or high-risk requirements, while a simpler representation may be sufficient for straightforward needs. The analyst’s personal preference or project staffing level should not determine modeling detail. Tailoring the model improves communication and ensures that analysis provides useful information without unnecessary complexity.

Question 102. A business analyst is determining whether a requirement is consistent with another approved requirement. Which quality characteristic is being evaluated?

1. Completeness
2. Consistency
3. Feasibility
4. Prioritization

Correct Answer: 2. Consistency

Explanation:
Consistency means that requirements do not contradict or conflict with one another. When a business analyst compares a requirement with another approved requirement to identify incompatible statements, the analyst is evaluating consistency. Completeness concerns whether necessary information is present, feasibility considers whether a requirement can realistically be satisfied, and prioritization determines relative importance or delivery order. Checking consistency is an important part of requirements verification because contradictory requirements can create confusion, implementation defects, and stakeholder disagreement.

Question 103. A stakeholder requests that a requirement be changed after it has been formally approved. What should the business analyst do?

1. Update the requirement immediately without review
2. Reject every change after approval
3. Delete the original requirement and replace it
4. Assess the proposed change according to the established change-control process

Correct Answer: 4. Assess the proposed change according to the established change-control process

Explanation:
Once requirements have been formally approved, changes should generally follow the established governance or change-control process. The business analyst should understand the reason for the change, assess its impact on related requirements, scope, value, risks, costs, and dependencies, and obtain the appropriate approval. Immediate informal modification can undermine traceability and governance. Automatically rejecting every change is also inappropriate because legitimate business conditions may require approved requirements to evolve. Controlled assessment ensures that stakeholders understand the consequences before deciding whether the change should be accepted.

Question 104. A business analyst needs to determine whether a proposed requirement is achievable within known technical and organizational constraints. Which characteristic should be assessed?

1. Feasibility
2. Consistency
3. Traceability
4. Stakeholder popularity

Correct Answer: 1. Feasibility

Explanation:
Feasibility concerns whether a requirement or proposed solution can realistically be achieved within applicable constraints. These may include technology, resources, budget, time, organizational capabilities, regulations, and other limitations. Consistency examines whether requirements conflict with one another, while traceability establishes relationships among requirements and related information. Stakeholder popularity does not determine whether a requirement can actually be implemented. Assessing feasibility early helps prevent investment in requirements that cannot reasonably be satisfied or would require unacceptable compromises.

Question 105. A business analyst is analyzing a business process and discovers that two departments perform nearly identical activities independently. What should the analyst investigate?

1. Whether the duplication creates inefficiency or an opportunity for process improvement
2. Which department has the larger budget
3. Whether both departments use identical job titles
4. Whether the process documentation uses the same font

Correct Answer: 1. Whether the duplication creates inefficiency or an opportunity for process improvement

Explanation:
Duplicate activities across departments may indicate unnecessary effort, inconsistent outcomes, or opportunities to improve the process. The business analyst should investigate why the duplication exists, whether it provides legitimate business value, and whether consolidation or standardization could improve performance. Budget size, job titles, and documentation formatting do not establish whether duplicated activities are appropriate. Process analysis should consider business objectives, controls, dependencies, risks, and stakeholder needs before recommending a change rather than assuming every duplicated activity is unnecessary.

Question 106. A business analyst is documenting how a customer request moves through several business activities, decisions, and outcomes. Which model would best represent this flow?

1. Capability map
2. Process model
3. Stakeholder matrix
4. Data dictionary

Correct Answer: 2. Process model

Explanation:
A process model represents the flow of activities, decisions, events, participants, and outcomes involved in performing business work. It can help stakeholders understand how a customer request moves through the organization and identify bottlenecks, unnecessary steps, or control points. A capability map describes what the organization is capable of doing at a higher level, a stakeholder matrix describes stakeholder characteristics, and a data dictionary defines data elements. A process model is therefore the appropriate representation for analyzing the sequence and flow of business activities.

Question 107. A business analyst is identifying restrictions that limit the possible solution designs, such as a fixed regulatory requirement and a maximum budget. What should these restrictions be documented as?

1. Assumptions
2. Business outcomes
3. Constraints
4. Stakeholder personas

Correct Answer: 3. Constraints

Explanation:
Constraints are restrictions or limitations that affect the possible solution or approach. Examples include regulatory obligations, fixed budgets, mandatory technologies, deadlines, organizational policies, or contractual conditions. Assumptions are conditions believed to be true for analysis purposes but may require validation. Business outcomes describe desired results, while personas represent characteristics and goals of user types. Clearly documenting constraints helps stakeholders understand the boundaries within which solution alternatives must be evaluated and prevents analysts from considering options that cannot realistically be pursued.

Question 108. A business analyst is evaluating several solution alternatives. One option has a higher initial cost but may produce significantly greater long-term benefits. What should the analyst provide to decision-makers?

1. Only the initial purchase cost
2. A comparison of relevant costs, benefits, risks, and other evaluation criteria
3. The option preferred by the technical team
4. The option with the shortest implementation schedule

Correct Answer: 2. A comparison of relevant costs, benefits, risks, and other evaluation criteria

Explanation:
Solution alternatives should be evaluated using criteria relevant to the decision rather than a single factor. A higher initial cost may be justified if an alternative provides greater benefits, lower long-term costs, reduced risks, or other important advantages. The business analyst should present the relevant trade-offs so decision-makers can understand the consequences of each option. Focusing only on purchase price or implementation speed can produce an incomplete analysis. The evaluation criteria should reflect stakeholder priorities, business objectives, constraints, and the decision context.

Question 109. A business analyst is determining whether stakeholders have approved a requirement or merely provided feedback on it. What should the analyst verify?

1. The requirement’s font size
2. The stakeholder’s job title only
3. The defined approval authority and documented decision status
4. The number of times the requirement was discussed

Correct Answer: 3. The defined approval authority and documented decision status

Explanation:
A stakeholder providing comments does not necessarily mean that the requirement has been formally approved. The business analyst should understand who has decision authority and how approval decisions are documented within the organization’s governance process. Confirming the requirement’s status helps prevent unapproved information from being treated as an authorized baseline. Job title alone may not establish decision rights, while discussion frequency and formatting are unrelated to approval status. Clear decision records improve governance, traceability, and communication throughout the requirements life cycle.

Question 110. A business analyst is reviewing a requirement that states, “The system will process transactions quickly.” What is the primary problem with this statement?

1. It does not identify the development team
2. It is too detailed
3. It contains a dependency
4. The term “quickly” is ambiguous and not objectively measurable

Correct Answer: 4. The term “quickly” is ambiguous and not objectively measurable

Explanation:
A requirement should be sufficiently clear and measurable to allow stakeholders to determine whether it has been satisfied. The term “quickly” can mean different things to different users and therefore does not provide an objective performance threshold. The business analyst should clarify the expected response time or processing duration and define appropriate acceptance criteria. A measurable requirement could specify a response time under defined conditions. Removing ambiguity improves shared understanding, supports testing, and reduces the possibility of disputes about whether the solution meets the intended requirement.

Question 111. A business analyst is assessing whether a proposed solution can support an expected increase in transaction volume over the next three years. Which solution characteristic should be examined?

1. Scalability
2. Stakeholder authority
3. Organizational hierarchy
4. Requirements ownership

Correct Answer: 1. Scalability

Explanation:
Scalability concerns a solution’s ability to handle increasing workloads or demand without unacceptable degradation in performance or other characteristics. If transaction volume is expected to grow substantially, scalability should be analyzed as part of the solution’s non-functional requirements and evaluation. Stakeholder authority and requirements ownership concern governance and management rather than solution capacity. Organizational hierarchy also does not establish whether a system can accommodate increased transaction volume. Defining expected growth and measurable scalability criteria can help ensure that the solution remains suitable as business demand changes.

Question 112. A business analyst is preparing a requirements package for stakeholders who have different levels of technical knowledge. What is the most appropriate communication approach?

1. Use highly technical terminology for everyone
2. Provide information tailored to each audience while maintaining consistent meaning
3. Give nontechnical stakeholders no requirements information
4. Allow each stakeholder to interpret technical terms independently

Correct Answer: 2. Provide information tailored to each audience while maintaining consistent meaning

Explanation:
Effective business analysis communication considers the audience’s knowledge, responsibilities, information needs, and decision-making role. Technical stakeholders may require detailed technical information, while business stakeholders may need emphasis on outcomes, impacts, and business rules. Tailoring presentation does not mean changing the underlying requirement or creating contradictory versions. Consistent meaning should be preserved across communication formats. Using highly technical language with every audience can reduce understanding, while excluding stakeholders prevents informed participation. Appropriate tailoring improves clarity and stakeholder engagement.

Question 113. A business analyst identifies that a proposed requirement supports one business objective but conflicts with another organizational objective. What should the analyst do?

1. Automatically prioritize the requirement
2. Remove both objectives from analysis
3. Analyze the trade-off and present the conflict to the appropriate decision-makers
4. Allow the development team to resolve the conflict

Correct Answer: 3. Analyze the trade-off and present the conflict to the appropriate decision-makers

Explanation:
When a requirement supports one objective but conflicts with another, the business analyst should make the trade-off visible rather than resolving it through personal preference. The analyst should examine the impact, value, risks, dependencies, and strategic implications associated with the competing objectives. The appropriate decision-makers can then determine how the conflict should be resolved according to organizational priorities and governance. Automatically prioritizing one objective or delegating the decision to developers bypasses the business decision that is actually required.

Question 114. A business analyst is asked to determine whether a proposed process improvement is producing the expected reduction in processing time. What should be established before evaluation?

1. A measurable performance baseline and target
2. A new project logo
3. The preferred meeting schedule
4. The number of analysts assigned to the project

Correct Answer: 1. A measurable performance baseline and target

Explanation:
To evaluate whether a process improvement achieved its intended effect, the analyst needs a meaningful basis for comparison. A baseline describes performance before the change, while a target represents the expected future performance. Comparing actual results against these measures provides evidence about whether processing time improved as intended. Without a baseline or measurable target, it may be difficult to determine the magnitude or significance of the change. Project branding, meeting schedules, and analyst staffing do not provide evidence about process performance.

Question 115. A business analyst needs to determine whether all important requirements have been identified for a particular stakeholder group. Which quality characteristic is most relevant?

1. Completeness
2. Volatility
3. Priority
4. Reusability

Correct Answer: 1. Completeness

Explanation:
Completeness concerns whether the necessary information and requirements have been sufficiently identified for the relevant scope and purpose. When evaluating whether important stakeholder needs have been captured, the analyst should look for missing requirements, scenarios, conditions, or relevant information. Volatility describes the likelihood of change, priority describes relative importance, and reusability concerns whether requirements or models can be used in other contexts. Completeness does not necessarily mean every possible detail has been documented; rather, it means the required information for the intended purpose has been adequately addressed.

Question 116. A business analyst is evaluating a proposed change that may affect several related requirements. What should the analyst determine before recommending approval?

1. Only whether the requester is senior enough
2. The change’s impacts, dependencies, risks, costs, and expected value
3. Whether the requirement can be shortened
4. Whether the change has been discussed informally

Correct Answer: 2. The change’s impacts, dependencies, risks, costs, and expected value

Explanation:
A change should be evaluated based on its consequences and expected value rather than simply the authority or preference of the requester. The business analyst should identify affected requirements, dependencies, scope, risks, costs, benefits, and other relevant impacts. This information allows decision-makers to understand the trade-offs associated with approving the change. Informal discussion may provide useful input but does not replace structured impact analysis. Assessing the full effect of a change supports controlled requirements management and reduces unintended consequences.

Question 117. A business analyst is creating a model that describes the capabilities an organization needs rather than the detailed sequence of activities used to perform them. Which model is most appropriate?

1. Process model
2. Use case diagram
3. Capability model
4. Decision table

Correct Answer: 3. Capability model

Explanation:
A capability model represents what an organization is able to do or needs to be able to do, generally without prescribing the detailed sequence of activities used to perform those capabilities. Capability models are useful for analyzing current and future organizational abilities and identifying capability gaps. Process models focus on the flow of activities, use case diagrams focus on interactions between actors and solutions, and decision tables represent conditional business rules. Keeping capability analysis separate from detailed process analysis helps stakeholders understand organizational needs at the appropriate level.

Question 118. A business analyst is validating a proposed requirement with stakeholders. One stakeholder confirms it, but another affected stakeholder says it does not represent their need. What should the analyst do?

1. Accept the first stakeholder’s confirmation as sufficient
2. Remove the second stakeholder from the analysis
3. Investigate the differing needs and facilitate resolution with the relevant stakeholders
4. Ask developers to choose which stakeholder is correct

Correct Answer: 3. Investigate the differing needs and facilitate resolution with the relevant stakeholders

Explanation:
Different affected stakeholders may have legitimate but competing needs. The business analyst should understand the reasons for the disagreement, determine whether the requirement needs clarification or modification, and facilitate discussion among the appropriate stakeholders. Treating one stakeholder’s confirmation as automatically sufficient can overlook important requirements. Developers should not independently resolve business priority conflicts unless they have been given that decision authority. Structured collaboration helps reveal the underlying needs and enables the appropriate decision-makers to resolve competing expectations.

Question 119. A business analyst wants to determine whether a requirement contributes directly to a measurable business outcome. What should the analyst establish?

1. A relationship between the requirement and the relevant business objective or outcome measure
2. The requirement’s position in the document
3. The number of words in the requirement
4. The developer assigned to implement it

Correct Answer: 1. A relationship between the requirement and the relevant business objective or outcome measure

Explanation:
Connecting requirements to business objectives and measurable outcomes helps demonstrate why the requirement exists and how it contributes value. This relationship supports prioritization, traceability, validation, and later solution evaluation. A requirement’s document position, word count, or assigned developer does not demonstrate business contribution. The analyst should identify the relevant objective, expected outcome, or performance measure and establish the relationship through appropriate requirements information. This makes it easier to evaluate whether the requirement remains relevant as the initiative progresses.

Question 120. A business analyst has completed a major initiative and wants to improve the organization’s future business analysis practices. What should the analyst capture?

1. Only the final project budget
2. Lessons learned, successful practices, challenges, and improvement opportunities
3. Only unresolved stakeholder disagreements
4. Only the original project schedule

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

Explanation:
Lessons learned provide valuable organizational knowledge that can improve future business analysis work. The analyst should capture successful practices, challenges encountered, decisions that worked well, problems that caused rework, and opportunities for improvement. Focusing only on the budget, unresolved disagreements, or original schedule does not provide a complete picture of what the organization can learn. Capturing and sharing relevant lessons supports continuous improvement, helps future analysts avoid recurring problems, and strengthens organizational business analysis practices over time.