ECBA Sample Questions Answers

Reusable requirements are those that can be applied across multiple projects or contexts without being tightly coupled to a specific solution. This is achieved by ensuring that the requirement is:

Technology-agnostic

Independent of a specific implementation

Focused on business rules or policies

Such characteristics make them valuable long-term assets for future initiatives.

BABOK® Reference:

Found in the Requirements Life Cycle Management knowledge area, under the task “Maintain Requirements,” which emphasizes maintaining requirements that may be reused across initiatives.

The task that provides stakeholders with business analysis information after the collated results are confirmed is " Communicate Business Analysis Information " , which falls under the Elicitation and Collaboration knowledge area. This task ensures that stakeholders have a shared understanding of the business analysis information, facilitating informed decision-making.

Reference from BABOK® Guide v3:

" Communicate Business Analysis Information: provides stakeholders with the business analysis information after the collated results are confirmed. "

— BABOK® Guide v3, Section 4.4

Checklists are a tool used by business analysts for quality control when verifying requirements and designs. They help ensure that all necessary steps are followed, and all important aspects are considered. Checklists can capture any identified issues and are used to confirm that nothing crucial is missed during the verification process.  This tool is particularly useful for specifying and modeling requirements, as it helps maintain the quality and completeness of the requirements documentation.  References : The use of checklists for quality control in business analysis is discussed in the context of verification activities, which are essential throughout the project lifecycle to maintain the validity of requirements and designs 1 .

Prioritization of requirements is not a one-time activity but a continuous process that occurs throughout the initiative. This approach allows for adjustments as new information is discovered, priorities shift, and the project evolves. It ensures that the most current and relevant requirements are being addressed at any given time, aligning with the changing needs and values of the business and stakeholders.

 The RACI Matrix is a tool used in business analysis to classify stakeholders according to their responsibility in a project. RACI stands for Responsible, Accountable, Consulted, and Informed. Each letter represents a level of task responsibility. The RACI Matrix clarifies the roles and responsibilities of stakeholders in a project, ensuring that everyone knows what is expected of them. This helps in avoiding confusion and overlapping of duties among stakeholders.

The correct answer is A . IIBA’s Business Analysis Standard and Agile business analysis principles emphasize thinking as a customer and analyzing to determine what is valuable . These ideas align directly with customer focus and value maximization , which are core drivers of effective business analysis work.

Option B is incorrect because although communication and planning matter, this combination does not reflect the central shared values highlighted by IIBA as the primary drivers of business analysis work.

Option C is incorrect because market assessment and management input may be useful in some contexts, but they are not presented by IIBA as the core shared values that broadly drive business analysis.

Option D is incorrect because courtesy and loss minimization are not the recognized IIBA shared values most associated with business analysis practice.

The active/noticeable observation approach involves the observer interacting with the subject , typically by asking questions as the work is being performed. This helps clarify steps, gather deeper insights, and validate the process as it unfolds. It contrasts with passive observation where the analyst simply watches without interrupting the workflow.

BABOK® Reference – Technique: Observation (Section 10.31):

“Active observation involves asking questions throughout the observation, while noticeable observation means the subjects are aware of being observed.”

When evaluating changes to requirements, in addition to the schedule, it is crucial to consider the number of customers and end-users affected by the change. This factor is important because it directly impacts the value delivery and satisfaction of the stakeholders.  The changes must align with the needs and expectations of the customers and end-users to ensure that the solution remains relevant and beneficial.  References : This consideration is supported by the Business Analysis Body of Knowledge (BABOK) guide, which emphasizes the importance of stakeholder engagement and value delivery in the requirements management and communication knowledge area 1 .

When undertaking requirements verification, the stakeholders who will be using the requirements are best positioned to determine if they are of good quality. These stakeholders have the practical experience and understanding of their needs and the context in which the requirements will be used. Their feedback ensures that the requirements are relevant, complete, and feasible. Involving stakeholders in the verification process helps in aligning the requirements with actual business needs and ensures that the final solution will be effective and satisfactory.

Considering both tangible and intangible costs and benefits provides a complete estimate of the solution’s value to the business. Tangible elements are directly measurable (e.g., cost savings, revenue), while intangible benefits (e.g., customer satisfaction, brand reputation) contribute to the strategic vision and long-term value.

Exact Extract from BABOK® Guide v3 – Section 7.6: Analyze Potential Value and Recommend Solution:

“Consideration should be given to both tangible and intangible value, including potential benefits and costs, to understand the overall impact of a proposed solution.”

The correct answer is C . IIBA explains that business analysis creates value by enabling change and improving outcomes across the organization, and this includes continuous evaluation and alignment of solutions with organizational goals. Monitoring and evaluating outcomes helps determine whether the change is delivering the intended value and where adjustments are needed to improve performance.

Option A is incorrect because documentation may support the organization, but documentation alone is not how business analysis primarily enhances organizational performance. Business analysis is focused on enabling value and better outcomes, not just producing artifacts.

Option B is incorrect because writing technology briefs is not a core description of how business analysis improves performance. It may be a communication activity in some contexts, but it does not represent the main performance-enhancing role of business analysis.

Option D is incorrect because business analysis does not narrow its focus only to implementation. IIBA frames business analysis as spanning strategy, initiative, and delivery contexts, with performance improvement requiring broader and ongoing evaluation.

The task Trace Requirements ensures that requirements and designs across different levels (business, stakeholder, solution) are consistently aligned with one another . This alignment supports scope management, impact analysis, verification and validation efforts, and change control.

Requirement tracing also:

Clarifies relationships between business needs and solution features.

Enables efficient scope monitoring and helps avoid scope creep.

Supports linking requirements to their source and derived components.

BABOK® Guide v3 – Section 5.1: Trace Requirements:

“The purpose of Trace Requirements is to ensure that requirements and designs at different levels are aligned to one another and to support change analysis, coverage, and allocation.”

When validating requirements, assumptions are defined so that the associated risks can be managed. Assumptions are considered to be true without proof for the purposes of planning and analysis, but they carry inherent risks if they prove to be incorrect. By defining assumptions clearly, business analysts and project teams can identify potential risks early in the process and develop strategies to address them, ensuring that the project remains on track and can adapt to any changes in circumstances.

An accepted practice is an example of a tacit business rule. Tacit business rules are those that are understood and followed by members of the organization but are not formally documented. They are often derived from the culture, norms, and shared understandings within the organization. These rules govern everyday behavior and decision-making processes implicitly, guiding how tasks are performed and how interactions occur without explicit instruction.

The correct answer is D . BABOK’s Collaborative Games technique explains that activities such as moving sticky notes, scribbling on whiteboards, or drawing pictures help participants overcome inhibitions , foster creativity, and think in different ways. These are all examples of a hands-on element , which makes option D the best answer.

Option A is incorrect because a take-home exploration step may support later reflection, but it is not identified by BABOK as the characteristic that most directly helps participants overcome inhibitions during the session itself.

Option B is incorrect because collaborative games in business analysis are meant to encourage shared understanding, creativity, and participation, not to emphasize rewards and penalties. That approach could even reduce openness in a newly formed group.

Option C is important for good facilitation, but the BABOK wording specifically points to interactive, physical participation as what helps people overcome inhibitions most effectively. That is why hands-on activity is the stronger answer here.

The purpose of brainstorming is to generate a large number of creative ideas in a short time, usually in a group setting. It is especially useful during early stages of analysis or design, where exploring multiple options is critical.

BABOK® Reference – Technique: Brainstorming (Section 10.5):

“Brainstorming is used to produce numerous new ideas, and to derive from them themes for further analysis.”

Understanding the scope of elicitation when initially assigned work is crucial for planning the business analysis approach. This involves determining the type of business analysis information to be discovered and selecting the appropriate techniques for elicitation. It requires a clear understanding of the business domain, corporate culture and environment, stakeholder locations, and the dynamics of the stakeholders involved.  This foundational step ensures that the business analysis activities are aligned with the project’s needs and objectives.  References : The answer is corroborated by the Business Analysis Body of Knowledge (BABOK) Guide, which emphasizes the importance of planning the business analysis approach as part of the scope of elicitation 1 .

Quality requirements relationships are determined by criteria that ensure the requirements are fundamentally sound. These criteria include:

Necessary : The requirement must be essential to meet the business need or opportunity.

Consistent : The requirement must not conflict with other requirements.

Correct : The requirement must accurately describe the functionality that will meet the business need or opportunity.

These criteria help in ensuring that the quality requirements are aligned with the business objectives and can be effectively implemented and managed.

The primary purpose of the interview technique is to elicit business analysis information directly from stakeholders through a structured or semi-structured conversation. Interviews are one of the most commonly used elicitation techniques and can be conducted individually or in small groups.

Key objectives of interviews include:

Discovering stakeholder needs, expectations, and experiences

Clarifying requirements and business rules

Validating assumptions and capturing detailed information

While interviews can also build trust and identify stakeholder roles, those are secondary benefits. The main goal remains to gather the information necessary to support analysis and define solutions.

BABOK® Reference:

Described in the Elicitation and Collaboration knowledge area, under the technique “Interviews,” where the technique’s primary application is to collect elicitation results by engaging stakeholders.

The end user is best positioned to verify that prioritized requirements will deliver value from a customer perspective because they directly interact with the solution and experience its outcomes. Their feedback ensures that the requirements meet usability, functionality, and satisfaction expectations.

While other stakeholders like the sponsor or domain SME validate alignment with business goals, the end user focuses on practical, value-based utility.

BABOK® Reference:

Throughout the BABOK®, particularly in Requirements Life Cycle Management and Solution Evaluation , the role of the end user is emphasized for validation and feedback based on real-world use.

The correct answer is C . In ECBA/BABOK, Confirm Elicitation Results is performed to ensure that the information gathered during elicitation is accurate and consistent with stakeholder understanding , and interviews are one of the techniques that can be used to communicate individually with stakeholders for that purpose. That makes the main objective here verifying that the requirements truly reflect the interviewees’ needs and expectations.

Option A is too narrow because usability and interface design feedback may be discussed in some interviews, but the question is specifically about confirming elicitation results , which is broader than UI feedback.

Option B is incorrect because ensuring that the CRM system meets all technical specifications is more related to solution design, verification, or testing activities, not the primary purpose of interviews used to confirm elicitation results.

Option D is incorrect because budget and resource allocation are not the main focus of this elicitation confirmation activity. The emphasis is on validating the captured needs and expectations with stakeholders.

When preparing for elicitation, Business Analysts (BAs) gather various supporting materials to ensure a comprehensive understanding of the current state and to facilitate effective stakeholder engagement. These materials provide context, background, and constraints that influence the requirements gathering process.

Key Supporting Materials:

System Documents: Include existing documentation such as system architecture diagrams, data flow diagrams, and user manuals. These help BAs understand the current systems in place.

Business Rules: Define the operations, definitions, and constraints that apply to an organization. Understanding these rules is crucial for identifying requirements that align with business operations.

Organizational Policies: Internal guidelines that govern business processes and decision-making. They provide insight into the organization ' s priorities and constraints.

Regulations: External legal and regulatory requirements that the organization must comply with. These are essential for ensuring that any proposed solutions are legally compliant.

Reference from BABOK® Guide v3:

The BABOK® Guide v3 emphasizes the importance of securing supporting materials during the preparation for elicitation. It states that BAs should identify and gather relevant information sources, including system documentation, business rules, organizational policies, and regulations, to inform the elicitation process effectively.

 Stakeholder requirements describe the needs of those participating in or impacted by business analysis activities. These requirements focus on ensuring that the perspectives and needs of all stakeholders are considered and integrated into the solution.  Stakeholder requirements are essential for understanding the context of the business needs and for defining the criteria for the success of the solution.  References : The information is verified as per the Business Analysis Learning documents, specifically the BABOK Guide, which outlines the types of requirements including Business, Stakeholder, Solution, and Transition Requirements 1 .

The role of a business analyst is pivotal in discovering, synthesizing, and analyzing information from various sources within an enterprise. This includes gathering data from tools, processes, documentation, and stakeholders. Business analysts are tasked with eliciting the true needs of stakeholders, which often involves investigating and clarifying their expressed desires to determine underlying issues and causes. They play a crucial role in aligning the designed and delivered solutions with the needs of stakeholders, ensuring that the outcomes meet business objectives effectively.

 A focus group is a qualitative research method used to gather in-depth insights and opinions from a group of individuals about a particular product, service, concept, or idea. It involves a small number of participants, typically 6-10, who are selected based on shared characteristics such as demographics, interests, or experiences. The discussion is moderated by a trained facilitator who encourages participants to share their thoughts, feelings, and attitudes towards the topic. This method is particularly effective for exploring perceptions, opinions, and ideas, making it a valuable tool for business analysis.

An atomic requirement is one that is self-contained and can be understood independently of other requirements or designs. It encapsulates a single piece of functionality or a single need without reference to other requirements. This characteristic ensures that the requirement can be considered, implemented, and tested on its own merits. Atomic requirements are essential for clear communication, effective analysis, and traceability throughout the project lifecycle.

Transition requirements are the only category of requirements that are temporary in nature . They define the capabilities that a solution must have to facilitate the transition from the current state to the future state , but they are not needed once the transition is complete. These include data conversion, training, and deployment needs.

They support the implementation but are not part of the long-term functioning solution. This distinguishes them from business, stakeholder, and solution requirements, which are ongoing or permanent once implemented.

BABOK® Guide v3 – Section 2.3.4: Transition Requirements:

“Transition requirements describe the capabilities that the solution must have to facilitate transition from the current state to the future state, but that will not be needed once that transition is complete.”

In the context of business analysis, a requirements viewpoint refers to a perspective or lens through which requirements are formulated and understood. A use case is an example of a requirements viewpoint because it represents a sequence of actions, typically involving an actor and a system, to achieve a goal.  Use cases are used to capture functional requirements and describe how users will interact with a solution.  References : The BABOK Guide mentions use cases as a tool within the requirements analysis and design definition, which aligns with the concept of a requirements viewpoint 1 .

 Industry knowledge equips a business analyst with the understanding of market forces, customer segments, services, products, and regulations. This type of knowledge is crucial for BAs as it helps them to comprehend the external factors that influence the organization and its market position. It includes insights into the competitive landscape, regulatory environment, market trends, customer demographics, and product lifecycle, which are all essential for effective business analysis.

The correct answer is B . BABOK’s Process Analysis technique is specifically used to understand and improve business processes, including examining interfaces or hand-offs between roles and organizational units in order to remove errors and reduce or eliminate bottlenecks . That makes Process Analysis the best direct fit for this scenario. ( IIBA )

Option A is incorrect because item tracking focuses on monitoring issues or work items, but it is not the primary BABOK technique for examining bottlenecks in hand-offs between organizational units. ( IIBA )

Option C is incorrect because interviews can help gather supporting information, but they are not the best primary technique when the problem is specifically about analyzing process bottlenecks and hand-offs. ( IIBA )

The correct answer is C . IIBA’s Business Analysis Standard states that foundational competencies are the basic skills, abilities, and characteristics necessary to perform effective business analysis . This matches option C most closely because it focuses on the skills and capabilities needed for effective analysis.

Option A is incorrect because foundational competencies are not limited to customer service. They apply broadly to the business analyst’s effectiveness across analysis work, not specifically to serving customers. BABOK’s competency-related material covers areas such as analytical thinking, communication, interaction skills, business knowledge, and tools/technology.

Option B is incorrect because techniques and metrics are not the definition of foundational competencies. BABOK separates techniques from underlying competencies . Techniques are methods a business analyst may use, while competencies are the personal and professional capabilities that support effective performance.

Option D is also incorrect because strategies and approaches to identify work are more closely related to planning and methodological choices, not to foundational competencies themselves. The core idea behind foundational competencies is the analyst’s basic effectiveness in performing business analysis.

The integrated output that correctly reflects captured information agreed upon by business analysts and other stakeholders is the “Confirmed elicitation results.” This output is the culmination of the elicitation process where the information gathered is validated and agreed to be accurate and relevant, serving as a foundation for further analysis and decision-making.  References : This answer is verified by the information found in the Business Analysis Body of Knowledge (BABOK) and discussions on the topic from credible sources related to the IIBA ECBA certification 1 .

 The core concept that defines a specific way of satisfying one or more needs in a context is ‘Solution’. According to the Business Analysis Core Concept Model™ (BACCM™), a solution satisfies a need by resolving a problem faced by stakeholders or enabling stakeholders to take advantage of an opportunity. It is a specific response to a need within a given context, and it can vary significantly from one organization to another as different organizations or situations may require different solutions.

In the context of prioritizing requirements , risk refers to the difficulty of implementing a requirement or the likelihood that it cannot deliver its potential value . Risk-based prioritization considers uncertainties related to implementation, cost overruns, time delays, or failure to achieve desired outcomes. High-risk requirements may be prioritized lower unless mitigated effectively.

BABOK® Reference – Task: Prioritize Requirements (Section 5.2):

“Risk: the chance that the requirement cannot deliver the potential value, or that the solution may not deliver the expected benefit.”

When a stakeholder seeks to understand the logistics and scope of each elicitation activity, the Business Analyst should share the elicitation activity plan . This plan outlines the objectives, techniques, stakeholders involved, and the schedule for each elicitation activity, providing clarity and setting expectations.

Reference from BABOK® Guide v3:

" Prepare for Elicitation: describes the tasks that the business analyst performs to prepare for elicitation activities. It includes determining the types of activities, the techniques, and the logistics required. "

— BABOK® Guide v3, Section 4.1

In the context of business analysis, value is a critical factor that influences the prioritization of requirements. It reflects the benefit or outcome the requirement brings to the business, ensuring that the most beneficial requirements are addressed first to maximize the return on investment and meet the strategic goals of the organization.

The correct answer is B . ECBA/BABOK communication guidance emphasizes that business analysis information should be communicated using tailored messages that are appropriate for the audience. When stakeholders need an easier-to-understand version of a technical document, the analyst should reduce jargon and adapt the language and presentation to the audience’s level of understanding.

Option A is incorrect because leaving the rest of the document unchanged may still make the overall content difficult for stakeholders to understand. The communication should be tailored more broadly, not only in selected sections.

Option C is incorrect because adding more technical detail would usually make the document harder, not easier, for non-technical stakeholders to understand.

Option D is incorrect because maintaining the original structure without changes prioritizes consistency over comprehension. BABOK communication practices favor effectiveness for the audience over preserving the source format unchanged.

The correct answer is A . BABOK states that the purpose of Prioritize Requirements is to rank requirements in order of relative importance . IIBA also explains that prioritization considers factors such as value, risk, urgency, and dependencies so that analysis and delivery effort can focus on the most important items at a given time. That is why prioritization supports efficient allocation of time, budget, and effort.

Option B is too absolute and therefore incorrect. Prioritization does not mean ignoring all lower-priority items forever; it means sequencing attention based on importance and context.

Option C is incorrect because prioritization exists precisely because not all requirements have equal value or urgency. BABOK emphasizes ranking by relative importance, not treating everything the same.

Option D is incorrect because prioritization does not automatically eliminate requirements. It helps decide the order and emphasis of work, not simply remove items.

 A logical data model is used to abstract a ‘conceptual data model’ by incorporating normalization rules to manage data integrity and relationships. It serves as an abstraction layer that defines the relationships between different data elements, entities, and attributes, focusing on the business concepts and rules that govern the data. This model helps in organizing data to reduce redundancy and improve data integrity, ensuring that the data structure is optimized for both business understanding and database design.

Decision modelling and root cause analysis fall under the Rationale model category , which focuses on the reasoning, logic, and justification behind decisions or problem identification . These techniques help in tracing the rationale for actions, understanding why a particular problem exists, and determining how decisions align with business objectives.

Decision modelling helps map out choices and potential outcomes.

Root cause analysis identifies underlying causes of issues.

BABOK® Reference:

These are detailed under Requirements Analysis and Design Definition , particularly in modeling techniques categorized under Rationale models.

Business analysis information can be stored in many ways. Storage decisions depend on many factors such as who must access the information, how often they need to access it, and what conditions must be present for access. Organizational standards and tool availability also influence storage and access decisions. The business analysis approach defines how various tools will be used on the initiative and how the information will be captured and stored within those tools. Tools may shape the selection of business analysis techniques, notations to be used, and the way that information is organized.

In the context of business analysis, reviews are conducted to assess the content of a work product. The participants in these reviews typically include:

Author : The person who created the work product.

Reviewer : Individuals who evaluate the work product, looking for defects and areas of improvement.

Facilitator : The person who leads the review process, ensuring that the objectives are met and the process is efficient.

Scribe : The individual responsible for documenting the findings of the review.

These roles are essential to ensure that the work product is complete, valid, and meets the necessary quality standards.

 The task of planning stakeholder engagement is a crucial part of the business analysis planning and monitoring knowledge area. It involves identifying stakeholders, understanding their needs and expectations, and determining the best ways to engage them in the business analysis process.  Effective stakeholder engagement is essential for ensuring that the requirements and solutions developed align with stakeholder needs and contribute to project success.  References : The Business Analysis Planning and Monitoring knowledge area includes tasks such as planning the business analysis approach, stakeholder engagement, governance, information management, and identifying business analysis performance improvements 1 .

 In the context of business analysis, elicitation is the practice of collecting information from stakeholders and other sources. Observation is a key elicitation technique where the business analyst (BA) actively watches how users interact with a system or how processes are carried out. This technique allows the BA to gather insights that might not be captured through direct inquiries, as people may not be aware of their own work habits or may not communicate them effectively. Observation can be particularly useful for identifying discrepancies between what people say they do and what they actually do, leading to a more accurate understanding of the current state and requirements.

The correct answer is B . In BABOK, stakeholder engagement planning includes identifying the appropriate stakeholders for a given situation and determining how and when to communicate with them. When an unexpected issue blocks progress, the business analyst should first understand the issue sufficiently and determine which stakeholders are relevant before initiating communication or meetings. This avoids unnecessary confusion and ensures the right people are involved in resolving the problem. ( iiba.org )

Option A is incorrect because sending a summary to all stakeholders may be premature and may include people who are not directly impacted or needed. BABOK emphasizes identifying stakeholder characteristics, responsibilities, and collaboration needs rather than communicating indiscriminately. ( iiba.org )

Option C is incorrect because delaying action until a complete solution is found can worsen the blockage. Business analysis supports timely collaboration and issue escalation when necessary; waiting too long can increase project risk and reduce responsiveness. (iiba.org)

Option D is also incorrect because immediately scheduling a meeting with all stakeholders is not always appropriate. The analyst should first determine the nature of the issue and who needs to be involved. BABOK encourages purposeful stakeholder engagement, not automatic involvement of everyone. ( iiba.org )

Personal accountability is a critical behavioral characteristic for business analysis professionals. It ensures that the tasks performed meet stakeholder expectations by holding the professional responsible for their actions and decisions. Personal accountability drives a commitment to delivering quality work, adhering to timelines, and maintaining transparency in communication. This characteristic fosters trust and reliability, ensuring that stakeholders can depend on the business analyst to meet their needs and expectations effectively.

A requirement that describes the capabilities the solution must have and the conditions the solution must meet to facilitate transition from the current state to the future state, but which are not needed once the change is complete. They are differentiated from other requirements types because they are of a temporary nature.

In the context of Business Analysis, elicitation through experiments involves conducting controlled tests to obtain information. This method is used to identify results based on tests run in a controlled environment, which can include proof of concepts, observational studies, and prototypes. It is a systematic approach to discovering requirements by validating hypotheses through experimentation.

Confirming elicitation results is a critical step in the business analysis process. It ensures that the information gathered during elicitation is not only accurate but also aligns with other information. This confirmation process involves reviewing the elicited information to identify any discrepancies, errors, omissions, or conflicts.  By doing so, business analysts can guarantee that the information used as input for further analysis and decision-making is reliable and consistent, which is essential for the success of any business initiative.  References : The importance of confirming elicitation results for accuracy and consistency is highlighted in the BABOK® Guide, which serves as a standard for the practice of business analysis 1 2 .

A traceability repository is a critical tool in business analysis that helps in documenting the lineage of requirements. This means it records the origin, development, and interrelationships of each requirement throughout the project lifecycle. By maintaining this detailed record, the repository ensures that every requirement is aligned with business objectives and stakeholder needs, facilitating effective project management and goal attainment.

Key Benefits of a Traceability Repository:

Alignment with Business Objectives: Ensures that each requirement is directly linked to business goals, confirming that the project remains focused on delivering value.

Impact Analysis: Facilitates the assessment of the implications of changes in requirements, aiding in decision-making and risk management.

Scope Management: Helps in identifying and managing the scope of the project by tracking which requirements are included or excluded.

Verification and Validation: Supports the processes of verifying that the solution meets the requirements and validating that the requirements meet stakeholder needs.

Extract from BABOK® Guide v3:

“Requirements traceability identifies and documents the lineage of each requirement, including its backward traceability, its forward traceability, and its relationship to other requirements. Traceability is used to help ensure that the solution conforms to requirements and to assist in scope, change, risk, time, cost, and communication management.”

— BABOK® Guide v3, Section 5.1.2 Description

The correct answer is D . IIBA’s Business Analysis Standard explains that business analysis creates value throughout the organization , across strategic, tactical, and operational levels , and over various timeframes . It also emphasizes continuously assessing and prioritizing work to maximize the value being delivered. Because option D includes both continuous evaluation and alignment with immediate and long-term goals , it is the best match to the IIBA view of value creation.

Option A is incorrect because it focuses too narrowly on short-term needs and compliance. IIBA’s framework is broader and includes long-term strategic outcomes in addition to tactical and operational value.

Option B is incomplete. Stakeholder feedback is important in business analysis, but value is not created only by responding to stakeholder preferences. IIBA ties value creation to achieving desired outcomes, making sound decisions, and aligning work across multiple organizational horizons.

Option C is not the best answer because it is too narrow and software-focused. Business analysis is not limited to software delivery, and IIBA defines it much more broadly as enabling change and delivering value across the organization.

The correct answer is A . BABOK explicitly states that Business Capability Analysis is used to assess performance and associated risks in order to identify specific performance gaps and prioritize investments , and it is also referenced in strategy analysis as a technique used to prioritize capability gaps in relation to value and risk . That matches the question almost exactly.

Option B is incorrect because benchmarking compares the organization to others, but the question is specifically about identifying internal capability gaps and prioritizing them by value and risk . Benchmarking may provide context, but it is not the best BABOK technique for this objective.

Option C is incorrect because a market capability survey is not the BABOK technique named for this purpose. The ECBA exam is typically looking for the standard BABOK technique terminology, and here that is Business Capability Analysis.

Option D is incorrect because SWOT analysis helps identify strengths, weaknesses, opportunities, and threats, but it does not specifically focus on capability gaps prioritized by value and risk the way Business Capability Analysis does.

The correct answer is C . BABOK states that the purpose of Plan Business Analysis Governance is to define how decisions are made about requirements and designs, including reviews, change control, prioritization, and approvals. IIBA’s task card further states that this output includes the list of decision-makers and a description of the approval processes. That is exactly what the question is asking for.

Option A is incorrect because Plan Business Analysis Information Management focuses on how business analysis information is captured, stored, and accessed, not on defining who the decision makers are or how approval decisions are made. This is a governance matter, not an information management matter.

Option B is incorrect because Maintain Requirements and Designs deals with the ongoing accuracy, reuse, and maintenance of requirements and designs. It does not define the approval authorities or decision-making structure.

Option D is incorrect because Validate Elicitation is not the BABOK task that establishes decision authority or governance. Elicitation-related tasks focus on gathering, confirming, and communicating information, not defining who approves requirements.

Identify Improvement OpportunitiesWhen proposing design options, a number of opportunities to improve the operation of the business may occur and are compared.Some common examples of opportunities include:

Increase Efficiencies: automate or simplify the work people perform by re-engineering or sharing processes, changing responsibilities, or outsourcing. Automation may also increase consistency of behaviour, reducing the likelihood of different stakeholders performing the same function in distinctly different fashions.

Improve Access to Information: provide greater amounts of information to staff who interface directly or indirectly with customers, thereby reducing the need for specialists.

Identify Additional Capabilities: highlight capabilities that have the potential to provide future value and can be supported by the solution. These capabilities may not necessarily be of immediate value to the organization (for example, a software application with features the organization anticipates using in the future).

 Stakeholders often face challenges in prioritizing requirements due to different perceived values. This challenge arises because stakeholders may have varying opinions on what is most important, leading to conflicts and difficulties in reaching a consensus on priority. The diversity in stakeholders’ backgrounds, roles, and interests can result in a wide range of perspectives on which requirements should take precedence.