Free IIBA ECBA Practice Exam with Questions & Answers | Set: 3

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 task that uses the " Elicitation Activity Plan " to draw out, explore, and identify information relevant to the change is " Conduct Elicitation. " This task involves direct interaction with stakeholders or independent research to understand stakeholder needs and identify potential solutions that may meet those needs. The Elicitation Activity Plan guides the business analyst through the planned elicitation activities, ensuring that the elicitation is focused, efficient, and aligned with the project objectives. This structured approach to elicitation helps in gathering relevant and accurate information, which is essential for the success of the change initiative .

A predictive planning approach (also known as waterfall or plan-driven) emphasizes upfront planning, thorough documentation, and clearly defined stages of work. One of its key characteristics is that information is captured in standardized templates, ensuring consistency, traceability, and formal approvals at each stage.

Other characteristics include:

Sequential task execution

Emphasis on documentation and traceability

Clear role definitions and responsibilities

Reduced flexibility to accommodate change mid-project

This is different from adaptive or Agile approaches, which rely on iterations, minimal documentation, and continuous stakeholder feedback.

BABOK® Reference:

Detailed in the Business Analysis Planning and Monitoring knowledge area under “Approaches and Techniques,” where predictive approaches are contrasted with adaptive approaches based on their structure, documentation, and flexibility.

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.

The BABOK® Guide outlines that during the verification process, requirements should be evaluated against established criteria to ensure they are complete, consistent, feasible, and testable1. Additionally, the guide emphasizes the importance of having specified and modeled requirements as a starting point for verification activities2.

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

The correct answer is A. “Think as a Customer” requires the business analysis professional to understand customer needs, expectations, pain points, desired outcomes, and value perception before jumping into system design. In the early stages, the analyst should begin with broad customer needs and then progressively decompose them into features or requirements that can deliver value. Option B is too competitor-focused and may miss actual customer needs. Option C is technology-focused and premature unless technical constraints are the main issue. Option D moves too quickly into detailed system requirements and solution scope. Customer-focused analysis starts with the customer problem and desired experience, then translates that understanding into actionable solution features.

===============

 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.

The role and benefits of a logical data model in business analysis are discussed in resources like “What is a Logical Data Model? Definition and Examples” and “The logical data model explained” which detail how logical data models serve as blueprints for structuring enterprise knowledge and ensuring data integrity12.

The correct answer is C. BABOK describes Lessons Learned as a technique used to identify changes to business analysis processes and deliverables, as well as successes that can be incorporated into future work. The purpose is to use experience from what happened before to improve current practice and influence future initiatives.

Option A is incorrect because getting consultant feedback may happen in some situations, but it is not the purpose of the lessons learned technique in BABOK. The focus is organizational learning and improvement.

Option B is incorrect because lessons learned are not meant to be kept confidential within only the BA team. Their value comes from sharing relevant insights so processes and outcomes can improve more broadly.

Option D is incorrect because lessons learned are meant to support improvement, not delay documentation unnecessarily. In many environments, especially iterative ones, learning is captured and applied continuously rather than postponed until the very end.

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.

The BABOK® Guide emphasizes the importance of securing supporting materials as part of the preparation for elicitation. This step ensures that the business analyst has all the necessary tools and information to effectively conduct elicitation activities1.