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 foundation for guiding the elicitation effort in business analysis is supporting material. According to the BABOK Guide v3, before initiating elicitation activities, a business analyst must review and gather relevant background information, which includes existing documentation, enterprise environmental factors, and business rules. This supporting material provides the necessary context and guidance to determine what information needs to be elicited and from whom.
Supporting material includes:
Existing system documents
Business processes and models
Organizational policies and procedures
Historical data from previous initiatives
Stakeholder and user manuals
The use of supporting material ensures that the elicitation is purposeful, well-directed, and focused on identifying information gaps and opportunities for refinement.
BABOK Reference:
This is covered under the Elicitation and Collaboration knowledge area, particularly in the task "Prepare for Elicitation," which lists supporting materials as a key input to the planning of elicitation activities.

The correct answer is B. A scope model is used to define the boundaries of an initiative, solution, or change. It clarifies what is included, what is excluded, and how stakeholders should understand the limits of the work.
This is important because unclear boundaries create scope creep, conflicting expectations, and unmanaged assumptions. Option A is incorrect because technical specifications describe how a solution may be built, not the overall scope boundary. Option C is incorrect because risks and issues are handled through risk analysis, issue management, or related planning activities. Option D is incorrect because roles and responsibilities are better addressed through stakeholder analysis, organizational modelling, or a RACI matrix, not a scope model.

Validate requirements ensures that a set of requirements or designs delivers business value and supports the organization's goals and objectives.

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.