매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
TOGAF Enterprise Architecture Combined Part 1 and Part 2 Exam 온라인 연습
최종 업데이트 시간: 2026년01월01일
당신은 온라인 연습 문제를 통해 The Open Group OGEA-103 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 OGEA-103 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 40개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
The scope of an architecture is the extent and level of detail of the architecture work. The scope of an architecture can be defined along four dimensions: project, breadth, depth, and architecture domains. The project dimension considers the boundaries and objectives of the architecture project, such as the time frame, budget, resources, and deliverables. The breadth dimension considers the coverage and completeness of the architecture across the enterprise, such as the organizational units, business functions, processes, and locations. The depth dimension considers the level of detail and specificity of the architecture, such as the granularity, abstraction, and precision of the architectural elements and relationships. The architecture domains dimension considers the aspects or segments of the architecture, such as the business, data, application, and technology domains.
Therefore, the depth dimension is the one that considers to what level of detail the architecting effort should go.
The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 25: Architecture Scope: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 25.2: Scope Dimensions: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 25.2.1: Project, Breadth, Depth, and Architecture Domains
정답:
Explanation:
Phase A: Architecture Vision is the first phase of the Architecture Development Method (ADM) cycle, which is the core of the TOGAF standard. The main purpose of this phase is to define the scope and approach of the architecture development, and to create the Architecture Vision, which is a high-level description of the desired outcomes and benefits of the proposed architecture. To achieve this purpose, this phase focuses on defining the problem to be solved, identifying the stakeholders, their concerns, and requirements, and establishing the business goals and drivers that motivate the architecture work. This phase also involves obtaining the approval and commitment of the sponsors and other key stakeholders, and initiating the Architecture Governance process.
The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 5: Introduction to the ADM: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18.3: Inputs: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18.4: Steps
정답:
Explanation:
The image shows a diagram that illustrates the basic concepts of architecture description as defined by the ISO/IEC/IEEE 42010:2011 standard1, which is also adopted by the TOGAF standard2.
According to the ISO/IEC/IEEE 42010:2011 standard, an architecture description is a work product used to express an architecture, and it consists of one or more architecture views1.
An architecture view is a representation of a system from the perspective of a related set of concerns, and it conforms to an architecture viewpoint1.
An architecture viewpoint is a specification of the conventions for constructing and using an architecture view to address specific stakeholder concerns1.
Therefore, the correct answer is option A, which identifies the items labeled as “A” and “B” in the image as an architecture viewpoint and an architecture view, respectively.
Reference:
1: ISO/IEC/IEEE 42010:2011 - Systems and software engineering ― Architecture description1
2: TOGAF Standard, Version 9.2 - Part IV: Architecture Content Framework - 31. Architectural Artifacts2
정답:
Explanation:
Architecture governance is the practice of ensuring compliance with the enterprise architecture and its principles, standards, and goals. Architecture governance provides the means to establish, monitor, and control the architecture development and implementation processes, and to resolve any issues or conflicts that may arise. Architecture governance also ensures that all stakeholders are represented and involved in the decision-making process, and that their interests and concerns are balanced and aligned. Statements 1 and 2 highlight the value and necessity for architecture governance to be adopted within organizations, as they emphasize the importance of responsibility, accountability, fairness, and transparency in the architectural activities. Statements 3 and 4 are more related to the benefits and outcomes of having a good enterprise architecture, rather than the governance aspect.
The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50:
Architecture Governance: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 29: Architecture Governance
정답:
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
Reference: 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
정답:
Explanation:
Building blocks are reusable components of business, IT, or architectural capability that can be combined to deliver architectures and solutions. Building blocks can be defined at various levels of detail, depending on the stage of architecture development. In the earlier phases of the ADM cycle (A to D), building blocks are defined in generic terms, such as logical or physical, to provide a high-level view of the architecture. In Phase E: Opportunities and Solutions, building blocks become implementation-specific, meaning that they are linked to specific products, standards, technologies, and vendors that are available in the market. This phase also identifies the delivery vehicles, such as projects, programs, or portfolios, that will realize the building blocks12
Reference:
1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 23: Phase E: Opportunities and Solutions
2: The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 36: Building Blocks
정답:
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.
Reference: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 24: Applying Iteration to the ADM
정답:
Explanation:
The objectives listed in the question correspond to the objectives of different phases of the TOGAF ADM (Architecture Development Method), which is a method for developing and managing an enterprise architecture1.
The ADM consists of nine phases, each with a specific purpose and output.
The phases are1:
Preliminary Phase: To prepare and initiate the architecture development cycle, including defining the architecture framework, principles, and governance.
Phase A: Architecture Vision: To define the scope, vision, and stakeholders of the architecture initiative, and to obtain approval to proceed.
Phase B: Business Architecture: To describe the baseline and target business architecture, and to identify the gaps between them.
Phase C: Information Systems Architectures: To describe the baseline and target data and application architectures, and to identify the gaps between them.
Phase D: Technology Architecture: To describe the baseline and target technology architecture, and to identify the gaps between them.
Phase E: Opportunities and Solutions: To identify and evaluate the opportunities and solutions for implementing the target architecture, and to define the work packages and transition architectures.
Phase F: Migration Planning: To finalize the implementation and migration plan, and to ensure alignment with the enterprise portfolio and project management.
Phase G: Implementation Governance: To provide architecture oversight and guidance for the implementation projects, and to manage any architecture change requests.
Phase H: Architecture Change Management: To monitor the changes in the business and technology environment, and to assess the impact and performance of the architecture.
Based on the above definitions, we can match each objective with the corresponding phase as follows:
Objective 1: Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision. This objective is achieved in Phase C: Information Systems Architectures, where the data architecture is defined as a subset of the information systems architecture2.
Objective 2: Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals. This objective is achieved in Phase B: Business Architecture, where the business architecture is defined as a subset of the enterprise architecture3.
Objective 3: Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture. This objective is achieved in Phase A: Architecture Vision, where the architecture vision is defined as a high-level description of the target architecture and its benefits4.
Objective 4: Develop the Target Application Architecture that enables the Business Architecture and the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns. This objective is achieved in Phase C: Information Systems Architectures, where the application architecture is defined as a subset of the information systems architecture2.
1: The TOGAF Standard, Version 9.2, Chapter 5: Architecture Development Method (ADM)
2: The TOGAF Standard, Version 9.2, Chapter 9: Phase C: Information Systems Architectures
3: The TOGAF Standard, Version 9.2, Chapter 8: Phase B: Business Architecture
4: The TOGAF Standard, Version 9.2, Chapter 7: Phase A: Architecture Vision
정답:
Explanation:
The Implementation Governance Model is a framework that defines the roles, responsibilities, processes, and standards for governing the implementation of the target architecture. It ensures that a project transitioning into implementation also smoothly transitions into appropriate Architecture Governance, which is the practice of ensuring compliance with the enterprise architecture and its principles, standards, and goals. The Implementation Governance Model is part of the Implementation and Migration Plan, which is the output of Phase F: Migration Planning of the Architecture Development Method (ADM)12
Reference: 1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 21: Phase F: Migration Planning 2: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50: Architecture Governance
정답:
Explanation:
The Architecture Landscape is a class of information within the Architecture Repository that shows an architectural view of the building blocks that are in use within the organization today (the Baseline Architecture), as well as those that are planned for the future (the Target Architecture). The Architecture Landscape typically contains a list of the applications in use within the enterprise, along with their relationships and dependencies, as well as other relevant architectural information. The Architecture Landscape helps to identify opportunities for re-use, consolidation, or retirement of existing applications, as well as gaps or overlaps in the current or future architecture.
The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 34: Architecture
Landscape: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter
47: Architecture Repository
정답:
Explanation:
Architecture Principles are general rules and guidelines that inform and support the way in which an organization sets about fulfilling its mission. They reflect a level of consensus among the various elements of the enterprise, and form the basis for making future IT decisions. One of the purposes of Architecture Principles is to establish a common understanding of how to control the business in pursuit of strategic objectives, by providing a framework for evaluating and agreeing on the changes that affect the enterprise’s architecture3
Reference: 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 23: Architecture Principles: The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 31: Architecture Principles
정답:
Explanation:
The Business Transformation Readiness Assessment technique is used to evaluate the readiness of the organization to undergo change and to identify the actions needed to increase the likelihood of a successful business transformation. These actions should be incorporated in the Implementation and Migration Plan, which is the detailed plan to transition from the Baseline Architecture to the Target Architecture. The Implementation and Migration Plan also includes the Transition Architectures, the Architecture Building Blocks, the Work Packages, the Implementation Governance Model, and the Architecture Contract12
Reference: 1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 27:
Business Transformation Readiness Assessment
2: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 21: Phase F: Migration Planning
정답:
Explanation:
An EA Capability is the ability of an organization to perform enterprise architecture effectively and efficiently. It involves establishing and maintaining the appropriate organization structures, roles, responsibilities, skills, processes, tools, and governance mechanisms to support the development and use of enterprise architecture. An EA Capability enables the organization to align its business and IT strategies, deliver value from its investments, manage change and complexity, and improve its performance and agility12
Reference: 1: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 44: Introduction
2: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 45: Establishing and Maintaining an Enterprise Architecture Capability
정답:
Explanation:
The chart shown is a Gantt chart, which is commonly used for project management to illustrate a project schedule. In the context of TOGAF (The Open Group Architecture Framework), which is a framework for enterprise architecture, this Gantt chart is demonstrating the sequenced approach to the Architecture Development Method (ADM). The ADM is the core process of TOGAF which provides a tested and repeatable process for developing architectures. The ADM is described as being iterative, over the whole process, between phases, and within phases. For each iteration of the ADM, a fresh decision must be taken about each of the parameters (scope, granularity, time period, and architecture assets).
The ADM consists of a number of phases that have to be followed in sequence:
Preliminary Phase: Framework and principles
Phase A: Architecture Vision
Phase B: Business Architecture
Phase C: Information Systems Architectures, including Data and Application Architectures
Phase D: Technology Architecture
Phase E: Opportunities and Solutions
Phase F: Migration Planning
Phase G: Implementation Governance
Phase H: Architecture Change Management
Requirements Management
Each phase is dependent on the outputs of the previous phase and the Requirements Management phase runs throughout. The Gantt chart clearly shows the dependency and sequence in which these phases occur, implying that a structured approach is followed to produce the enterprise architecture.
The TOGAF Standard, Version 9.2, a standard of The Open Group
The TOGAF documentation available at https://publications.opengroup.org/standards/architecture and https://publications.opengroup.org/guides/architecture
정답:
Explanation:
The purpose of the Gap Analysis technique is similar to the previous question, but with a focus on the Target Architecture. The technique helps to identify the items that are not included or specified in the Target Architecture, such as capabilities, services, components, standards, or technologies. These items may be essential for achieving the vision and goals of the enterprise, or for addressing the stakeholder concerns and requirements. By identifying the items omitted from the Target Architecture, the technique helps to ensure that the architecture is comprehensive, feasible, and realistic.