無料OGEA-103試験ブレーン問題集認定ガイド問題と解答 [Q42-Q61]

無料OGEA-103試験ブレーン問題集認定ガイド問題と解答

OGEA-103認定概要最新のOGEA-103PDF問題集

オープングループOGEA-103試験は、TOGAFフレームワークとそのアプリケーションを深く理解する必要がある挑戦的な認証です。候補者は、フレームワークの概念、原則、および建築開発プロセスに関する知識を実証できる必要があります。また、この知識を実際のシナリオに適用し、効果的なエンタープライズアーキテクチャソリューションを開発および実装する能力を実証できる必要があります。

 

質問 # 42
What are the four architecture domains that the TOGAF standard deals with?

• A. Capability, Segment, Enterprise, Federated
• B. Business, Data, Application, Technology
• C. Baseline, Candidate, Transition, Target
• D. Application, Data, Information, Knowledge

正解：B

解説：
Explanation
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

質問 # 43
Complete the sentence The purpose of Enterprise Architecture is to_______________.

• A. guide effective change
• B. control the bigger changes
• C. take major improvement decisions
• D. govern the stakeholders

正解：A

解説：
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.

質問 # 44
Consider the illustration.

What are the items labelled A, B and C?

• A. A-Enterprise Continuum, B-Architecture Continuum, C-Solutions Continuum
• B. A-Enterprise Architecture, B-Architecture Building Blocks, C-Solutions Building Blocks
• C. A-Architecture Vision, B-Business Architecture, C-Information Systems Architecture
• D. A-Enterprise Strategic Architecture, B-Segment Architecture, C-Solutions Architecture

正解：A

解説：
The illustration shows the relationship between the Enterprise Continuum, the Architecture Continuum, and the Solutions Continuum, which are key concepts in the TOGAF framework. The Enterprise Continuum is a view of the Architecture Repository that shows how generic foundation architectures can be leveraged and specialized to support the requirements of an individual organization. The Architecture Continuum specifies a structured classification for architectural artifacts, such as models, patterns, and descriptions, that can be reused and adapted across different domains and levels of abstraction. The Solutions Continuum identifies implemented solutions that support various stages of business and IT capability evolution, such as common systems, industry solutions, and organization-specific solutions. The illustration also shows how the architecture context and requirements are influenced by external factors, such as business drivers, stakeholders, and standards, and how they shape the generic and specific architectures and solutions. The illustration also shows how the deployed solutions become part of the architecture context for future iterations of the architecture development cycle. References:
*TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 6: Architecture Repository, Section 6.2 Enterprise Continuum.
*TOGAF Standard, 10th Edition, Part IV: Architecture Content Framework, Chapter 35: Enterprise Continuum and Tools, Section 35.1 Introduction.

質問 # 45
Which of the following best summarizes the purpose of Enterprise Architecture?

• A. Taking major improvement decisions.
• B. Controlling the bigger changes.
• C. Governing the Stakeholders.
• D. Guiding effective change.

正解：D

解説：
Explanation
EA applies architecture principles and practices to analyze, design, plan, and implement enterprise analysis that supports digital transformation, IT growth, and the modernization of IT2. EA also helps organizations improve the efficiency, timeliness, and reliability of business information, as well as the alignment, agility, and adaptability of the architecture to the changing needs and requirements3. Therefore, the best summary of the purpose of EA is to guide effective change.
References: 1: Enterprise architecture - Wikipedia 2: What is enterprise architecture? A framework for transformation 3: 3 The Purpose of Enterprise Architecture - The Open Group

質問 # 46
Complete the sentence. When considering agile development, Architecture to Support Portfolio will identify what products the Enterprise needs, the boundary of the products, and what constraints a product owner has; this defines the Enterprise's

• A. backlog
• B. operating model
• C. risk tolerance
• D. business continuity

正解：A

解説：
When considering agile development,Architecture to Support Portfoliowill 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'sbacklog, which in agile methodologies, is a prioritized list of work for the development team that is derived from the roadmap and its requirements.

質問 # 47
Which of the following best summarizes the purpose of Enterprise Architecture?

• A. Taking major improvement decisions.
• B. Controlling the bigger changes.
• C. Governing the Stakeholders.
• D. Guiding effective change.

正解：D

解説：
EA applies architecture principles and practices to analyze, design, plan, and implement enterprise analysis that supports digital transformation, IT growth, and the modernization of IT2. EA also helps organizations improve the efficiency, timeliness, and reliability of business information, as well as the alignment, agility, and adaptability of the architecture to the changing needs and requirements3. Therefore, the best summary of the purpose of EA is to guide effective change.
References: 1: Enterprise architecture - Wikipedia 2: What is enterprise architecture? A framework for transformation 3: 3 The Purpose of Enterprise Architecture - The Open Group

質問 # 48
Complete the sentence The Architecture Landscape is divided into levels known as__________________________.

• A. Gaps Plateaus, and Target Architectures
• B. Segment Strategic and Capability Architectures
• C. Transitional Complete and incremental Architectures
• D. Baseline. Transition and To Be Architectures

正解：B

解説：
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.

質問 # 49

Consider the image showing basic architectural concepts.
What are items A and B?

• A. A-Candidate Architecture, B-Trade-off
• B. A-Architecture Board, B-Architecture Capability
• C. A-Requirement. B-Candidate Architecture
• D. A-Architecture Viewpoint, B-Architecture View

正解：D

解説：
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. References:
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

質問 # 50
Consider the following ADM phases objectives.

Which phase does each objective match?

• A. 1G-2H-3H-4F
• B. 1F-2G-3G-4H
• C. 1F-2G-3H-4H
• D. 1H-2F-3F-4G

正解：D

解説：
According to the TOGAF Standard, Version 9.2, the ADM phases and their objectives are as follows1:
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.
Requirements Management: To manage the architecture requirements throughout the ADM cycle, and to ensure alignment with the business requirements.
Based on the above definitions, we can match each objective with the corresponding phase as follows:
Objective 1: Ensure that the business value and cost of work packages and transition architectures is understood by key stakeholders. This objective is achieved in Phase H: Architecture Change Management, where the value realization and cost-benefit analysis of the architecture are performed2.
Objective 2: Ensure conformance with the Target Architecture by implementation projects. This objective is achieved in Phase F: Migration Planning, where the conformance requirements and criteria for the implementation projects are defined3.
Objective 3: Ensure that the architecture development cycle is maintained. This objective is achieved in Phase F: Migration Planning, where the architecture roadmap and iteration cycle are maintained3.
Objective 4: Ensure that the Architecture Governance Framework is executed. This objective is achieved in Phase G: Implementation Governance, where the architecture governance processes and procedures are applied to the implementation projects4.
Reference:
1: The TOGAF Standard, Version 9.2, Chapter 5: Architecture Development Method (ADM)
2: The TOGAF Standard, Version 9.2, Chapter 21: Architecture Change Management
3: The TOGAF Standard, Version 9.2, Chapter 20: Migration Planning
4: The TOGAF Standard, Version 9.2, Chapter 19: Implementation Governance

質問 # 51
Which of the following statements about architecture partitioning is correct?

• A. Partitions are defined and assigned to agile Enterprise Architecture teams.
• B. Partitions reflect the organization's structure.
• C. Partitions are used to simplify the management of the Enterprise Architecture.
• D. Partitions are equivalent to architecture levels.

正解：C

解説：
Explanation
Based on the web search results, architecture partitioning is a technique that divides the Enterprise Architecture into smaller and manageable segments or groups, based on various classification criteria, such as subject matter, time, maturity, volatility, etc.12 Architecture partitioning is used to simplify the development and management of the Enterprise Architecture, by reducing complexity, improving governance, enhancing reusability, and increasing alignment and agility12. Therefore, the statement that partitions are used to simplify the management of the Enterprise Architecture is correct.
The other statements are incorrect because:
*Partitions are not equivalent to architecture levels. Architecture levels are different layers of abstraction that describe the Enterprise Architecture from different perspectives, such as strategic, segment, and capability3.
Partitions are subsets of architectures that are defined within or across the levels, based on specific criteria1.
*Partitions do not necessarily reflect the organization's structure. The organization's structure is one possible criterion for partitioning the architecture, but it is not the only one. Other criteria, such as business function, product, service, geography, etc., can also be used to partition the architecture12.
*Partitions are not defined and assigned to agile Enterprise Architecture teams. Agile Enterprise Architecture is an approach that applies agile principles and practices to the architecture work, such as iterative development, frequent feedback, adaptive planning, and continuous delivery4. Partitions are not a specific feature of agile Enterprise Architecture, but a general technique that can be applied to any architecture method or framework, including TOGAF12.
References: 1: The TOGAF Standard, Version 9.2 - Architecture Partitioning 2: TOGAF Standard - Introduction - Architecture Partitioning 3: [The TOGAF Standard, Version 9.2 - Applying the ADM Across the Architecture Landscape] 4: TOGAF Standard - Introduction - Definitions - The Open Group

質問 # 52
What are the following activities part or?
* Initial risk assessment
* Risk mitigation and residual risk assessment
* Risk monitoring

• A. Security Architecture
• B. Risk Management
• C. Phase A
• D. Phase C

正解：B

解説：
Explanation
The following activities are part of Risk Management:
Initial risk assessment
Risk mitigation and residual risk assessment
Risk monitoring
Risk Management is the process of identifying, assessing, and responding to risks that may affect the achievement of the enterprise's objectives. Risk Management involves balancing positive and negative outcomes resulting from the realization of either opportunities or threats. Reference: The TOGAF Standard | The Open Group Website, Section 3.3.3 Risk Management.

質問 # 53
Consider the following ADM phases objectives.
Objective:
1.Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision
2.Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals
3.Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture
4.Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures Which phase does each objective match?

• A. 1A-2B-3C-4D
• B. 1B-2D-3A-4C
• C. 1C-2D-3B-4A
• D. 1C-2B-3A-4D

正解：D

解説：
Explanation
*Phase A: Architecture Vision
oDevelop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture oDefine the scope and boundaries of the architecture engagement oIdentify the key stakeholders and their concerns and expectations oDefine the Architecture Vision statement and the Architecture Definition Document oObtain approval and commitment from the sponsors and stakeholders
*Phase B: Business Architecture
oDevelop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals oDefine the Baseline Business Architecture, if not available oPerform a gap analysis between the Baseline and Target Business Architectures oDefine candidate roadmap components for the Business Architecture oResolve impacts across the Architecture Landscape
*Phase C: Information Systems Architecture
oDevelop the Target Data Architecture that enables the Business Architecture and the Architecture Vision oDevelop the Target Application Architecture that supports the Business Architecture and the Architecture Vision oDefine the Baseline Data and Application Architectures, if not available oPerform a gap analysis between the Baseline and Target Data and Application Architectures oDefine candidate roadmap components for the Information Systems Architecture oResolve impacts across the Architecture Landscape
*Phase D: Technology Architecture
oDevelop the Target Technology Architecture that enables the Information Systems Architecture and the Architecture Vision oDefine the Baseline Technology Architecture, if not available oPerform a gap analysis between the Baseline and Target Technology Architectures oIdentify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures oResolve impacts across the Architecture Landscape Therefore, the correct matching of the objectives and the phases is:
*1C: Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision
*2B: Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals
*3A: Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture
*4D: Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures References: 1: The TOGAF Architecture Development Method

質問 # 54
What is an objective of the ADM Implementation Governance Phase?

• A. To finalize the Implementation and Migration Plan
• B. To establish the resources for architecture governance
• C. To provide continual monitoring of the governance framework
• D. To ensure conformance for the target architecture

正解：D

解説：
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.

質問 # 55
Which of the following describes the practice by which the enterprise architecture is managed and controlled at an enterprise-wide level?

• A. Architecture governance
• B. IT governance
• C. Technology governance
• D. Corporate governance

正解：A

解説：
According to the TOGAF Standard, 10th Edition, architecture governance is "the practice by which enterprise architectures and other architectures are managed and controlled at an enterprise-wide level" 1. Architecture governance ensures that the architecture development and implementation are aligned with the strategic objectives, principles, standards, and requirements of the enterprise, and that they deliver the expected value and outcomes. Architecture governance also involves establishing and maintaining the architecture framework, repository, board, contracts, and compliance reviews 1. The other options are not correct, as they are not the term used by the TOGAF Standard to describe the practice by which the enterprise architecture is managed and controlled at an enterprise-wide level. Corporate governance is "the system by which an organization is directed and controlled" 2, and it covers aspects such as leadership, strategy, performance, accountability, and ethics. IT governance is "the system by which the current and future use of IT is directed and controlled" 2, and it covers aspects such as IT strategy, policies, standards, and services. Technology governance is "the system by which the technology decisions and investments are directed and controlled" 3, and it covers aspects such as technology selection, acquisition, deployment, and maintenance. References: 1: TOGAF Standard,
10th Edition, Part VI: Architecture Governance, Chapter 44: Introduction. 2: TOGAF Standard, 10th Edition, Part I: Introduction, Chapter 3: Definitions. 3: TOGAF Series Guide: Using the TOGAF Framework to Define and Govern Service-Oriented Architectures, Part II: Using the TOGAF Framework to Define and Govern Service-Oriented Architectures, Chapter 5: Technology Governance.

質問 # 56
Please read this scenario prior to answering the question
You are serving as the Lead Architect for an Enterprise Architecture team within a leading multinational biotechnology company. The company works in three major industries, including healthcare, crop production, and agriculture. Your team works within the healthcare division.
The healthcare division is developing a new vaccine, and has to demonstrate its effectiveness and safety in a set of clinical trials that satisfy the regulatory requirements of the relevant health authorities. The clinical trials are undertaken by its research laboratories at multiple facilities worldwide. In addition to internal research and development activities, the healthcare division is also involved in publicly funded collaborative research projects with industrial and academic partners.
The Enterprise Architecture team has been engaged in an architecture project to develop a secure system that will allow the healthcare researchers to share information more easily about their clinical trials, and work more collaboratively across the organization and also with its partners. This system will also connect with external partners.
The Enterprise Architecture team uses the TOGAF ADM with extensions required to support healthcare manufacturing practices and laboratory practices. Due to the highly sensitive nature of the information that is managed, special care has been taken to ensure that each architecture domain considers the security and privacy issues that are relevant.
The Vice President for Worldwide Clinical Research is the sponsor of the Enterprise Architecture activity.
She has stated that disruptions must be minimized for the clinical trials, and that the rollout must be undertaken incrementally.
Refer to the scenario
You have been asked to recommend the approach to identify the work packages for an incremental rollout meeting the requirements.
Based on the TOGAF standard which of the following is the best answer?

• A. You recommend that an Implementation Factor Catalog is drawn up to indicate actions and constraints.
  A Consolidated Gaps. Solutions and Dependencies Matrix should also be created. For each gap.
  identify a proposed solution and classify it as new development, purchased solution, or based on an existing product. Group similar activities together to form work packages. Identify dependencies between work packages factoring in the clinical trial schedules. Regroup the work packages into a set of Capability Increments scheduled into a series of Transition Architectures.
• B. You recommend that the Solution Building Blocks from a Consolidated Gaps, Solutions and Dependencies Matrix be grouped into a set of work packages. Using the matrix as a planning tool, regroup the work packages to account for dependencies. Sequence the work packages into the Capability Increments needed to achieve the Target Architecture, so that the implementation team can schedule the rollout one region at a time to minimize disruption. Document the work packages for the Enterprise Architecture using a Transition Architecture State Evolution Table.
• C. You recommend that a Consolidated Gaps. Solutions and Dependencies Matrix is used as a planning tool for creating work packages. For each gap classify whether the solution is either a new development, purchased solution, or based on an existing product. Group the similar solutions together to define the work packages. Regroup the work packages into a set of Capability Increments to transition to the Target Architecture considering the schedule for clinical trials, and document in an Architecture Definition Increments Table.
• D. You recommend that the set of required Solution Building Blocks be determined by identifying those which need to be developed and which need to be procured. Eliminate any duplicates. Group the remaining Solution Building Blocks together to create the work packages using a CRUD (create, read, update, delete) matrix. Rank the work packages and select the most cost-effective options for inclusion in a series of Transition Architectures. Schedule the roll out of the work packages to be sequential across the geographic regions.

正解：C

解説：
A Consolidated Gaps, Solutions and Dependencies Matrix is a technique that can be used to create work packages for an incremental rollout of the architecture. A work package is a set of actions or tasks that are required to implement a specific part of the architecture. A work package can be associated with one or more Architecture Building Blocks (ABBs) or Solution Building Blocks (SBBs), which are reusable components of business, IT, or architectural capability. A work package can also be associated with one or more Capability Increments, which are defined, discrete portions of the overall capability that deliver business value. A Capability Increment can be realized by one or more Transition Architectures, which are intermediate states of the architecture that enable the transition from the Baseline Architecture to the Target Architecture123 The steps for creating work packages using this technique are:
* For each gap between the Baseline Architecture and the Target Architecture, identify a proposed solution and classify it as new development, purchased solution, or based on an existing product. A gap is a difference or deficiency in the current state of the architecture that needs to be addressed by the future state of the architecture. A solution is a way of resolving a gap by implementing one or more ABBs or SBBs.
* Group similar solutions together to define the work packages. Similar solutions are those that have common characteristics, such as functionality, technology, vendor, or location.
* Identify dependencies between work packages, such as logical, temporal, or resource dependencies.
Dependencies indicate the order or priority of the work packages, and the constraints or risks that may affect their implementation.
* Regroup the work packages into a set of Capability Increments to transition to the Target Architecture.
Capability Increments should be defined based on the business value, effort, and risk associated with each work package, and the schedule and objectives of the clinical trials. Capability Increments should also be aligned with the Architecture Vision and the Architecture Principles.
* Document the work packages and the Capability Increments in an Architecture Definition Increments Table, which shows the mapping between the work packages, the ABBs, the SBBs, and the Capability Increments. The table also shows the dependencies, assumptions, and issues related to each work package and Capability Increment.
Therefore, the best answer is B, because it describes the approach to identify the work packages for an incremental rollout meeting the requirements, using the Consolidated Gaps, Solutions and Dependencies Matrix as a planning tool.
References: 1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 30:
Gap Analysis 2: The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 36:
Building Blocks 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter
31: Architecture Change Management : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 23: Phase E: Opportunities and Solutions : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 21: Phase F: Migration Planning :
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 III: ADM Guidelines and Techniques, Chapter
23: Architecture Principles

質問 # 57
Consider the following chart:

Which important concept for Enterprise Architecture Practitioners does it illustrate?

• A. ADM phases must be run in a sequenced approach to produce the Architecture.
• B. Enterprise Architects must use Gantt charts to communicate with Stakeholders.
• C. ADM phases must be run simultaneously until the relevant information has been produced.
• D. An Enterprise Architecture must be developed in phases with a limited fixed duration.

正解：A

解説：
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.
Reference:
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

質問 # 58
Please read this scenario prior to answering the question
You are working as an Enterprise Architect at a large supermarket. The company runs many retail stores, as well as an online grocery shop. Many of the stores used to remain open 24/7, but the number has decreased in recent years. Instead, they now focus on fulfilling online orders during the night.
The company has a mature Enterprise Architecture (EA) practice and uses the TOGAF standard for its architecture development method. The EA practice is involved in all aspects of the business, with oversight provided by an Architecture Board with representatives from different parts of the business. The EA program is sponsored by the Chief Information Officer (CIO).
Each store uses a standard method to track sales and inventory. This involves sending accurate timely sales data to a central Al-based inventory management system that can predict demand, adjust stock levels and automate reordering. The central inventory management system is housed at the company's central data center.
The company has bought a major rival. The Chief Executive Officer believes that a merger will enable growth through combined offerings and cost savings. The decision has been taken to fully integrate the two organizations, including merging retail operations and systems. This means that duplicated systems will be replaced with one standard retail management system. Also, the company will reduce the number of applications that are used. The CIO expects significant savings will be achieved by implementing these changes across the newly merged company.
One improvement that the rival has successfully implemented is the use of hand-held devices within stores, for both customers and staff. This has increased both customer and staff employee satisfaction due to the time savings this has brought. The CIO has given the go-ahead to roll out the devices in all stores but has stated that training on how to use the hand-held devices should be brief because there are a lot of employees, many of whom are part-time.
The Request for Architecture Work to oversee the merger has been approved. The project has been scoped and you have been assigned to work on it. Your role includes managing the architecture for the retail stores.
Refer to the scenario
You have been asked to confirm the most relevant architecture principles for the transformation.
Based on the TOGAF Standard, which of the following is the best answer?
[Note: The sequence of the principles listed in each answer does not matter. You should assume the company follows the set of principles that are provided in the TOGAF Standard, ADM Techniques, Architecture Principles chapter. You may need to refer to section 2.6 located in ADM Techniques within the reference text to answer this question.]

• A. Common Vocabulary and Data Definitions, Compliance with the Law, Requirements Based Change, Responsive Change Management, Data Security
• B. Control Technical Diversity, Interoperability, Data is an Asset, Data is Shared, Business Continuity
• C. Maximize Benefit to the Enterprise, Common Use Applications, Data is an Asset, Responsive Change Management, Technology Independence
• D. Common Use Applications, Data is an Asset, Data is Accessible, Ease of Use, Business Continuity

正解：C

解説：
Key aspects of the scenario:
* Business Objective:
* A merger is happening to combine offerings, reduce costs, and achieve operational efficiency.
* The goal includes fully integrating retail operations and systems, replacing duplicated systems, and reducing the number of applications used.
* Technological Improvements:
* A central AI-based inventory system is in place.
* Hand-held devices for stores have improved customer and staff satisfaction and increased efficiency.
* Scope of Architecture Work:
* Integrating the merged systems.
* Managing retail architecture to optimize operations.
TOGAF Alignment:
TOGAF principles aim to ensure the architecture supports business transformation effectively while aligning with governance and best practices.
Best answer analysis:
* Option 1:
* Maximize Benefit to the Enterprise: Aligns with the merger goals of cost reduction and efficiency.
* Common Use Applications: Matches the goal to reduce duplicated systems.
* Data is an Asset: Central AI system depends on accurate and reliable data.
* Responsive Change Management: Necessary to support the transition and manage organizational impacts.
* Technology Independence: Encourages selecting flexible, scalable solutions post-merger.
This option comprehensively aligns with the scenario.
* Option 2:
* Control Technical Diversity: Important but less emphasized than cost reduction and application unification.
* Interoperability: Relevant, but less critical compared to principles addressing business value.
* Data is an Asset: Relevant.
* Data is Shared: Implied in centralized inventory but not directly stated.
* Business Continuity: Important but not the main focus here.
This option partially fits but lacks emphasis on business outcomes.
* Option 3:
* Common Vocabulary and Data Definitions: Indirectly helpful but not central to the transformation.
* Compliance with the Law: Always critical, but no explicit legal issues are mentioned.
* Requirements-Based Change: General principle but not transformation-specific.
* Responsive Change Management: Relevant.
* Data Security: Important but not a central concern in the scenario.
This option focuses more on governance and less on merger goals.
* Option 4:
* Common Use Applications: Relevant to reducing duplicate systems.
* Data is an Asset: Relevant.
* Data is Accessible: Fits with AI system and handheld devices but is a subset of "Data is an Asset."
* Ease of Use: Relevant to handheld devices but not a core transformation principle.
* Business Continuity: Important but secondary to cost and efficiency.
This option focuses more on usability and accessibility rather than transformation objectives.

質問 # 59
Complete the sentence The purpose of the Preliminary Phase is to_____________.

• A. architect an Enterprise Architecture Capability
• B. identify the stakeholders and their requirements
• C. describe the target architecture
• D. define the enterprise strategy

正解：A

解説：
Explanation
The purpose of the Preliminary Phase is to architect an Enterprise Architecture Capability that meets the needs and expectations of the enterprise's stakeholders and supports and enables subsequent phases of architecture development and transition. This phase involves defining the scope, principles, framework, and governance for the Enterprise Architecture Capability. Reference: The TOGAF Standard | The Open Group Website, Section 3.2 Preliminary Phase.

質問 # 60
What are the four architecture domains that the TOGAF standard deals with?

• A. Capability, Segment, Enterprise, Federated
• B. Business, Data, Application, Technology
• C. Baseline, Candidate, Transition, Target
• D. Application, Data, Information, Knowledge

正解：B

解説：
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

質問 # 61
......

ベストなThe Open Group OGEA-103学習ガイドと問題集には2025：https://www.passtest.jp/TheOpenGroup/OGEA-103-shiken.html

トップクラスThe Open Group OGEA-103試験材料で学習ガイド！練習問題バージョンで挑もう：https://drive.google.com/open?id=17LWxNRwxsY12fIOgMhQ4hOC2U4B5Pwm9