ECBA Exam Dumps - Entry Certificate in Business Analysis (ECBA)

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

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.

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.

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.

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

When examining requirements relationships, " unambiguous " is a key quality criterion. It ensures that the nature of the relationship between two or more requirements is clearly understood and not open to multiple interpretations. This clarity is critical for supporting impact analysis, traceability, requirement decomposition, and requirement allocation.

Poorly defined or ambiguous relationships can result in incorrect assumptions about dependencies or sequencing, potentially leading to implementation errors.

Additional Criteria Related to Requirement Relationships (from BABOK® Guide v3, Section 5.1 – Trace Requirements):

Necessity: The relationship exists because one requirement depends on another.

Correctness: The relationship accurately represents the dependency.

Consistency: The relationship does not conflict with other requirement links.

Unambiguity: All stakeholders interpret the relationship in the same way.

The correct answer is C. IIBA’s Business Analysis Standard explains the “See the whole” principle as analyzing needs in the big picture context and creating desired outcomes by understanding the context, the solution, and the stakeholders. This means the business analysis professional should ensure the loyalty program fits the broader organizational environment and addresses the relevant business and stakeholder needs, not just isolated requirements.

Option A is related to constraints and scope, which can be important, but it is narrower than the “See the Whole” principle. The principle is broader and emphasizes viewing the initiative within the overall environment rather than only looking at limitations.

Option B reflects a customer-centered mindset, which is important, but it aligns more closely with the “Think as a customer” principle than with “See the whole.” The question specifically asks about understanding the full context and overall environment.

Option D is also too narrow because clarifying executive goals is only one part of the overall picture. “See the Whole” requires balancing context, stakeholder needs, and solution alignment across the organization.

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