TOGAF Business Architecture Part 1: OGB-001

Correct Answer: C

Explanation: This answer is based on the definition of the enables relationship in the ArchiMate 3.1 Specification 1, which states that "An enabling relationship describes how an element (e.g., a node, device, or system software) enables another element (e.g., a business process, service, or function) to function." In this case, the value stream stage enables the business capability to function, as it provides the necessary inputs, outputs, and resources for the capability to deliver value. The other options are not correct, as they do not describe the relationship between a value stream stage and a business capability.

Correct Answer: A

Explanation: This answer is based on the TOGAF Standard, Version 9.2 - Phase A: Architecture Vision 1, which states that "Business principles, business goals, and strategic drivers of the organization are already defined elsewhere in the enterprise. If so, the activity in Phase A is involved with ensuring that existing definitions are current, and clarifying any areas of ambiguity. Otherwise, it involves defining these essential items from scratch." Business principles, goals, and drivers provide context for the architecture work by describing the needs and ways of working of the enterprise. They define the desired outcomes, the guiding values, and the strategic direction of the enterprise. They also help to align the architecture work with the business strategy and objectives. The other options are not correct, as they do not provide context for the architecture work in Phase A.

Correct Answer: A

Explanation: This answer is based on the TOGAF Series Guide: Business Capabilities , which states that "A business capability model is a structured representation of the capabilities of an organization. It is typically structured using two concepts: categorizing and grouping." Categorizing is the process of assigning capabilities to different categories based on their nature, purpose, or function. Grouping is the process of arranging capabilities into different levels or layers based on their granularity, abstraction, or dependency. The other options are not correct, as they are not concepts used for structuring a business capability model.