OGBA-101 Practice Exam Questions with Answers TOGAF Business Architecture Foundation Exam Certification

A TOGAF business scenario is a technique that can be used to fully understand the requirements of information technology and align it with business needs1. It is not a business case, which is a document that provides justification for a proposed project or initiative6. It is not a method to develop a business model, which is a description of how an organization creates, delivers, and captures value for its stakeholders7. It is not a use-case, which is a description of how a system interacts with external actors to achieve a specific goal.

A TOGAF business scenario is a technique that helps to derive architecture requirements by describing a business process, application, or set of activities. It includes detailing the actors, roles, goals, business policies, business processes, and the environment in which the scenario takes place. Business scenarios are used within TOGAF to ensure that the architecture has a clear link to the business requirements.

The diagram shows the Enterprise Continuum, which is a view of the Architecture Repository that provides methods for classifying architecture and solution artifacts as they evolve from generic Foundation Architectures to Organization-Specific Architectures4. The Enterprise Continuum comprises two complementary concepts: the Architecture Continuum and the Solutions Continuum. The Architecture Continuum shows the relationships among foundationalframeworks, common system architectures, industry architectures, and enterprise architectures4. The Solutions Continuum shows the relationships among foundational solutions, common system solutions, industry solutions, and enterprise solutions4.

According to the TOGAF Standard, an enterprise is defined as any collection of organizations that has a common set of goals and/or a single bottom line1. The examples given in the question are all types of enterprises that can be the subject of enterprise architecture1.

In the context of TOGAF, the term 'enterprise' encompasses more than just a single organization. It refers to any collection of organizations that has a common set of goals. This can include, as described in the statements provided, entire corporations or their divisions, government agencies or departments, as well as business partnerships such as consortia or supply chains. TOGAF uses the term 'enterprise' to define the full scope of the entity that is the subject of planning, design, implementation, and operation of an Enterprise Architecture.

According to the TOGAF Standard, business scenarios are an important technique that may be used at various stages of the enterprise architecture, principally the Architecture Vision and theBusiness Architecture, but in other architecture domains as well, if required, to derive the characteristics of the architecture directly from the high-level requirements of the business1. The Architecture Vision is developed in Phase A, and the Business Architecture is developed in Phase B. The Preliminary Phase is also a stage where business scenarios can be used to help identify and understand business needs2.

Business scenarios are a tool used within TOGAF to help identify and understand the business requirements and to drive the creation of the enterprise's architecture. They are used in the Preliminary Phase to understand the organizational context, Phase A to develop the Architecture Vision, and Phase B to derive the Business Architecture based on the stakeholder's requirements and the business strategy.

A business model is a high-level conceptual representation that explains how an organization creates, delivers, and captures value. This encompasses the organization’s core logic for creating value, and may include its intended customer segments, the value propositions it offers, the channels through which it reaches customers, customer relationships it establishes, key activities, resources, and partnerships, as well as the revenue streams and cost structures. Thus, it is a visual and strategic representation of how a business operates and competes in the marketplace.

In the context of value stream stages, a gating stage is the element that describes the specific state change which triggers the next stage of the value stream to begin. It acts as a checkpoint that ensures that certain criteria are met before the process can proceed to the next phase.

The diagram of an architecture development cycle shows three phases of the TOGAF ADM. The correct phase names corresponding to the labels 1, 2 and 3 are Requirements Management, Implementation Governance, and Preliminary respectively3. These phases are described as follows:

• Requirements Management (label 1): This phase provides a process for managing architecture requirements throughout the ADM cycle3. It ensures that requirements are captured, stored, prioritized, and addressed by relevant ADM phases3. It also ensures that requirements are validated and updated as necessary3.
• Implementation Governance (label 2): This phase provides a process for ensuring that the implementation projects conform to the defined architecture3. It involves establishing an implementation governance model, defining architecture contracts and compliance reviews, and monitoring and supporting the implementation projects3.
• Preliminary (label 3): This phase provides a process for preparing and planning the architecture project3. It involves defining the scope and vision of the project, customizing the ADM process and content framework, defining principles and governance structures, and evaluating the enterprise architecture maturity and readiness3.

In the context of TOGAF's business scenarios, business capabilities and value streams are typically modeled during the phase of identifying and documenting the desired outcomes. This is because desired outcomes are directly related to what the business intends to achieve, and therefore, it makes sense to model the capabilities (what the business can do) and the value streams (the series of steps the business undertakes to create value) at this stage. This helps in understanding the required changes or enhancements to business capabilities and processes to achieve those outcomes.

One of the purposes of mapping capabilities to value stream stages is to classify, group, and align capabilities into categories for a deeper understanding of how they support value creation and delivery2. By mapping capabilities to value stream stages, the architect can identify which capabilities are required for each stage of the value stream, how they relate to each other, and how they contribute to the overall value proposition. This can help to assess the maturity, effectiveness, performance, and value or cost contribution of each capability.

The provided representation of a business model appears to be a variant of the Business Model Canvas, which is a strategic management template for developing new or documenting existing business models. It is a visual chart with elements describing a firm's value proposition, infrastructure, customers, and finances. The model assists firms in aligning their activities by illustrating potential trade-offs. Since none of the options precisely match the Business Model Canvas and the Four Box Framework is conceptually closest to the Business Model Canvas, option B is the best available answer, albeit not a perfect match.

In the provided diagram, item A refers to the Architecture Repository, which is a part of the TOGAF framework where all the architecture assets are stored. This includes the architectural models, patterns, architecture descriptions, and other artifacts relevant to the architecture. Item B is labeled as the Governing Board, which is likely referring to the Architecture Board or a similar governance structure responsible for oversight and decision-making regarding the enterprise architecture. Item C refers to Enterprise Capability, which encompasses the processes, tools, skills, and other capabilities that enable the architecture function within the enterprise.

When developing the Architecture Vision, which is part of the TOGAF ADM Phase A, architects should examine the Architecture Principles and Business Goals. These components provide the foundational guidance and the strategic context for the architecture work. They ensure that the resulting architecture aligns with the overall direction and objectives of the enterprise.

The statement that best describes iteration and the ADM is that the ADM is iterative, over the whole process, between phases, and within phases4. Iteration is a key concept in managing the complexity of developing an Enterprise Architecture and managing its lifecycle4. The ADM supports several forms of iteration as follows:

• Iteration over the whole process: Projects will iterate through the entire ADM cycle, commencing with Phase A (Architecture Vision) and ending with Phase H (Architecture Change Management)4. Each cycle of the ADM will be bound by a Request for Architecture Work that defines the scope and objectives of the project4. The architecture output will populate or update the Architecture Landscape that describes the current and target states of the enterprise4.
• Iteration between phases: Projects may cycle between ADM phases in planned cycles covering multiple phases4. Typically, this is used to converge on a detailed Target Architecture when higher-level architecture does not exist to provide context and constraint4. For example, a project may iterate between Phase B (Business Architecture), Phase C (Information Systems Architectures), and Phase D (Technology Architecture) until a satisfactory solution is achieved4.
• Iteration within phases: Projects may return to previous activities within an ADM phase in order to circle back and update work products with new information4. Typically, this is used to manage the inter-relationship between different aspects of an architecture domain or viewpoint4. For example, a project may revisit Business Architecture models after developing Information Systems Architecture models to ensure alignment and consistency4.