매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
TOGAF Enterprise Architecture Bridge Exam (English) 온라인 연습
최종 업데이트 시간: 2024년05월09일,104문제.
당신은 온라인 연습 문제를 통해 The Open Group OGEA-10B 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 OGEA-10B 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 104개의 시험 문제와 답을 포함하십시오.
정답:
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
References: 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 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.
정답:
Explanation:
The Enterprise Continuum provides methods for classifying architecture artifacts as they evolve from generic architectures to Organization-Specific Architectures. Generic architectures are architectures that have been developed for use across a wide range of enterprises with similar characteristics. They provide common models, functions, and services that can be reused and adapted for specific purposes. Organization-Specific Architectures are architectures that have been tailored to meet the needs and requirements of a particular enterprise or a major organizational unit within an enterprise. They reflect the unique vision, goals, culture, structure, processes, systems, and technologies of that enterprise or unit.
Reference: The TOGAF® Standard | The Open Group Website, Section 2.3 Enterprise Continuum.
정답:
Explanation:
The Implications section describes the impact of adhering to the principle on the organization, the processes, the information systems, and the technology23. It also identifies the changes, costs, and risks that may result from applying the principle23. The Implications section helps to communicate the benefits and consequences of the principle to the stakeholders and to guide the implementation and governance of the architecture23.
The other sections of the TOGAF template for Architecture Principles are1:
• Name: This section provides a short and memorable name for the principle that represents its essence and purpose23. The name should not mention any specific technology or solution23.
• Statement: This section provides a concise and formal definition of the principle that expresses the fundamental rule or constraint that the principle imposes23. The statement should be clear, unambiguous, and testable23.
• Rationale: This section provides the reasoning and justification for the principle, explaining why it is important and how it supports the business goals and drivers23. The rationale should also link the principle to the higher-level enterprise or IT principles that it elaborates on23.
References: 2: The TOGAF Standard, Version 9.2 - Architecture Principles 3: TOGAF 8.1.1 Online - Architecture Principles 1: Architecture Principles Template
정답:
Explanation:
The objective of the ADM Implementation Governance Phase is to provide an architectural oversight of the implementation and to ensure conformance for the target architecture. This phase involves establishing procedures and processes to monitor and control the implementation projects and to verify that they comply with the defined architecture.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.2.7 Phase G: Implementation Governance.
정답:
Explanation:
According to the TOGAF Standard, Version 9.2, an architecture view is a representation of a system from the perspective of a related set of concerns1. It consists of one or more architecture models that demonstrate how the system addresses the stakeholder concerns1.
An architecture viewpoint is a specification of the conventions for constructing and using an architecture view to address specific stakeholder concerns1. It defines the perspective, scope, notation, and techniques for creating an architecture view of a system1.
Architects can present architecture views and viewpoints to stakeholders to extract hidden agendas, principles, and requirements that could impact the final Target Architecture, because23:
Architecture views and viewpoints help to communicate and visualize the architecture in a way that is meaningful and relevant to different stakeholders, addressing their specific interests and needs.
Architecture views and viewpoints help to elicit and validate the stakeholder concerns and requirements, ensuring that they are aligned with the business goals and objectives, and that they are consistent and feasible within the architecture context.
Architecture views and viewpoints help to identify and resolve any conflicts, gaps, or trade-offs among the stakeholder concerns and requirements, ensuring that they are balanced and prioritized in the architecture design and decision-making.
Architecture views and viewpoints help to demonstrate and verify the value and benefits of the architecture to the stakeholders, ensuring that they are satisfied and committed to the architecture outcome and governance.
References:
1: The TOGAF Standard, Version 9.2, Chapter 22: Architecture Views, Viewpoints, and Stakeholders
2: The TOGAF Standard, Version 9.2, Chapter 4: Introduction to Part II, Section 4.2: What is an Architecture Framework?
3: The TOGAF Standard, Version 9.2, Chapter 31: Architectural Artifacts, Section 31.1: Basic Concepts
정답:
Explanation:
The purpose of Enterprise Architecture is to guide effective change by providing a coherent and consistent view of the enterprise’s current and future state, as well as the roadmap and principles for achieving it. Enterprise Architecture helps to align business and IT strategies, optimize resources and investments, reduce complexity and risks, enhance agility and innovation, and deliver value to stakeholders.
Reference: The TOGAF® Standard | The Open Group Website, Section 1.3 Executive Overview.
정답:
Explanation:
According to the TOGAF standard, the objectives of each ADM phase are as follows1:
• Phase E: Opportunities and Solutions
- Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value
- Identify and group major work packages within the Architecture Roadmap
- Identify and group major implementation projects to realize the Architecture Roadmap oIdentify dependencies between increments and projects
- Estimate cost, benefit, and risk at a high level for each increment and project oConduct initial prioritization and sequencing of the Architecture Roadmap and projects • Phase F: Migration Planning
- Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D
- Confirm the Transition Architectures with relevant stakeholders
- Create the Implementation and Migration Plan, including Transition Architectures, work packages, projects, and other activities
- Confirm and agree the Architecture Roadmap and Implementation and Migration Plan with relevant stakeholders
• Phase G: Implementation Governance
- Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan oEnsure conformance with the Target Architecture by implementation projects
- Perform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests
- Ensure that the architecture lifecycle is maintained
- Ensure that the Architecture Governance Framework is executed • Phase H: Architecture Change Management
- Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders
- Manage risks and issues related to the Architecture Roadmap and Implementation and Migration Plan - Monitor the implementation projects and Transition Architectures
- Manage changes to the architecture baseline
- Manage changes to the Architecture Capability
Therefore, the correct matching of the objectives and the phases is:
• 1G: Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value
• 2E: Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D
• 3F: Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan
• 4F: Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders
References: 1: The TOGAF Architecture Development Method
정답:
Explanation:
The statement illustrates iteration and the ADM. Iteration is the technique of repeating a process or a phase with the aim of improving or refining the outcome. Iteration allows for feedback loops and adaptations at any point in the architecture development and transition process. Separate projects may operate their own ADM cycles concurrently, with relationships between the different projects, to address different aspects or levels of the architecture in an iterative manner.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.1 Introduction to the ADM.
정답:
Explanation:
These domains provide a consistent way to describe and understand the architecture from different perspectives, such as business, information, and technology12. Each domain has its own set of concepts, models, views, and artifacts that define the structure and behavior of the architecture within that domain12.
The other options are incorrect because:
• Logical and Physical are not architecture domains, but rather levels of abstraction that can be applied to any domain. Logical architecture describes the functionality and behavior of the system, while physical architecture describes the implementation and deployment of the system3.
• Information and Data are not distinct architecture domains, but rather aspects of the same domain. Information architecture describes the meaning and context of the data, while data architecture describes the structure and format of the data4.
• Capability and Segment are not architecture domains, but rather levels of granularity that can be applied to any domain. Capability architecture describes the current and desired states of a specific business capability, while segment architecture describes a subdivision of the enterprise that has a clear business focus5.
References:
1: The TOGAF Standard, Version 9.2 - Definitions 2: TOGAF® Standard ― Introduction - Definitions 3: [Logical vs Physical Architecture] 4: [Information Architecture vs Data Architecture] 5: [The TOGAF Standard, Version 9.2 - Applying the ADM Across the Architecture Landscape]
정답:
Explanation:
An Architecture Contract is a deliverable that specifies the responsibilities and obligations of the parties involved in the implementation and governance of an architecture. It ensures a system of continuous monitoring to check integrity changes decision-making and audit of all architecture-related activities.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.4 Architecture Contracts.
정답:
Explanation:
Statements 1 and 3 about architecture partitioning are correct. Architecture partitioning is the technique of dividing an architecture into smaller and more manageable parts that can be developed, maintained, and governed independently. Partitions are used to simplify the management of the Enterprise Architecture and to enable different teams to work on different elements of the architecture at the same time. Partitions are not equivalent to architecture levels, which are different degrees of abstraction or detail in an architecture. Partitions do not necessarily reflect the organization’s structure, which may change over time or differ from the architecture’s scope and boundaries.
Reference: The TOGAF® Standard | The Open Group Website, Section 2.5 Architecture Partitioning.
정답:
Explanation:
A set of architecture principles that cover every situation perceived meets the recommended criteria of completeness. Completeness is one of the six criteria that should be applied when developing or assessing architecture principles. Completeness means that there are no gaps or overlaps in the coverage of principles across all relevant aspects of the enterprise’s architecture.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.7 Architecture Principles.
정답:
Explanation:
When considering agile development, Architecture to Support Portfolio will identify the necessary products for the enterprise, define their boundaries, and outline the constraints for a product owner. This process directly relates to defining the enterprise's backlog, which in agile methodologies, is a prioritized list of work for the development team that is derived from the roadmap and its requirements.
정답:
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.
References:
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