OGEA-103 Online Practice Questions and Answers

Correct Answer: C

Explanation: The four dimensions used to scope an architecture are Breadth, Depth, Time Period, and Architecture Domains. Breadth refers to the extent of the enterprise covered by the architecture. Depth refers to the level of detail and

completeness of the architecture. Time Period refers to the planning horizon and the number of Transition Architectures required to achieve the Target Architecture. Architecture Domains refer to the four domains of Business, Data,

Application, and Technology that constitute an enterprise's architecture. Reference: The TOGAF Standard | The Open Group Website, Section 3.2.1 Phase A:

Architecture Vision.

Correct Answer: B

Explanation: When considering agile development, Architecture to Support Project will identify what products the enterprise needs, the boundary of the products, and what constraints a product owner has. This defines the enterprise's backlog. A backlog is a list of features or tasks that need to be done to deliver a product or service. It is prioritized by the product owner based on the value and urgency of each item. Reference: The TOGAF Standard | The Open Group Website, Section 3.3.5 Architecture to Support Project.

Correct Answer: C

Explanation: The Architecture Landscape is divided into levels known as Segment Strategic and Capability Architectures. These levels correspond to different scopes and purposes of architectures within an enterprise. Segment Architectures are architectures that address specific business units, functions, or processes within an enterprise. Strategic Architectures are architectures that provide a high-level view of the enterprise's vision, goals, and direction. Capability Architectures are architectures that address specific business capabilities or services that span multiple segments or domains. Reference: The TOGAF Standard | The Open Group Website, Section 2.4 Architecture Repository.

Correct Answer: B

Explanation: The statement "Projects may cycle between ADM phases, in planned cycles covering multiple phases" illustrates the concept of iteration, which is the process of repeating the ADM phases or steps within a phase to refine the architecture outputs and address the changing requirements and stakeholder concerns. Iteration can occur at different levels of granularity and scope, such as within a single phase, across multiple phases, or across the entire ADM cycle. Iteration can also be applied to different architecture domains, such as business, data, application, and technology. Iteration is a key feature of the ADM that enables the development of architectures that are fit for purpose, adaptable, and responsive to change. References: : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 24: Applying Iteration to the ADM

Correct Answer: B

Explanation: The Preliminary Phase is the preparatory phase of the Architecture Development Method (ADM) cycle, which sets the context and direction for the architecture work. One of the objectives of this phase is to select and implement tools to support the Architecture Capability, which is the ability of an organization to perform enterprise architecture effectively and efficiently. Tools can include software applications, methods, techniques, standards, and frameworks that assist the architecture development and governance processes. The selection and implementation of tools should be based on the requirements and constraints of the organization, and the alignment with the Architecture Principles and the Architecture Vision3 References: 3: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 6: Preliminary Phase : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 45: Establishing and Maintaining an Enterprise Architecture Capability : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 46: Tools for Architecture Development

Correct Answer: B

Explanation: Business scenarios are a technique for capturing, clarifying, and communicating the functional and non-functional requirements of a system. Business scenarios describe the business environment, the actors involved, the desired outcomes, and the processes or rules that govern the behavior of the system. Business scenarios are useful for ensuring that the architecture addresses the real needs and concerns of the stakeholders, and for validating and testing the architecture against expected situations. Business scenarios are developed in Phase A: Architecture Vision of the ADM cycle, and refined and updated throughout the other phases3 References: 3: The TOGAF Standard, Version 9.2, Part

III: ADM Guidelines and Techniques, Chapter 26: Business Scenarios : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision

Correct Answer: A

https://pubs.opengroup.org/togaf-standard/adm-practitioners/adm-practitioners_3.html

Correct Answer: A

The TOGAF standard divides Enterprise Architecture into four primary architecture domains: business, data, application, and technology. These domains represent different aspects of an enterprise and how they relate to each other. The business domain defines the business strategy, governance, organization, and key business processes. The data domain describes the structure of the logical and physical data assets and data management resources. The application domain provides a blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes. The technology domain describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services. Other domains, such as motivation, security, or governance, may span across these four primary domains. References: The TOGAF Standard, Version 9.2 - Core Concepts Domains - The Open Group TOGAF Standard -- Introduction - Definitions - The Open Group The TOGAF Standard, Version 9.2 - Definitions - The Open Group TOGAF and the history of enterprise architecture | Enable Architect

Correct Answer: D

Business Transformation readiness assessment is initiated in Phase E, Completed in Phase F and monitored in Phase G.

Understanding the readiness of the organization to accept change, identifying the issues, and then dealing with them in the Implementation and Migration Plans is key to successful architecture transformation in Phases E and F. This will be a joint effort between corporate (especially human resources) staff, lines of business, and IT planners.

Correct Answer: B

Explanation: A Stakeholder Map is a technique that can be used to identify and classify the stakeholders of the architecture work, and to document their key interests, requirements, and concerns. A stakeholder is any person, group, or organization that has a stake in the outcome of the architecture work, such as the sponsor, the client, the users, the suppliers, the regulators, or the competitors. A Stakeholder Map can help to understand the needs and expectations of the stakeholders, and to communicate and engage with them effectively1 The steps for creating a Stakeholder Map are: Identify the stakeholders of the architecture work, using various sources and methods, such as interviews, surveys, workshops, or existing documents. Classify the stakeholders according to their roles, responsibilities, and relationships, using various criteria and dimensions, such as power, influence, interest, attitude, or impact. Define the concerns and relevant views for each stakeholder group, using various techniques, such as business scenarios, use cases, or value propositions. A concern is a key interest or issue that is relevant to the stakeholder, such as a goal, a problem, a need, or a risk. A view is a representation of the system of interest from the perspective of one or more stakeholders and their concerns. Record the stakeholders and their concerns in a Stakeholder Map, which shows the mapping between the stakeholder groups, the concerns, and the views. The Stakeholder Map also shows the dependencies, assumptions, and issues related to each stakeholder and concern. Therefore, the best answer is B, because it recommends the approach that would enable the development of an architecture that addresses the concerns of the CIO and the partners, using the Stakeholder Map technique. The answer covers the following aspects: An analysis of the stakeholders is undertaken, which involves identifying, classifying, and defining the stakeholders and their concerns. The stakeholders and their concerns are documented in a Stakeholder Map, which provides a clear and comprehensive picture of the stakeholder landscape and their interests. The concerns and relevant views are recorded in the Architecture Vision document, which is the output of Phase A: Architecture Vision of the Architecture Development Method (ADM), which is the core process of the TOGAF standard that guides the development and management of the enterprise architecture. The Architecture Vision defines the scope and approach of the architecture work, and establishes the business goals and drivers that motivate the architecture work. The Architecture Vision also involves obtaining the approval and commitment of the sponsors and other key stakeholders, and initiating the Architecture Governance process2 The requirements include risk mitigation through regular assessments, which involves identifying, analyzing, and evaluating the risks that may affect the architecture, and determining the appropriate measures or actions to prevent, reduce, or mitigate the risks. Risk mitigation can also involve monitoring and reviewing the risk situation, and communicating and reporting the risk status and actions3 This approach also allows a supervised agile implementation of the continuous Machine Learning, which involves applying agile principles and practices to the architecture development and implementation, such as iterative and incremental delivery, frequent feedback, collaboration, and adaptation. A supervised agile implementation can help to ensure the quality, value, and alignment of the architecture, and to respond to the changing needs and expectations of the stakeholders. References: 1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 24: Stakeholder Management 2: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase

A: Architecture Vision 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 32: Risk Management : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 29: Applying Iteration to the ADM