100%無料Enterprise Architecture OGEA-103問題集PDFお試しサンプル認定ガイドカバー率 [Q57-Q77]

100%無料Enterprise Architecture OGEA-103問題集PDFお試しサンプル認定ガイドカバー率

PDF試験材料2026年最新の実際に出るOGEA-103問題集

質問 # 57
Consider the illustration.

What are the items labelled A, B and C?

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

正解：D

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

質問 # 58
What is the purpose of the Preliminary Phase?

• A. Describing the target architecture.
• B. Identifying the stakeholders and their requirements.
• C. Developing an Enterprise Architecture Capability.
• D. Defining the Enterprise Strategy.

正解：C

解説：
An Enterprise Architecture Capability is the ability of the organization to perform effective and efficient architecture work, including the definition, governance, and management of its architectures2. The Preliminary Phase involves the following activities1:
* Reviewing the organizational context, scope, and drivers for conducting Enterprise Architecture
* Establishing the Architecture Capability desired by the organization, including the maturity level, roles, responsibilities, processes, and tools
* Defining and establishing the Organizational Model for Enterprise Architecture, which describes how the architecture function is organized and integrated within the enterprise
* Defining and establishing the Architecture Governance framework, which provides the mechanisms for ensuring the quality, consistency, and compliance of the architecture work
* Selecting and implementing the tools that support the Architecture Capability, such as repositories, modeling tools, and communication tools
* Defining the Architecture Principles that will guide and constrain the architecture work, based on the business principles, goals, and drivers of the organization
* Defining the Organization-Specific Architecture Framework, which is an adaptation of the generic TOGAF ADM to suit the specific requirements, standards, and practices of the organization The Preliminary Phase is essential for preparing the organization for the successful development and implementation of its architectures, as well as for ensuring the alignment of the architecture work with the business strategy and objectives1.

質問 # 59
What can be introduced to formalize a joint agreement between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture?

• A. Architecture Contracts
• B. Service Level Agreements
• C. The Statement of Architecture Work
• D. Non-disclosure Agreement

正解：A

解説：
Comprehensive and Detailed Explanation
In TOGAF, Architecture Contracts are agreements between development partners and sponsors that define:
* The deliverables to be produced.
* The quality expectations.
* The fitness-for-purpose of the architecture.
* The responsibilities of each party and the governance arrangements.
Architecture Contracts are a key part of Phase G: Implementation Governance, where they are used to manage and control architecture implementation. They help ensure that implementation projects remain aligned with the approved Target Architecture and business objectives.
They serve as the formal mechanism for:
* Validating that architecture deliverables meet stakeholder expectations.
* Providing a measurable basis for conformance assessment.
* Supporting architecture governance by linking architectural intent with project execution.
Why the other options are incorrect
* B. The Statement of Architecture Work: This defines the scope, approach, resources, and schedule for architecture work, but it is not a joint agreement on deliverables and fitness-for-purpose.
* C. Service Level Agreements (SLAs): These are agreements about operational service levels (e.g., availability, performance), not architecture deliverables.
* D. Non-disclosure Agreement (NDA): This protects confidentiality of information but does not address deliverables, quality, or fitness-for-purpose of an architecture.
References
* The Open Group, TOGAF Standard, Version 9.2, Part II: ADM - Phase G: Implementation Governance, Architecture Contracts.
* The Open Group, TOGAF 9 Certified Study Guide - explanation of Architecture Contracts as a governance tool.

質問 # 60
Consider the following descriptions of deliverables consumed and produced across the TOGAF ADM cycle.

Which deliverables match these descriptions?

• A. 1 Statement of Architecture Work - 2 Architecture Principles - 3 Architecture Requirements Specification - 4 Request for Architecture Work
• B. 1 Architecture Requirements Specification - 2 Request for Architecture Work - 3 Statement of Architecture Work - 4 Architecture Principles
• C. 1 Request for Architecture Work - 2 Statement of Architecture Work - 3 Architecture Principles - 4 Architecture Requirements Specification
• D. 1 Architecture Principles - 2 Architecture Requirements Specification - 3 Request for Architecture Work
  - 4 Statement of Architecture Work

正解：C

解説：
Explanation
The Request for Architecture Work is a deliverable that is sent from the sponsor and triggers the start of an architecture development cycle. It defines the scope, budget, schedule, and deliverables for a specific architecture project. The Statement of Architecture Work is a deliverable that is produced by the architect and defines the approach and resources needed to complete an architecture project. It forms the basis of a contractual agreement between the sponsor and the architecture organization. The Architecture Principles are a deliverable that is produced by the architect and defines the general rules and guidelines for the architecture work. They reflect the business principles, business goals, and business drivers of the organization. The Architecture Requirements Specification is a deliverable that is produced by the architect and defines the requirements that govern the architecture work. It covers both functional and non-functional requirements as well as constraints and assumptions.

質問 # 61
Which of the following best describes the purpose of the Gap Analysis technique?

• A. To identify items omitted from the Target Architecture
• B. To govern the architecture throughout its implementation process
• C. To allocate resources for architecture projects
• D. To develop a set of general rules and guidelines for the architecture

正解：A

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

質問 # 62
Scenario
You are working as an Enterprise Architect within an Enterprise Architecture (EA) team at a global company that sells consumer products. The company produces many products that buyers use and enjoy.
The company has announced a major change to its products that will occur over a four-year period. This change includes the introduction of digital products and services. An architecture to support this strategy has been finished, along with a roadmap for a set of projects to implement this significant change. This will be a cross-functional effort between the product design and software teams. It is planned to be developed in phases.
The company faces a challenge in presenting and providing access to different services through its products and digital platforms while ensuring compliance with data privacy laws. In some countries and regions, the data residency requirements mean that the company has to store certain data within the region where it is collected. As a result, the company's application portfolio and infrastructure must connect with various cloud services and data repositories in different countries.
The EA team has inherited the architecture used by the current products, some of which can be carried over to the new products. The EA team has started to define which parts of the architecture to carry forward. Enough of the Business Architecture has been defined so that work can commence on the Information Systems and Technology Architectures. Those architectures need to be defined to support the key digital services that the company plans to provide.
The company uses the TOGAF Standard as the foundation for its Enterprise Architecture framework, and architecture development follows the purpose-based EA Capability model outlined in the TOGAF Series Guide: A Practitioner's Approach to Developing Enterprise Architecture Following the TOGAF ADM. The EA team reports to the Chief Information Officer (CIO), who oversees the program.
You have been asked how to decide and organize the work to deliver the requested architectures.
Based on the TOGAF standard, which of the following is the best answer?

• A. You look outside the company to study how other companies organize their data models and application portfolios. You create just enough architecture description for the Application, Data, and Technology Architectures to identify the different options. For each project, this includes identification of candidate architecture and solution building blocks. You then identify solution providers, perform a readiness assessment, and assess the viability and fitness of the solution options. You then write the draft Implementation and Migration plan.
• B. You refer to the superior architecture for guidance. You review the projects identified, their dependencies, and synergies, then decide the sequence for starting the projects. You develop high-level architecture descriptions. For each project, you determine how much work is needed, identify reference architectures, and candidate building blocks. You identify the resource needs taking into account cost and value. You document the different options, risks, and ways to control them to enable feasibility analysis and trade-off with the stakeholders.
• C. You research leading data companies, using your findings to help in developing high-level Target Data, Application, and Technology Architectures. You review the Architecture Vision to determine the level of detail, time, and scope of the ADM cycle phases required for each project. You identify and estimate the cost of the main resources. You then prepare an Architecture Roadmap and request the Architecture Board to review the roadmap. You then start the project.
• D. You commence an iteration of ADM Phase A, identifying the stakeholders and revising the Architecture Vision. You perform a Stakeholder Analysis and update the Stakeholder Map. You conduct workshops and interviews to reflect the stakeholders who are now the key drivers for the digital products and services. You coordinate with the CIO to ensure alignment with the overall roadmap and update the Implementation and Migration Plan accordingly.

正解：B

解説：
Comprehensive and Detailed Step-by-Step Explanation
Context of the Scenario
The company is in the process of delivering requested architectures to support the introduction of digital products and services. The Business Architecture is sufficiently defined, and the focus is on developing the Information Systems and Technology Architectures.
TOGAF emphasizes breaking down large, complex transformation programs into manageable projects, focusing on dependencies, risks, trade-offs, and sequencing of efforts. Based on the scenario, the company must deal with:
Data privacy and residency compliance across different regions.
Re-use of existing architecture for efficiency.
Alignment of digital services with a global roadmap.
The activity described aligns with ADM Phases B (Business Architecture), C (Information Systems Architecture), and D (Technology Architecture), with a focus on delivering architectures for implementation.
Option Analysis
Option A:
Strengths:
Refers to developing high-level architecture descriptions and identifying reference architectures and candidate building blocks, which align with ADM Phases B, C, and D.
Addresses feasibility analysis, trade-offs, and stakeholder engagement, which are part of architecture development and decision-making in TOGAF.
Ensures that the architecture descriptions are resource-conscious, including cost and value analysis, dependencies, risks, and synergies between projects.
Conclusion: Correct, as it provides a complete approach to organizing the work to deliver architectures while adhering to TOGAF principles.
Option B:
Strengths:
Suggests creating architecture descriptions for the Application, Data, and Technology Architectures, which are necessary for delivering requested architectures.
Addresses readiness assessments and the fitness of solutions.
Weaknesses:
Emphasizes looking outside the company and studying other companies' models, which is not necessarily aligned with TOGAF unless justified by specific gaps.
Skips essential TOGAF steps like feasibility analysis and detailed stakeholder engagement.
Conclusion: Incorrect, as it places undue emphasis on external research instead of leveraging TOGAF's structured ADM.
Option C:
Strengths:
Suggests reviewing the Architecture Vision and determining scope, which aligns with TOGAF principles.
Proposes preparing an Architecture Roadmap and involving the Architecture Board for review.
Weaknesses:
Does not cover important elements such as candidate building blocks, feasibility analysis, or stakeholder engagement.
Suggests starting the project prematurely without proper sequencing or risk trade-offs.
Conclusion: Incorrect, as it skips key steps and lacks a structured approach to dependencies and resource management.
Option D:
Strengths:
Suggests revising the Architecture Vision and conducting a Stakeholder Analysis, which aligns with Phase A of the ADM.
Weaknesses:
Returning to Phase A is not required here, as the Architecture Vision has already been defined. Revising the vision at this stage indicates a step backward.
Lacks focus on feasibility analysis, dependencies, and sequencing, which are the immediate needs in this phase.
Conclusion: Incorrect, as it unnecessarily revisits earlier ADM phases instead of progressing.
TOGAF References
ADM Phases B, C, D: Emphasizes developing detailed architectures, identifying candidate building blocks, and addressing dependencies, risks, and resource needs (TOGAF 9.2, Chapters 8-10).
Architecture Roadmap and Feasibility Analysis: Guides sequencing and trade-offs for implementation (TOGAF 9.2, Section 12.4).
Stakeholder Engagement: Critical for ensuring alignment and feasibility (TOGAF 9.2, Section 24.2).
Decision-Making and Trade-offs: TOGAF emphasizes documenting risks and trade-offs as part of feasibility analysis (TOGAF 9.2, Section 6.4.1).

質問 # 63
Consider the following descriptions of deliverables consumed and produced across the TOGAF ADM cycle.

Which deliverables match these descriptions?

• A. 1 Statement of Architecture Work - 2 Architecture Principles - 3 Architecture Requirements Specification - 4 Request for Architecture Work
• B. 1 Architecture Requirements Specification - 2 Request for Architecture Work - 3 Statement of Architecture Work - 4 Architecture Principles
• C. 1 Request for Architecture Work - 2 Statement of Architecture Work - 3 Architecture Principles - 4 Architecture Requirements Specification
• D. 1 Architecture Principles - 2 Architecture Requirements Specification - 3 Request for Architecture Work - 4 Statement of Architecture Work

正解：C

解説：
The Request for Architecture Work is a deliverable that is sent from the sponsor and triggers the start of an architecture development cycle. It defines the scope, budget, schedule, and deliverables for a specific architecture project. The Statement of Architecture Work is a deliverable that is produced by the architect and defines the approach and resources needed to complete an architecture project. It forms the basis of a contractual agreement between the sponsor and the architecture organization. The Architecture Principles are a deliverable that is produced by the architect and defines the general rules and guidelines for the architecture work. They reflect the business principles, business goals, and business drivers of the organization. The Architecture Requirements Specification is a deliverable that is produced by the architect and defines the requirements that govern the architecture work. It covers both functional and non-functional requirements as well as constraints and assumptions.

質問 # 64
According to the TOGAF standard, what term describes an individual with an interest in a system?

• A. consumer
• B. lead architect
• C. stakeholder
• D. sponsor

正解：C

解説：
According to the TOGAF Standard, 10th Edition, a stakeholder is "an individual with an interest in a system"
1. A stakeholder can be anyone who is affected by the system, or who can influence or be influenced by the system. Stakeholders can have different roles, perspectives, and concerns regarding the system, and they can be internal or external to the organization. Stakeholder management is a technique that helps to identify, analyze, and engage the stakeholders of an architecture project, and to address their needs and expectations 2.
The other options are not correct, as they are not the term used by the TOGAF Standard to describe an individual with an interest in a system. A consumer is "an individual or group that uses a product or service" 1.
A lead architect is "an individual who is responsible for leading the development of an architecture" 1. A sponsor is "an individual who provides funding and support for an architecture project" 1. References: 1:
TOGAF Standard, 10th Edition, Part I: Introduction, Chapter 3: Definitions. 2: TOGAF Standard, 10th Edition, Part III: ADM Guidelines and Techniques, Chapter 24: Stakeholder Management.

質問 # 65
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. ADM phases must be run simultaneously until the relevant information has been produced.
• C. An Enterprise Architecture must be developed in phases with a limited fixed duration.
• D. Enterprise Architects must use Gantt charts to communicate with Stakeholders.

正解：C

解説：
Explanation
https://pubs.opengroup.org/architecture/togaf8-doc/arch/chap03.html
The chart that you have provided is a Gantt chart that shows the tasks and timelines of a TOGAF project. It illustrates the concept of phased development of an Enterprise Architecture, which is one of the key principles of the TOGAF Architecture Development Method (ADM). The ADM is a cyclic process that consists of nine phases, from Preliminary to Architecture Change Management1. Each phase has a specific purpose, scope, inputs, steps, and outputs, and produces a part of the Enterprise Architecture. The phases are executed in a sequential order, with some iterations and feedback loops, to ensure that the architecture is consistent, complete, and aligned with the business requirements and objectives. The phases also have a limited fixed duration, which is determined by the complexity, scope, and resources of the project. This helps to manage the expectations, risks, and costs of the architecture development, and to deliver the architecture in a timely and effective manner23.

質問 # 66
Which of the following is a responsibility of an Architecture Board?

• A. Conducting assessments of the maturity level of architecture discipline within the organization
• B. Allocating resources for architecture projects
• C. Establishing targets for re-use of components
• D. Creating the Statement of Architecture Work

正解：C

解説：
* An Architecture Board is an executive-level group responsible for the review and maintenance of the strategic architecture and all of its sub-architectures1. It is a key element in a successful Architecture Governance strategy2.
* An Architecture Board is typically made responsible, and accountable, for achieving some or all of the following goals2:
* Providing the basis for all decision-making with regard to the architectures
* Consistency between sub-architectures
* Establishing targets for re-use of components
* Flexibility of the Enterprise Architecture: To meet changing business needs To leverage new technologies
* Enforcement of Architecture Compliance
* Improving the maturity level of architecture discipline within the organization
* Ensuring that the discipline of architecture-based development is adopted
* Supporting a visible escalation capability for out-of-bounds decisions
* Therefore, the correct answer is option D, which captures one of the goals of an Architecture Board as stated in the TOGAF Standard, Version 9.22.
* Option A is incorrect, because conducting assessments of the maturity level of architecture discipline within the organization is not a direct responsibility of an Architecture Board, but rather a part of the Architecture Capability Framework3.
* Option B is incorrect, because allocating resources for architecture projects is not a direct responsibility of an Architecture Board, but rather a part of the Architecture Governance Framework4.
* Option C is incorrect, because creating the Statement of Architecture Work is not a direct responsibility of an Architecture Board, but rather a part of the Architecture Development Method5. References:
* 1: Architecture Board - The Open Group3
* 2: TOGAF Standard, Version 9.2 - Part VI: Architecture Governance Framework - Architecture Board
* 3: TOGAF Standard, Version 9.2 - Part VI: Architecture Governance Framework - Architecture Capability Framework
* 4: TOGAF Standard, Version 9.2 - Part VI: Architecture Governance Framework - Architecture Governance Framework
* 5: TOGAF Standard, Version 9.2 - Part II: Architecture Development Method - Phase A: Architecture Vision

質問 # 67
Which of the following best describes a purpose of the Gap Analysis technique?

• A. To determine service levels for the architecture
• B. To establish quality metrics for the architecture
• C. To identify missing functions
• D. To validate non-functional requirements

正解：C

解説：
Gap analysis is a technique that is used to validate an architecture by highlighting the shortfall between the Baseline Architecture and the Target Architecture. One of the purposes of gap analysis is to identify missing functions that are either deliberately omitted, accidentally left out, or not yet defined in the Target Architecture. Missing functions are marked as gaps that need to be filled by developing or procuring the building blocks.

質問 # 68
Exhibit
Consider the illustration showing an architecture development cycle Which description matches the phase of the ADM labeled as item 2?

• A. Provides architectural oversight for the implementation
• B. Establishes procedures for managing change to the new architecture
• C. Conducts implementation planning for the architecture defined in previous phases
• D. Operates the process of managing architecture requirements

正解：A

解説：
Based on the illustration, the phase of the ADM labeled as item 2 is the Implementation Governance phase. This phase provides architectural oversight for the implementation. It ensures that the implementation project conforms to the architecture. It also provides a framework for monitoring and managing the implementation.
The Implementation Governance phase involves the following activities:
Finalizing the Architecture Roadmap and the supporting Implementation and Migration Plan Assigning an Architecture Board to oversee the implementation Establishing Architecture Contracts with the implementation partners Reviewing and approving the implementation project plans and deliverables Performing Architecture Compliance reviews to ensure alignment with the architecture Performing Architecture Audit reviews to ensure quality and performance of the architecture Resolving any architecture issues or change requests that arise during the implementation Maintaining the architecture lifecycle and ensuring its continuity The Implementation Governance phase is essential for ensuring that the architecture is realized as intended and that it delivers the expected business value and outcomes.
Implementation Governance

質問 # 69
Consider the following statement.
According to the TOGAF standard, a governed approach of a particular deliverable will ensure adherence to the principles, standards, and requirements of the existing or developing architectures.
Which deliverable does this refer to?

• A. An Architecture Contract
• B. The Architecture Definition Document
• C. The Architecture Vision
• D. The Statement of Architecture Work

正解：A

解説：
According to the TOGAF Standard, 10th Edition, an architecture contract is "a formal agreement between a service provider and a service consumer that defines the mutual commitments and expectations for the delivery of an architecture" 1. An architecture contract is a governed approach of a particular deliverable that will ensure adherence to the principles, standards, and requirements of the existing or developing architectures, as it specifies the roles, responsibilities, deliverables, quality criteria, and acceptance criteria for the architecture work 1. The other options are not correct, as they are not governed approaches of a particular deliverable, but rather different types of deliverables within the architecture development process. An architecture vision is "a high-level, aspirational view of the target architecture" 1. A statement of architecture work is "a document that defines the scope and approach that will be used to complete an architecture project" 1. An architecture definition document is "a document that describes the baseline and target architectures for one or more domains" 1. Reference: 1: TOGAF Standard, 10th Edition, Part I: Introduction, Chapter 3: Definitions.

質問 # 70
What is present in all phases within the ADM and should be identified, classified and mitigated before starting a transformation effort?

• A. Budgetary constraints
• B. Information gaps
• C. Risk
• D. Schedule constraints

正解：C

解説：
According to the TOGAF Standard, 10th Edition, risk is present in all phases within the Architecture Development Method (ADM), and it should be identified, classified, and mitigated before starting a transformation effort 1. Risk is defined as "the effect of uncertainty on objectives" 2, and it can have positive or negative impacts on the architecture project. Risk management is a technique that helps to assess and address the potential risks that may affect the achievement of the architecture objectives, and to balance the trade-offs between opportunities and threats. Risk management is applied throughout the ADM cycle, from the Preliminary Phase to the Requirements Management Phase, and it is integrated with other techniques, such as stakeholder management, business transformation readiness assessment, gap analysis, and migration planning 1. The other options are not correct, as they are not present in all phases within the ADM, and they are not necessarily identified, classified, and mitigated before starting a transformation effort. Budgetary constraints are the limitations on the financial resources available for the architecture project, and they are usually considered in Phase E: Opportunities and Solutions, and Phase F: Migration Planning 3. Schedule constraints are the limitations on the time available for the architecture project, and they are also usually considered in Phase E and F 3. Information gaps are the missing or incomplete data or knowledge that may affect the architecture project, and they are usually identified in Phase B: Business Architecture, Phase C:
Information Systems Architecture, and Phase D: Technology Architecture . References: 1: TOGAF Standard,
10th Edition, Part III: ADM Guidelines and Techniques, Chapter 32: Risk Management. 2: TOGAF Standard,
10th Edition, Part I: Introduction, Chapter 3: Definitions. 3: TOGAF Standard, 10th Edition, Part II:
Architecture Development Method, Chapter 16: Phase E: Opportunities and Solutions, and Chapter 17: Phase F: Migration Planning. : TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter
13: Phase B: Business Architecture, Chapter 14: Phase C: Information Systems Architecture, and Chapter 15:
Phase D: Technology Architecture.

質問 # 71
Exhibit:

Consider the illustration. What are the items labelled A, B, and C?

• A. A-Enterprise Repository, B-Governance Repository, C-Board Repository
• B. A-Architecture Repository, B-Governance Repository, C-Architecture Capability
• C. A-Enterprise Repository, B-Board repository, C-Enterprise Capability
• D. A-Architecture Repository, B-Governing Board, C-Enterprise Capability

正解：D

解説：
A-Architecture Repository: This is a part of the Architecture Metamodel that contains artifacts structured according to the metamodel. It includes the Architecture Landscape which is adopted by the enterprise and governed by certain standards and practices.
B-Governing Board: The Governing Board ensures visibility and escalation, meaning it oversees and manages the capability of the architecture landscape. It plays a crucial role in governance.
C-Enterprise Capability: This refers to how well an enterprise can execute its mission, meet business objectives or satisfy its stakeholders' needs and expectations. It's influenced by both internal factors (like resources, processes) and external ones (like market trends).
TOGAF Version 9.1, Chapter 34: 1

質問 # 72
Please read this scenario prior to answering the question
You are employed as an Enterprise Architect consultant within a manufacturing company. The company has multiple business units located worldwide, including retail, manufacturing, pharmaceuticals, and technology.
The company has a mature Enterprise Architecture (EA) practice and uses the TOGAF standard for its architecture development method. The EA practice is engaged throughout all the business units, with governance provided by multiple Architecture Boards with responsibility for a business line. In addition to the EA program, the company uses a number of management frameworks, including business planning, project/portfolio management, and operations management. The EA program is sponsored by the Chief Information Officer (CIO).
After a recent study, senior management are concerned about the impact of the company's multiple data centers and duplication of applications on the business efficiency. To address the concern, a strategic architecture has been defined; it will help improve the ability to meet customer demand and improve the efficiency of operations. The strategic architecture involves the consolidation of multiple applications programs that are currently used in different business units and putting them all onto a cloud-based solution instead.
Each business unit has completed the Architecture Definition documentation to meet its own specific operational requirements. The Enterprise Architects have analyzed the corporate changes and implementation constraints. A consolidated gap analysis has been completed. Based on its results, the architects have reviewed the requirements, dependencies and interoperability requirements needed to integrate the cloud-based solution. The architects have completed the Business Transformation Readiness Assessment. Based on all these factors they have produced a risk assessment. They have also completed the draft Implementation and Migration Plan, the draft Architecture Roadmap, and the Capability Assessment deliverables.
Due to the risks of changing from the current environment, the decision has been taken that a gradual approach is needed to implement the target architectures. It will likely take a few years to complete the whole implementation process.
Refer to the scenario
You have been asked to decide on the next steps for the migration planning.
Based on the TOGAF standard which of the following is the best answer?

• A. You estimate the business value for each project by applying the Business Value Assessment Technique. The assessment should focus on return on investment and performance evaluation criteria used to monitor the progress of the architecture transformation. You confirm and plan a series of Transition Architecture phases using an Architecture Definition Increments Table. You then document the lessons learned and generate the final Implementation and Migration Plan.
• B. You need to determine how the Implementation and Migration plan fits with the other frameworks being used in the organization. You coordinate the planning with the business planning, project/portfolio management and operations management frameworks. You assign a business value to each project, considering the available resources and how well they align with the strategy. You then update the architecture roadmap and the Implementation and Migration Plan.
• C. You conduct a Compliance Assessment to ensure that the architecture is being implemented according to the contract. The Compliance Assessment verifies that the implementation team is using the proper development methodology. It should also include deployment of monitoring tools. If the monitoring tools show that performance targets are not being met, then the performance requirements should be changed and the Implementation and Migration Plan updated.
• D. You update the Architecture Definition Document, which includes setting project objectives and documenting the final requirements. This will ensure that the architecture remains relevant and responsive to the needs of the enterprise. You then produce an Implementation Governance Model to manage the lessons learned prior to finalizing the Implementation and Migration plan. You recommend that lessons learned be quickly applied as changes to the architecture.

正解：B

解説：
Option C aligns best with TOGAF Phase F: Migration Planning, which deals with developing a detailed Implementation and Migration Plan, ensuring alignment with other enterprise frameworks, and assigning business value to work packages and projects.
🔍 TOGAF Phase F Activities (from the standard):
Confirm Management Framework Interactions:
Per TOGAF, Phase F ensures that the migration planning is aligned with the business planning, portfolio/project management, and operations management frameworks used by the enterprise (which are mentioned in the scenario).
TOGAF emphasizes coordination between EA and other enterprise governance processes.
Prioritize Projects:
TOGAF recommends using business value, resource availability, and strategic alignment to prioritize the various work packages and projects for implementation.
This is directly referenced in option C: "assign a business value to each project, considering the available resources and how well they align with the strategy." Update Roadmaps and Implementation Plan:
After coordination and prioritization, the Architecture Roadmap and the Implementation and Migration Plan are updated.
This is essential before formal governance (Phase G).
❌ Why the Other Options Are Incorrect:
A: Incorrect focus on updating the Architecture Definition Document and lessons learned.
The Architecture Definition Document is mostly finalized in Phases B-E.
Lessons learned and governance modeling are more relevant to Phase G (Implementation Governance) and Phase H (Architecture Change Management), not Phase F.
B: Although it mentions the Business Value Assessment Technique (a valid tool in TOGAF), it includes Architecture Definition Increments Table, which is not a standard TOGAF artifact.
Also, "document the lessons learned" is premature in Phase F; these are more applicable in Phase H.
D: Focuses on Compliance Assessment, which is part of Phase G (Implementation Governance), not Phase F.
Changing performance requirements based on monitoring tools is handled during operations and change management, not during migration planning.
📚 Source
Reference from TOGAF:
TOGAF 9.2 - Section 11.3 (Phase F: Migration Planning)
"Activities include confirming the enterprise's capability for transition, prioritizing projects, identifying dependencies and resource availability, and co-ordinating with other management frameworks." TOGAF 9.2 - Section 11.4 Outputs:
Architecture Roadmap (updated)
Implementation and Migration Plan (updated)
Business Value Assessment
Consolidated Gaps, Solutions, and Dependencies

質問 # 73
Consider the following descriptions of deliverables consumed and produced across the TOGAF ADM cycle.
General rules and guidelines, intended to be enduring and seldom
amended, that inform and support the way in which an organization sets
about fulfilling its mission
The joint agreements between development partners and sponsors on the
deliverables, quality, and fitness-for-purpose of an architecture.
A document that is sent from the sponsoring organization to the
architecture organization to trigger the start of an architecture
development cycle
A set of quantitative statements that outline what an implementation
project must do in order to comply with the architecture.
Which deliverables match these descriptions?
1 Architecture Principles -2 Architecture Contracts - 3 Request for Architecture Work - 4 Architecture Requirements Specification
1 Architecture Contracts - 2 Architecture Requirements Specification - 3 Architecture Vision - 4 Architecture Principles
1 Architecture Requirements Specification -2 Architecture Principles - 3 Architecture Vision - 4 Architecture Contracts

正解：

解説：
1 Architecture Principles -2 Architecture Contracts - 3 Architecture Requirements Specification-4 Request for Architecture Work Explanation:
According to the TOGAF standard, the deliverables that match the descriptions are as follows:
1 Architecture Principles: These are general rules and guidelines, intended to be enduring and seldom amended, that inform and support the way in which an organization sets about fulfilling its mission1. They reflect a level of consensus among the various elements of the enterprise, and form the basis for making future IT decisions1.
2 Architecture Contracts: These are the joint agreements between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture2. They are used to ensure that the architecture is implemented and governed according to the agreed-upon specifications and standards2.
3 Request for Architecture Work: This is a document that is sent from the sponsoring organization to the architecture organization to trigger the start of an architecture development cycle3. It defines the scope, schedule, budget, deliverables, and stakeholders of the architecture project3.
4 Architecture Requirements Specification: This is a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture4. It defines the requirements for each architecture domain, as well as the relationships and dependencies among them4.
1: Architecture Principles 2: Architecture Contracts 3: Request for Architecture Work 4: Architecture Requirements Specification

質問 # 74
Refer to the table below:

Which ADM Phase does this describe?

• A. Phase E
• B. Phase F
• C. Phase G
• D. Phase A

正解：B

解説：
The description provided aligns with Phase F: Migration Planning in the TOGAF ADM. This phase focuses on finalizing and implementing the projects necessary to reach the adjusted target state.
Phase F Objective:
Ensures projects and work packages are well-defined and align with stakeholder priorities.
Translates architecture changes into actionable implementation projects.
Assesses risk, value, and effort in implementation.
Establishes the Implementation and Migration Plan.
Key Outputs of Phase F:
Architecture Roadmap (Updated)
Implementation and Migration Plan
Governance Model for Change Implementation
Why Other Options Are Incorrect:
Option A (Phase E: OpportunitiesandSolutions): Focuses on defining projects and high-level solutions, but does not complete their implementation planning.
Option B (Phase A: Architecture Vision): Establishes high-level goals but does not involve migration planning.
Option C (Phase G: Implementation Governance): Ensures the execution aligns with architecture, but does not define projects for migration.
Reference:
TOGAF Standard, 10th Edition - Part II: Architecture Development Method, Chapter 19 (Phase F: Migration Planning).

質問 # 75
Which phase of the ADM has the purpose to develop an Enterprise Architecture Capability?

• A. Preliminary Phase
• B. Phase B
• C. Phase G
• D. Phase A

正解：A

解説：
According to the TOGAF Standard, 10th Edition, the Preliminary Phase of the Architecture Development Method (ADM) has the purpose to develop an Enterprise Architecture Capability 1. An Enterprise Architecture Capability is the ability of the organization to perform the activities and tasks related to Enterprise Architecture, such as defining the scope, principles, vision, governance, and stakeholders of the architecture. The Preliminary Phase also establishes the architecture framework, the architecture repository, the architecture tools, and the architecture team 1. The other options are not correct, as they have different purposes in the ADM. Phase G: Implementation Governance has the purpose to ensure that the implementation projects conform to the target architecture 2. Phase A: Architecture Vision has the purpose to define the scope, stakeholders, business drivers, and objectives of the architecture project 3. Phase B: Business Architecture has the purpose to describe the baseline and target business architecture, and to identify the gaps between them .

質問 # 76
Which of the following best describes a purpose of the Gap Analysis technique?

• A. To determine service levels for the architecture
• B. To establish quality metrics for the architecture
• C. To identify missing functions
• D. To validate non-functional requirements

正解：C

解説：
Explanation
Gap analysis is a technique that is used to validate an architecture by highlighting the shortfall between the Baseline Architecture and the Target Architecture. One of the purposes of gap analysis is to identify missing functions that are either deliberately omitted, accidentally left out, or not yet defined in the Target Architecture. Missing functions are marked as gaps that need to be filled by developing or procuring the building blocks.

質問 # 77
......

更新されたのはThe Open Group OGEA-103問題集PDFオンラインエンジン：https://jp.fast2test.com/OGEA-103-premium-file.html

OGEA-103.PDFで問題解答PDFサンプル問題信頼され続ける：https://drive.google.com/open?id=1BXx87Z6mjZNZWACz8iitJgkonBO4wPmS