View Full IIBA CBAP Exam Dumps and Practice Test Dumps

 

Question 161. A business analyst is determining how requirements should be approved and maintained throughout an initiative. What should be established?

1. A requirements governance approach
2. A development team’s coding standard
3. A marketing communication plan
4. A user-interface color scheme

Correct Answer: 1. A requirements governance approach

Explanation:
Requirements governance defines how requirements are reviewed, approved, changed, maintained, and controlled throughout an initiative. It should establish decision authority, approval processes, change procedures, roles, and other relevant controls. A governance approach helps ensure that requirements remain consistent with organizational policies and that changes are managed transparently. Coding standards, marketing plans, and interface design address different concerns. Establishing requirements governance early helps stakeholders understand how decisions will be made and prevents informal changes from undermining the integrity of approved requirements.

Question 162. A business analyst is evaluating whether a proposed solution can be implemented using the organization’s available technology and skills. Which aspect of feasibility is being examined?

1. Market feasibility
2. Technical feasibility
3. Organizational culture
4. Stakeholder influence

Correct Answer: 2. Technical feasibility

Explanation:
Technical feasibility examines whether the proposed solution can be developed and operated using available or attainable technology, infrastructure, skills, and technical capabilities. It may include considerations such as system integration, performance, security, architecture, technical resources, and technology constraints. Organizational culture and stakeholder influence may affect other aspects of feasibility but do not directly determine technical feasibility. Evaluating this area helps stakeholders understand whether a proposed solution is realistically achievable from a technology perspective before significant resources are committed.

Question 163. A business analyst is determining whether a requirement is stated at an appropriate level and does not contain unnecessary implementation details. What should the analyst examine?

1. Whether the requirement is solution-independent where appropriate
2. Whether the requirement has the longest possible description
3. Whether the requirement uses technical terminology throughout
4. Whether the requirement was written by a developer

Correct Answer: 1. Whether the requirement is solution-independent where appropriate

Explanation:
Requirements should describe the need or expected capability at an appropriate level without unnecessarily constraining the solution. Solution-independent requirements allow alternative approaches to be evaluated and reduce the risk of prematurely selecting a particular implementation. This does not mean technical details are never appropriate; they may be required when constraints or technical requirements are explicitly part of the business need. The analyst should distinguish between genuine constraints and unnecessary design decisions. This helps preserve flexibility while maintaining sufficient detail for understanding and validation.

Question 164. A stakeholder provides a requirement that conflicts with a mandatory legal obligation. What should the business analyst do?

1. Implement the stakeholder’s requirement first
2. Ignore the legal obligation if implementation is difficult
3. Analyze the conflict and ensure applicable legal obligations are addressed through the appropriate decision process
4. Remove all requirements related to the stakeholder

Correct Answer: 3. Analyze the conflict and ensure applicable legal obligations are addressed through the appropriate decision process

Explanation:
Legal and regulatory obligations can impose mandatory constraints on a solution. When a stakeholder requirement conflicts with such an obligation, the business analyst should identify the conflict, understand its implications, and involve the appropriate stakeholders or governance authority. The analyst should not simply implement the conflicting requirement or ignore the legal obligation because implementation is difficult. Resolving the conflict may require changing the requirement, changing the proposed solution, or escalating the decision. Proper analysis helps maintain compliance while preserving as much stakeholder value as possible.

Question 165. A business analyst wants to understand how a new capability could affect existing organizational roles. What should the analyst examine?

1. Role responsibilities, decision rights, skills, and workflow impacts
2. Only the organization’s office layout
3. Only the current project budget
4. The number of pages in role documentation

Correct Answer: 1. Role responsibilities, decision rights, skills, and workflow impacts

Explanation:
Introducing a new capability can change who performs activities, who makes decisions, what skills are required, and how work flows through the organization. The business analyst should assess these role-related impacts to identify organizational changes, training needs, transition requirements, and potential risks. Office layout and document length do not establish the effect on organizational roles. Budget information may be relevant to implementation but does not explain role impacts. Understanding these changes helps ensure that the organization is prepared to operate the future-state capability effectively.

Question 166. A business analyst is reviewing a set of requirements to determine whether each one can be linked to an identified source or stakeholder need. What practice supports this review?

1. Requirements traceability
2. Organizational restructuring
3. Technical prototyping only
4. Project scheduling

Correct Answer: 1. Requirements traceability

Explanation:
Requirements traceability establishes relationships between requirements and their sources, such as business objectives, stakeholder needs, business rules, or other requirements. Reviewing these relationships helps the analyst determine whether requirements have a valid origin and remain justified. Traceability can also support impact analysis, verification, validation, and change management. Organizational restructuring and project scheduling address different concerns, while prototyping alone does not establish the origin or business justification of requirements. Maintaining traceability helps preserve the connection between identified needs and delivered capabilities.

Question 167. A business analyst is deciding whether a requirement should be mandatory, desirable, or optional for an upcoming release. What should the analyst facilitate?

1. Prioritization using agreed criteria and stakeholder input
2. Selection based only on document order
3. Selection based only on developer preference
4. Automatic inclusion of every requirement

Correct Answer: 1. Prioritization using agreed criteria and stakeholder input

Explanation:
Prioritization determines the relative importance of requirements and helps stakeholders make decisions when resources or delivery capacity are limited. The business analyst should facilitate agreement on relevant criteria, which may include business value, urgency, risk, dependencies, cost, regulatory obligations, and strategic alignment. Stakeholder input is important because different requirements may affect different business interests. Document order and developer preference are not sufficient prioritization methods. A transparent approach helps stakeholders understand why requirements receive different priority levels and supports consistent release planning.

Question 168. A business analyst is examining a proposed process and wants to identify activities that do not contribute to the desired business outcome. What should the analyst do?

1. Analyze the process for unnecessary activities and their underlying causes
2. Remove activities immediately without stakeholder review
3. Focus only on the process documentation format
4. Ask the technical team to redesign the process without analysis

Correct Answer: 1. Analyze the process for unnecessary activities and their underlying causes

Explanation:
Process analysis can identify activities that add little or no value, create delays, duplicate work, or contribute to unnecessary complexity. However, an activity should not be removed simply because it appears unnecessary; it may provide a control, compliance function, risk mitigation, or other important purpose. The analyst should understand the activity’s purpose, dependencies, costs, risks, and contribution to outcomes before recommending change. Stakeholder and process-owner input can help validate the findings and ensure that proposed improvements do not create unintended consequences.

Question 169. A business analyst is determining whether stakeholders understand the implications of a proposed solution option. What should the analyst communicate?

1. Relevant benefits, costs, risks, assumptions, constraints, and trade-offs
2. Only the preferred option
3. Only technical implementation details
4. Only the project’s completion date

Correct Answer: 1. Relevant benefits, costs, risks, assumptions, constraints, and trade-offs

Explanation:
Stakeholders need sufficient information to understand the consequences of solution alternatives. The business analyst should communicate relevant benefits, costs, risks, assumptions, constraints, dependencies, and trade-offs. Presenting only one preferred option can hide important alternatives and reduce transparency. Technical details may be appropriate for certain audiences but are not enough to support broader business decisions. Providing balanced decision information enables stakeholders to evaluate alternatives against agreed objectives and make informed choices within the appropriate governance structure.

Question 170. A business analyst is asked to determine whether a proposed solution addresses all relevant stakeholder needs without introducing unnecessary functionality. What should be evaluated?

1. The alignment between stakeholder requirements, solution scope, and delivered capabilities
2. Only the number of screens in the solution
3. Only the development team’s workload
4. The visual consistency of project documents

Correct Answer: 1. The alignment between stakeholder requirements, solution scope, and delivered capabilities

Explanation:
Solution scope should reflect the requirements and needs that the initiative is intended to address. The analyst should evaluate whether relevant stakeholder requirements are covered and whether delivered capabilities fall within the agreed scope. This can reveal missing functionality, unnecessary additions, or scope expansion. Screen count and development workload may provide supporting information but do not establish alignment with stakeholder needs. Reviewing the relationship among requirements, scope, and capabilities helps ensure that the solution delivers what is needed without introducing unjustified functionality.

Question 171. A business analyst identifies a requirement that depends on information supplied by an external business process. What should be documented?

1. The dependency and the conditions required for the information to be available
2. Only the requirement’s title
3. The stakeholder’s personal preference
4. The project team’s office location

Correct Answer: 1. The dependency and the conditions required for the information to be available

Explanation:
Requirements that depend on external processes or information sources should have those dependencies identified and documented. The analyst should understand what information is required, where it originates, when it must be available, who is responsible for providing it, and what risks exist if the dependency fails. Documenting these relationships supports impact analysis, solution design, testing, and operational planning. Ignoring the dependency can create unexpected failures when the solution is implemented. Clear dependency information also helps stakeholders coordinate responsibilities across organizational boundaries.

Question 172. A business analyst is validating a future-state process with stakeholders. One participant proposes a change that improves one department’s performance but creates additional work for another. What should the analyst do?

1. Evaluate the cross-functional impact and facilitate discussion of the trade-off
2. Accept the change because one department benefits
3. Reject the change because all departments must have identical workloads
4. Allow the affected departments to resolve it without analysis

Correct Answer: 1. Evaluate the cross-functional impact and facilitate discussion of the trade-off

Explanation:
Process changes can create benefits in one area while introducing costs or risks elsewhere. The business analyst should examine the overall organizational impact rather than optimizing one department in isolation. Relevant effects may include workload, cost, cycle time, customer experience, risk, controls, and strategic value. Facilitating discussion allows stakeholders to understand the trade-offs and determine whether the overall outcome is acceptable. The analyst should provide evidence and facilitate the decision rather than automatically favoring one department or requiring identical workloads.

Question 173. A business analyst is reviewing requirements and finds that one requirement has no identifiable stakeholder, business objective, or other source. What should the analyst investigate?

1. Its justification and whether it is still necessary
2. Whether it should automatically receive the highest priority
3. Whether it can be made longer
4. Whether a developer can implement it quickly

Correct Answer: 1. Its justification and whether it is still necessary

Explanation:
Requirements should have an understandable reason for existing, such as a business objective, stakeholder need, business rule, regulatory obligation, or other valid source. If a requirement has no identifiable justification, the analyst should investigate its origin and determine whether it remains necessary. Lack of traceability does not automatically mean the requirement should be deleted, but it is a signal that additional analysis may be needed. Understanding its purpose helps prevent unnecessary scope and ensures that requirements continue to contribute to legitimate business needs.

Question 174. A business analyst is preparing a recommendation and wants decision-makers to understand the uncertainty surrounding some analysis results. What should the analyst communicate?

1. Relevant assumptions, limitations, uncertainties, and their potential impact
2. Only the most favorable interpretation
3. Only the final recommendation
4. No uncertainty because it could confuse stakeholders

Correct Answer: 1. Relevant assumptions, limitations, uncertainties, and their potential impact

Explanation:
Good business analysis communicates not only conclusions but also important assumptions, limitations, and uncertainties that may affect those conclusions. Decision-makers need to understand the reliability and boundaries of the analysis so they can assess risks appropriately. Presenting only favorable information can create a misleading impression, while hiding uncertainty does not eliminate it. The analyst should explain what is known, what remains uncertain, and how uncertainty could affect the decision. This supports transparent and evidence-based decision-making.

Question 175. A business analyst is determining whether a requirement should be reused in another initiative. What should be assessed first?

1. Whether the requirement’s underlying need, context, and assumptions remain applicable
2. Whether the requirement has the longest description
3. Whether the same analyst wrote it
4. Whether the original project had the same number of stakeholders

Correct Answer: 1. Whether the requirement’s underlying need, context, and assumptions remain applicable

Explanation:
Requirements may sometimes be reused, but reuse should not be based solely on similar wording. The analyst should determine whether the underlying business need, context, assumptions, constraints, stakeholders, and expected outcomes are sufficiently similar. A requirement that was appropriate in one environment may be unsuitable in another. Reusing requirements without validation can introduce outdated assumptions or inappropriate constraints. Assessing applicability first allows useful business analysis information to be reused while ensuring that it remains valid for the new initiative.

Question 176. A business analyst is evaluating a solution after implementation and finds that users are not using an available feature. What should the analyst investigate before recommending its removal?

1. User awareness, training, usability, business need, and barriers to adoption
2. Only the feature’s development cost
3. Only whether the feature was included in the original requirements
4. Only the number of lines of code

Correct Answer: 1. User awareness, training, usability, business need, and barriers to adoption

Explanation:
Low feature usage does not necessarily mean the feature has no value. Users may not know that it exists, may lack training, may find it difficult to use, or may encounter process or organizational barriers. The business analyst should investigate these factors and determine whether the feature still addresses a valid need. Original requirements and development cost provide useful context but do not fully explain current usage. Understanding the cause of low adoption allows stakeholders to determine whether improvement, training, redesign, or removal is appropriate.

Question 177. A business analyst is determining how a change in one requirement could affect multiple downstream solution components. Which information would provide the strongest support?

1. A maintained traceability relationship between the requirement and related solution elements
2. An informal conversation with one developer
3. The project meeting calendar
4. The organization’s employee directory

Correct Answer: 1. A maintained traceability relationship between the requirement and related solution elements

Explanation:
Traceability provides structured relationships between requirements and related elements such as other requirements, solution components, test cases, business objectives, and deliverables. When a requirement changes, these relationships help the business analyst identify potentially affected areas and perform impact analysis. Informal conversations may provide useful supplementary information but are less reliable as the primary basis for systematic change assessment. Meeting calendars and employee directories do not establish relationships between requirements and solution components. Maintaining traceability throughout the initiative therefore supports controlled change management.

Question 178. A business analyst is asked to identify the people who have authority to approve a significant change to solution scope. What should the analyst determine?

1. The established decision rights and governance authority for scope changes
2. Which stakeholder has the most technical knowledge
3. Which stakeholder attends the most meetings
4. Which stakeholder requested the original solution

Correct Answer: 1. The established decision rights and governance authority for scope changes

Explanation:
Approval authority should be determined through the organization’s governance structure and defined decision rights. The person who requested a solution or has the most technical knowledge may not have authority to approve a scope change. Similarly, meeting attendance does not establish decision rights. The business analyst should identify the appropriate governance body or individual, understand the required approval process, and ensure that relevant impact information is available for the decision. Clear authority prevents unauthorized scope changes and supports consistent requirements governance.

Question 179. A business analyst is analyzing why a business process produces inconsistent results even though employees follow the same documented procedure. What should the analyst investigate?

1. Variations in inputs, business rules, resources, systems, and operating conditions
2. Only the procedure’s page count
3. Only employee job titles
4. Only the project manager’s communication style

Correct Answer: 1. Variations in inputs, business rules, resources, systems, and operating conditions

Explanation:
Identical documented procedures do not always produce identical outcomes because other process conditions may vary. The analyst should examine inputs, data quality, business rules, systems, resources, workload, skills, timing, controls, and other environmental factors. This can reveal hidden causes of process variation that are not visible in the written procedure. Focusing only on job titles or document characteristics is unlikely to explain inconsistent outcomes. Understanding these variations helps identify whether the issue is caused by the process itself, supporting conditions, or both.

Question 180. A business analyst is preparing to transition a solution into operational use. Which information is most important for identifying potential transition requirements?

1. Differences between the current state and the capabilities needed to operate the future state
2. Only the original project schedule
3. Only the solution’s marketing material
4. Only the number of development tasks completed

Correct Answer: 1. Differences between the current state and the capabilities needed to operate the future state

Explanation:
Transition requirements address temporary capabilities needed to move from the current state to the future state. To identify them, the business analyst should understand the differences between current and future processes, systems, data, roles, skills, and operational capabilities. These gaps may reveal needs for training, migration, temporary procedures, data conversion, communication, or transitional support. Project schedules and marketing materials do not by themselves identify these needs. Comparing current and future states provides a structured basis for determining what is required during transition.