ECBA Entry Certificate in Business Analysis (ECBA) Questions and Answers

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.”

After elicitation activities are performed, the purpose of comparing the results is to ensure consistency and accuracy across information gathered from various stakeholders or techniques. This comparison helps in identifying discrepancies, resolving conflicting inputs, and validating that stakeholder perspectives are properly reflected.

BABOK® Reference – Task: Confirm Elicitation Results (Section 4.3):

“The purpose of Confirm Elicitation Results is to check the information gathered during elicitation for accuracy and consistency with other information.”

Automating steps that are more routine and predictable is a common change made to improve a process. This approach helps in reducing human errors, speeding up the process, and freeing up human resources to focus on more complex tasks. Automation ensures consistency and reliability in the execution of routine tasks, leading to increased efficiency and productivity within the process. For example, implementing workflow management systems or straight-through processing can significantly enhance the efficiency of business operations.

Matrices in modeling formats are used to describe complex but uniform structures. They are particularly useful for breaking down and organizing complex requirements into a structured and understandable format. By inputting simple requirements into a matrix, business analysts can model requirements that are complex in nature but uniform in structure, such as those found in data dictionaries, gap analysis, and requirements traceability.

Prototyping is a requirements elicitation technique that involves creating a preliminary version of a system or product to validate and refine the stakeholders’ needs. It is an iterative process that helps in discovering requirements by providing a tangible representation of the product that stakeholders can interact with. This interaction allows stakeholders to give immediate feedback, which is then used to refine the prototype in subsequent iterations. Prototyping is particularly useful when stakeholders find it difficult to articulate their needs or when the requirements are not well understood.

A Business Analyst (BA) is primarily responsible for bridging the gap between business needs and technological solutions. They play a pivotal role in defining the solution approach, which includes understanding and interpreting both the business and technical aspects of a project. This involves identifying, analyzing, and documenting business requirements, and ensuring that the proposed solutions meet these requirements. BAs are not typically responsible for authorizing projects, approving execution plans, or accepting risk mitigation plans, as these tasks are generally within the purview of project managers or other stakeholders.

The optimum group size for brainstorming is six to eight individuals who represent a range of backgrounds and experiences with the topic. This size is considered ideal because it allows for a diverse set of ideas and perspectives, while still being manageable enough to ensure that everyone has an opportunity to contribute. Having participants from varied backgrounds enhances the creative process by introducing different viewpoints and experiences, thereby enriching the brainstorming session and leading to a broader range of innovative solutions .

A requirement can be of benefit to a stakeholder and still not be a desirable part of a solution. A requirement that does not deliver benefit to a stakeholder is a strong candidate for elimination. When requirements do not align, either the future state must be re- evaluated and the solution scope changed, or the requirement removed from the solution scope.

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.

In preparation for elicitation, a business analyst secures supporting material which is essential for the elicitation activities. This involves identifying and procuring all necessary information and resources that will be used during these activities. It includes gathering documents, systems information, historical data, and any other relevant materials that will support the elicitation process.

This statement is the formal definition of business analysis as provided by the BABOK® Guide. It emphasizes the role of the business analyst in enabling change by understanding and defining what an organization needs and proposing solutions that deliver value.

BABOK® Reference – Introduction (Section 1.2):

“Business analysis is the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders.”

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.

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.

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.”

 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.

Scope modelling is the technique used to identify the elements and boundaries of the requirements architecture. This technique involves defining what is included within the project or initiative and what is outside its boundaries. Scope modelling helps in clarifying the scope of the work, the features and functions that are to be included in the solution, and any constraints or limitations that should be considered. It provides a structured approach to understanding the overall context and limits of the change being proposed, ensuring that stakeholders have a common understanding of what the initiative aims to achieve and what it does not cover.

In the context of managing stakeholder engagement, business analysts (BAs) are particularly vigilant about the risk of scope creep. Scope creep refers to the uncontrolled expansion of project scope without adjustments to time, cost, and resources, which can occur when new requirements are added to the project without proper review. It is a common challenge in project management that can lead to project delays, budget overruns, and can compromise the quality of the final deliverable.

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.

Definitional rules are a type of business rule that form theories or produce information. They represent something that is fundamentally true or untrue about some concept within the organization. Unlike behavioral rules, which are about people’s behavior, definitional rules constitute operational knowledge of the organization. They cannot be violated but can be misused. For instance, a definitional rule might be used to classify different categories of customers based on contractual agreements or order quantities.

Systems thinking is a crucial skill for business analysts as it enables them to view the enterprise in a holistic manner. This approach helps BAs understand the complex interactions between people, processes, and technology within an organization. It involves recognizing patterns and interrelationships and considering how different systems work together and influence one another within the whole.  By applying systems thinking, BAs can better comprehend the broader impacts of any changes to one part of the system on the entire organization.  References : The BABOK® Guide outlines the importance of systems thinking as a competency for business analysts, emphasizing its role in understanding the enterprise from a holistic perspective 1 2 .

The approach in which solution components are assembled, constructed, or developed by experts as a direct response to a set of requirements is referred to as “Create.” This involves the business analysts assessing the merits of the solution approaches for each design option, which includes creating solution components that are tailored to meet the specific requirements. This option also encompasses modifying an existing solution to better fit the requirements.

In the context of business analysis, interviews are a fundamental elicitation technique used to gather detailed information. There are two basic types of interviews: structured and unstructured. A structured interview is one where the interviewer comes prepared with a specific set of questions that are asked in a systematic manner. This approach ensures consistency and comparability of responses. On the other hand, an unstructured interview is more flexible, allowing the conversation to flow more naturally based on the interviewee’s responses.  This can lead to the discovery of information that might not have been uncovered through a structured approach.  References : The information aligns with the guidelines provided by the International Institute of Business Analysis (IIBA) and is verified according to their standards for elicitation techniques 1 2 .

The correct answer is B . BABOK’s Trace Requirements task and related task card identify Scope Modelling as a technique used to visually depict scope and trace requirements to the area of scope the requirement supports . Since the problem in the scenario is misalignment, using scope modelling helps ensure requirements and designs are connected to the correct scope areas and remain aligned with what the initiative is intended to achieve.

Option A is incorrect because prototyping can help stakeholders visualize a solution, but it does not itself provide the strongest tracing mechanism for maintaining alignment between requirements, designs, and scope.

Option C is incorrect because SWOT analysis is used to assess strengths, weaknesses, opportunities, and threats. It is not a tracing technique, and the phrasing about duplicating a competitor’s threat is not BABOK-aligned.

Option D is incorrect because observation can help understand user work or behavior, but it is not the best technique for tracing requirements and designs to avoid strategic or scope misalignment.

 Stakeholder analysis is a technique used by business analysts to understand the attitudes and influence of various stakeholders. This involves identifying stakeholders, assessing their interests, influence, and the impact they can have on the project. Understanding stakeholders’ attitudes and influence helps in managing their expectations, securing their support, and mitigating potential risks associated with stakeholder engagement.

Re-evaluating the allocation of design elements between components can be appropriate at any time during the evaluation process. This ongoing evaluation allows for flexibility and ensures that any changes in requirements or constraints can be accommodated. Continuous re-evaluation helps in optimizing the design to meet the evolving needs of the project and ensures that the final solution is robust and adaptable to any changes or discoveries made during the evaluation phase.

The correct answer is D . BABOK guidance on Assess Risks states that one valid decision is to not pursue the benefits of a change when the risks are too great. In other words, the “Do Nothing” option is most appropriate when the risk of making the change outweighs the expected value or benefits .

Option A is incorrect because a long timeframe or lower priority may affect scheduling, but it does not by itself justify recommending no change at all. The “Do Nothing” option is a value-and-risk decision, not merely a timing decision.

Option B is incorrect because having more resources than necessary does not logically support doing nothing. Resource availability may influence how a change is implemented, but it is not the BABOK reason for selecting the no-change option.

Option C is the opposite of the correct reasoning. If effort is low and value is high, that would generally support making the change rather than doing nothing. From a business analysis perspective, action is more justifiable when expected value is favorable relative to cost and risk

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 )

Good collaboration with stakeholders is characterized by regular, frequent, and bi-directional communication with all stakeholders involved in the initiative. This ensures that all voices are heard, and that information, ideas, and innovations are freely exchanged, contributing to a more inclusive and comprehensive understanding of the project requirements and objectives.

When the focus of specifying and modeling is on how a solution will meet requirements , the output is referred to as a design . According to the BABOK® Guide v3, design is the usable representation of a solution. It describes the solution components and how they interact to fulfill business needs. This is distinct from requirements, which describe the " what " rather than the " how. "

Requirements = What the solution must do

Design = How the solution will do it

BABOK® Reference:

Requirements Analysis and Design Definition knowledge area explains that specifying and modeling can result in either requirements or designs depending on the focus of the activity.

The measure of significance in reporting business analysis performance refers to how well the value delivered by the BA work products justifies the effort and resources invested . It focuses on whether the deliverables contributed meaningful value to the organization and whether they supported decision-making, change enablement, or strategic goals.

BABOK® Reference – Task: Assess Business Analysis Performance (Section 3.5):

“Significance assesses the value delivered by the business analysis work and whether it justifies the resources expended.”

The requirements life cycle continues beyond implementation and ends when the solution and the requirements that define it are retired . This marks the conclusion of the requirements ' relevance to the organization and their formal removal from active use.

Exact Extract from BABOK® Guide v3 – Section 5: Requirements Life Cycle Management Overview:

“The requirements life cycle ends when a solution component that a requirement traces to is retired.”

The concept of opportunity cost is fundamental in economics and decision-making processes, which also applies to business analysis. Opportunity cost refers to the benefits that are foregone by choosing one alternative over another. In the context of business analysis, when resources are allocated to one design option, the opportunity cost is the value of the best alternative that is not chosen. This means that the opportunity cost is the cost of the next best alternative that could have been achieved with those resources.

A Center of Excellence (CoE) offers standardized practices, tools, techniques, and procedures to enhance the quality and consistency of business analysis efforts across the organization. When a BA uses a CoE, they are typically drawing on pre-established methodologies and best practices to guide their work.

Functions of a CoE:

Maintain organizational BA standards

Provide reusable templates and models

Offer training and professional development

BABOK® Reference:

Covered in the Business Analysis Planning and Monitoring knowledge area, CoEs are identified as a resource for determining appropriate techniques and procedural guidance.

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 .

Business Analysts (BAs) commonly use a checklist during requirements verification to ensure that all requirements are consistent, complete, coherent, and testable. This checklist typically includes a standard set of quality elements that the requirements must adhere to. The use of a checklist helps BAs to systematically verify each requirement against these quality criteria.  References : The BABOK Guide lists 8 characteristics of requirements quality: cohesive, complete, consistent, correct, feasible, modifiable, unambiguous, and testable.  These characteristics form the basis of the standard quality elements included in a verification checklist 1 .

In the Elicitation and Collaboration knowledge area, the task " Prepare for Elicitation " takes " needs " and " stakeholder engagement approach " as key inputs. The purpose of this task is to understand the scope, identify stakeholders, choose elicitation techniques, and prepare the logistics to ensure a productive elicitation session.

Needs define the business problem or opportunity prompting the elicitation.

Stakeholder engagement approach outlines how stakeholders will be involved, influencing techniques and planning.

BABOK® Guide v3 – Section 4.1: Prepare for Elicitation:

Inputs: " Needs " and " Stakeholder Engagement Approach "

“The purpose of Prepare for Elicitation is to understand the scope of the elicitation activity, select appropriate techniques, and plan for the elicitation.”

 In the context of Business Analysis, requirements should be initially prioritized based on the business benefits they are expected to deliver. This approach aligns with the principle of delivering the most value to the organization and ensuring that the most impactful requirements are addressed first. Prioritizing by business benefits helps in focusing on what is most important for achieving business objectives and delivering value to stakeholders.

 In the context of collaborative games used in business analysis, the opening step is where participants are informed about the problem and the rules of the game. It is during this initial phase that they start generating ideas.  This step is crucial as it sets the stage for the exploration and iteration steps that follow, where ideas are further developed and refined.  References : The information is verified as per the Business Analysis Learning documents, which outline that during the opening step of a collaborative game,

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 selecting elicitation techniques, a business analyst should consider techniques that are commonly used in similar initiatives , as these techniques are proven to work in comparable contexts. According to BABOK® Guide v3, the appropriateness of a technique depends on the situation, stakeholders, and the type of information needed. Techniques that have been successful in similar initiatives are likely to produce reliable and familiar results, reduce stakeholder resistance, and improve efficiency.

Exact Extract from BABOK® Guide v3 – Section 4.2: Conduct Elicitation:

“The business analyst considers the characteristics of the source, the type of information to be elicited, the techniques commonly used in similar initiatives, and the time and resource constraints when selecting elicitation techniques.”

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.

 Changes to requirements can occur at any point during the project lifecycle. This is because projects are dynamic, and various factors such as evolving stakeholder needs, market trends, technological advancements, or regulatory changes can necessitate modifications to the requirements. Business Analysts must be prepared to handle these changes effectively, ensuring that the project remains aligned with its objectives while accommodating necessary adjustments.

Video conferencing, electronic calendars, and electronic voting are all tools that facilitate collaboration among team members by allowing them to communicate and make decisions together, regardless of their physical location. These tools support the sharing of information and resources, coordination of activities, and collective decision-making, which are essential aspects of collaboration in business analysis.

Requirements that are good candidates for reuse are those that are not tied to a specific tool, technology, or system. These requirements are generally applicable across various contexts and can be used in multiple projects without significant changes. They are typically high-level business requirements that describe what the business needs without prescribing how to achieve it. This makes them flexible and adaptable to different situations, which is essential for reuse.

The correct answer is D . IIBA’s Business Analysis Standard states that business analysis is a human-centred, creative process aimed at achieving desired outcomes and driving organizational change . Among the given options, choice D is the closest and best match to that definition.

Option A is incorrect because business analysis is not limited to creating a strategic plan. It supports strategy, delivery, and evaluation work more broadly, all aimed at achieving desired outcomes.

Option B is incorrect because the IIBA definition is human-centred , not organization-centred, and business analysis is not defined primarily as resource allocation.

Option C is incorrect because creating plans may be part of the work, but it is not the best description of business analysis according to IIBA. The focus is on enabling change and achieving desired outcomes.

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 .

The Active Observation Approach is used when a business analyst (BA) asks questions during the job shadowing with a subject matter expert. This approach involves the observer interacting with the person performing the task, allowing the BA to ask questions and gain immediate understanding of the process and reasoning behind actions taken during the activity. It is a method that enables the BA to quickly comprehend undocumented processes and the rationale behind the tasks being observed.

The correct answer is B . In the BACCM, Change is defined by IIBA as the act of transformation in response to a need . Therefore, exploring the Change concept helps the business analysis professional understand what must be transformed in order to address the identified need. ( IIBA )

Option A is incorrect because the problem or opportunity to be addressed corresponds to the BACCM concept of Need , not Change. ( IIBA )

Option C is incorrect because the specific way to satisfy one or more needs corresponds to Solution , not Change. ( IIBA )

Option D is incorrect because who is impacted by or who impacts the change corresponds to Stakeholder , not Change. ( IIBA )

To ensure high-quality relationships between requirements, the criteria are that they should be consistent (logically aligned without contradictions) and correct (accurately represent the intended relationships and dependencies).

Exact Extract from BABOK® Guide v3 – Section 5.1: Trace Requirements:

“Relationships between requirements should be clearly defined, consistent, and correct to support impact analysis and traceability.”

While assessing requirements changes, a business analyst (BA) determines the formality of the assessment process based on the governance approach. The governance approach provides the framework within which changes are evaluated and decisions are made regarding the approval or rejection of changes. This approach outlines the processes, roles, responsibilities, and standards that guide how changes are managed, ensuring that changes align with organizational policies and strategic objectives .

The information management approach outlines the methods by which business analysis information, including requirements and models, will be stored, maintained, and accessed for future use. This approach ensures that the valuable insights gained from business analysis are not lost and can be effectively reused in subsequent projects or processes, thereby saving time and resources.

In the context of business analysis, the input status of requirements for undertaking requirement verification activities is ‘Specified and Modeled’. This means that the requirements have been detailed and documented, and models have been created to represent them. This status is crucial for verification activities because it ensures that the requirements are clearly understood and can be systematically evaluated against quality standards to ensure they are usable for their intended purpose.

In use case diagrams , the relationships between use cases may include “include” and “extend.”

Include indicates that a use case incorporates another use case as part of its behavior.

Extend shows optional behavior that extends the base use case under certain conditions.

These relationships help modularize functionality and clarify dependencies.

BABOK® Reference – Technique: Use Cases and Scenarios (Section 10.49):

“Use cases can have relationships such as include or extend to indicate reuse or conditional behavior extensions.”

The correct answer is A . BABOK’s Prepare for Elicitation task identifies Risk Analysis and Management as a technique used to identify, assess, and manage conditions or situations that could disrupt elicitation or affect the quality of the information obtained. That makes it the best technique for addressing issues that may arise during the elicitation session.

Option B is incorrect because Data Mining is used to discover patterns and information from existing data, not primarily to prepare for or manage issues during a live elicitation session.

Option C is incorrect because brainstorming can help generate ideas, but it is not the BABOK technique most directly aimed at identifying and managing risks that may arise during elicitation.

Option D is incorrect because Estimation focuses on forecasting time, effort, and cost, not on proactively identifying and handling elicitation issues.

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.