OGEA-10B試験問題を今すぐ試そう！最新の[2024年最新] 正解回答付き [Q34-Q56]

OGEA-10B試験問題を今すぐ試そう！最新の[2024年最新] 正解回答付き

練習できるOGEA-10Bには認定ガイド問題と解答とトレーニングを提供しています

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

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

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

質問 # 35
What can architects present to stakeholders to extract hidden agendas, principles, and requirements that could impact the final Target Architecture?

A. Solutions and Applications
B. Alternatives and Trade-offs
C. Architecture Views and Architecture Viewpoints
D. Business Scenarios and Business Models

正解：C

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

質問 # 36
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. The Architecture Vision
B. The Statement of Architecture Work
C. An Architecture Contract
D. The Architecture Definition Document

正解：C

解説：
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. References: 1: TOGAF Standard, 10th Edition, Part I: Introduction, Chapter 3:
Definitions.

質問 # 37
Exhibit:

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

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

正解：C

解説：
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).
References: TOGAF Version 9.1, Chapter 34: 1

質問 # 38
Consider the following ADM phases objectives.

Which phase does each objective match?

A. 1F-2G-3G-4H
B. 1G-2H-3H-4F
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.
References:
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

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

A. Taking major improvement decisions.
B. Governing the Stakeholders.
C. Controlling the bigger changes.
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

質問 # 40
Please read this scenario prior to answering the question
You have been appointed as Chief Enterprise Architect (CEA). reporting to the Chief Technical Officer (CTO), of a company established as a separate operating entity by a major automotive manufacturer. The mission of the company is to build a new industry leading unified technology and software platform for electric vehicles.
The company uses the TOGAF Standard as the basis for its Enterprise Architecture (EA) framework, and architecture development follows the purpose-based EA Capability model as described in the TOGAF Series Guide: A Practitioners'Approach to Developing Enterprise Architecture Following the TOGAF ADM.
An end-to-end Target Architecture has been completed with a roadmap for change over a five-year period. The new platform will be a cross-functional effort between hardware and software teams, with significant changes over the old platform. It is expected to be developed in several stages over three years. The EA team has inherited the architecture for the previous generation hardware and software automotive platform, some of which can be carried over to the new unified platform. The EA team has started to define the new platform, including defining 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 need to be defined to support the core business services that the company plans to provide. The core services will feature an innovative approach with swarm data generated by vehicles, paving the way for autonomous driving in the future.
The presentation and access to different variations of data that the company plans to offer through its platform pose an architecture challenge. The application portfolio and supporting infrastructure need to interact with various existing cloud services and data- Refer to the scenario You have been asked what approach should be taken to determine and organize the work to deliver the requested architectures?
Based on the TOGAF standard which of the following is the best answer?

A. You would look outside the enterprise to research data models and application portfolios of leading big data businesses. You would develop just enough applications, data, and technology architecture to identify options. For each project this should include identification of candidate architecture and solution building blocks. You will identify solution providers, perform a readiness assessment, and assess the viability and fitness of the solution options. You will then document the draft Implementation and Migration plan.
B. You will revisit ADM Phase A. identifying the stakeholders and creating a new Architecture Vision.
You will update the Stakeholder map produced for the strategic architecture so it reflects the stakeholders who are now the most relevant to the projects that are to be developed. You would then ask the CTO to make some decisions about the Architecture Roadmap, and update the Implementation and Migration Plan to reflect the decisions.
C. You will research leading data businesses, developing high-level Target Data, Application and Technology Architectures. You would review the Architecture Vision in order to estimate the level of detail, time, and breadth of the ADM cycle phases that will be needed to develop the architecture. You will identify and cost major work packages, and then develop an Architecture Roadmap. You would then seek approval by the Architecture Board and initiate the project.
D. You would refer to the end-to-end Target Architecture for guidance and direction. The first objective should be to identify projects, dependencies and synergies, then prioritize before initiating the projects.
You will develop high-level architecture descriptions. For each project you would estimate effort size, identify reference architectures, and candidate building blocks. You will identify the resource needs considering cost and value. You will document options, risks, and controls to enable viability analysis and trade-off with the stakeholders.

正解：D

解説：
The Target Architecture is a description of the future state of the architecture that addresses the business goals and drivers, and satisfies the stakeholder requirements and concerns. The Target Architecture is developed through the Architecture Development Method (ADM), which is the core process of the TOGAF standard that guides the development and management of the enterprise architecture. The Target Architecture is typically divided into four domains: Business, Data, Application, and Technology. The Target Architecture also includes a roadmap for change, which defines the Transition Architectures, the Capability Increments, and the work packages that enable the transition from the Baseline Architecture to the Target Architecture12 The best answer is B, because it describes the approach that should be taken to determine and organize the work to deliver the requested architectures, which are the Information Systems and Technology Architectures.
The answer covers the following steps:
Refer to the end-to-end Target Architecture for guidance and direction. The end-to-end Target Architecture provides the overall vision, scope, and objectives of the architecture work, and the alignment with the business strategy and goals. The end-to-end Target Architecture also provides the high-level definitions and principles for the four architecture domains, and the roadmap for change that outlines the major milestones and deliverables.
Identify projects, dependencies and synergies, then prioritize before initiating the projects. Projects are the units of work that implement the architecture work packages, which are the sets of actions or tasks that are required to implement a specific part of the architecture. Dependencies are the relationships and constraints that affect the order or priority of the projects, such as logical, temporal, or resource dependencies. Synergies are the benefits or advantages that result from the combination or coordination of the projects, such as cost savings, efficiency gains, or innovation opportunities. Prioritization is the process of ranking the projects according to their importance, urgency, or value, and assigning resources and schedules accordingly.
Develop high-level architecture descriptions. High-level architecture descriptions are the outputs of the architecture development phases (B, C, and D) of the ADM cycle, which describe the Business, Data, Application, and Technology Architectures in terms of the Architecture Building Blocks (ABBs) and the Solution Building Blocks (SBBs), which are reusable components of business, IT, or architectural capability. High-level architecture descriptions also include the Architecture Views, which are representations of the system of interest from the perspective of one or more stakeholders and their concerns.
For each project, estimate effort size, identify reference architectures, and candidate building blocks.
Effort size is the measure of the amount of work, time, or resources required to complete a project.
Effort size can be estimated using various techniques, such as analogy, expert judgment, parametric, or bottom-up. Reference architectures are standardized architectures that provide a common framework and vocabulary for a specific domain or industry. Reference architectures can be used as a source of best practices, patterns, and models for the architecture development. Candidate building blocks are the potential ABBs or SBBs that can be used to implement the architecture. Candidate building blocks can be identified from the Architecture Repository, which is a collection of architecture assets, such as models, patterns, principles, standards, and guidelines.
Identify the resource needs considering cost and value. Resource needs are the specifications and criteria that define the acceptable level and quality of the resources required to complete the project, such as human, financial, physical, or technological resources. Resource needs can be identified by analyzing the scope, complexity, and dependencies of the project, and the availability, capability, and suitability of the resources. Cost and value are the factors that influence the allocation and utilization of the resources, such as the budget, the return on investment, the benefits, or the risks.
Document options, risks, and controls to enable viability analysis and trade-off with the stakeholders.
Options are the alternative ways of achieving the project objectives, such as different solutions, technologies, vendors, or approaches. Risks are the effects of uncertainty on the project objectives, such as threats or opportunities. Controls are the measures or actions that are taken to prevent, reduce, or mitigate the risks, such as policies, procedures, or standards. Viability analysis is the process of evaluating and comparing the options, risks, and controls, and determining the feasibility, suitability, and desirability of each option. Trade-off is the decision outcome that balances and reconciles the multiple, often conflicting, requirements and concerns of the stakeholders, and ensures alignment with the Architecture Vision and the Architecture Principles.
References: 1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 5: Introduction to the ADM 2: The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 36: Building Blocks : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 19: Phase B: Business Architecture : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 20: Phase C: Information Systems Architectures : 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 III: ADM Guidelines and Techniques, Chapter 23: Architecture Principles : The TOGAF Standard, Version 9.2, Part III:
ADM Guidelines and Techniques, Chapter 30: Trade-Off Analysis : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 46: Tools for Architecture Development : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 47: Architecture Board : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 48: Architecture Compliance : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 49:
Architecture Contract : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50: Architecture Governance : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 51: Architecture Maturity Models : The TOGAF Standard, Version 9.2, Part VI:
Architecture Capability Framework, Chapter 52: Architecture Skills Framework

質問 # 41
What is defined as the effect of uncertainty on objectives?

A. Threat
B. Continuity
C. Risk
D. Vulnerability

正解：C

解説：
Risk is defined as the effect of uncertainty on objectives, according to the ISO 31000 standard, which provides principles and guidelines for risk management1 Risk can be positive or negative, depending on whether the uncertainty affects the achievement or the failure of the objectives. Risk can also be expressed in terms of likelihood and impact, which indicate the probability and the consequence of the risk occurrence. Risk management is the coordinated activities to direct and control an organization with regard to risk. Risk management is an integral part of the TOGAF standard, as it helps to identify, assess, and treat the risks that may affect the architecture development and implementation2 References: 1: ISO 31000:2018, Risk management - Guidelines, Clause 3.1 2: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 32: Risk Management

質問 # 42
Please read this scenario prior to answering the question
You are the Lead Enterprise Architect at a major agribusiness company. The company's main annual harvest is lentils, a highly valued food grown worldwide. The lentil parasite, broomrape, has been an increasing concern for many years and is now becoming resistant to chemical controls. In addition, changes in climate favor the propagation and growth of the parasite. As a result, the parasite cannot realistically be exterminated, and it has become pandemic, with lentil yields falling globally.
The CEO appreciates the seriousness of the situation and has set out a change in direction that is effectively a new business for the company. There are opportunities for new products, and new markets. The company will use the fields for another harvest and will cease to process third-party lentils. Thus, the target market will change, and the end-products will be different and more varied. This is a major decision and the CEO has stated a desire to repurpose rather than replace so as to manage the risks and limit the costs.
The company has a mature Enterprise Architecture practice based in its headquarters and uses the TOGAF standard as the method and guiding framework. The practice has an established Architecture Capability, and uses iteration for architecture development. The CIO is the sponsor of the activity.
The CIO has assigned the Enterprise Architecture team to this activity. At this stage there is no shared vision, or requirements.
Refer to the scenario
You have been asked to propose the best approach for architecture development to realize the CEO's change in direction for the company.
Based on the TOGAF standard which of the following is the best answer?

A. You propose that the priority is to understand and bring structure to the definition of the change. The team should focus iteration cycles on a baseline first approach to architecture development, and then transition planning. This will identify what needs to change in order to transition from the baseline to the target, and can be used to work out in detail what the shared vision is for the change.
B. You propose that the team focus its iteration cycles on architecture development by going through the architecture definition phases (B-D) with a baseline first approach.
This will support the change in direction as stated by the CEO. It will ensure that the change can be defined in a structured manner and address the requirements needed to realize the change.
C. You propose that this engagement define the baseline Technology Architecture first in order to assess the current infrastructure capacity and capability for the company. Then the focus should be on transition planning and incremental architecture deployment.
This will identify requirements to ensure that the projects are sequenced in an optimal fashion so as to realize the change.
D. You propose that the team focus on architecture definition, with emphasis on defining the change parameters to support this new business strategy that the CEO has identified. Once understood, the team will be in the best position to identify the requirements, drivers, issues, and constraints for the change. You would ensure that the architecture development addresses non-functional requirements to assure that the target architecture is robust and secure.

正解：A

解説：
Based on the TOGAF standard, this answer is the best approach for architecture development to realize the CEO's change in direction for the company. The reason is as follows:
The scenario describes a major business transformation that requires a clear understanding of the current and future states of the enterprise, as well as the gaps and opportunities for change. Therefore, the priority is to understand and bring structure to the definition of the change, rather than focusing on the implementation details or the technology aspects.
The team should use the TOGAF ADM as the method and guiding framework for architecture development, and adapt it to suit the specific needs and context of the enterprise. The team should also leverage the existing Architecture Capability and the Architecture Repository to reuse and integrate relevant architecture assets and resources.
The team should focus iteration cycles on a baseline first approach to architecture development, which means starting with the definition of the Baseline Architecture in each domain (Business, Data, Application, and Technology), and then defining the Target Architecture in each domain. This will help to identify the current and desired states of the enterprise, and to perform a gap analysis to determine what needs to change in order to achieve the business goals and objectives.
The team should then focus on transition planning, which involves identifying and prioritizing the work packages, projects, and activities that will deliver the change. The team should also create an Architecture Roadmap and an Implementation and Migration Plan that will guide the execution and governance of the change.
The team should use the Architecture Vision phase and the Requirements Management phase to work out in detail what the shared vision is for the change, and to capture and validate the stakeholder requirements and expectations. The team should also use the Architecture Governance framework to ensure the quality, consistency, and compliance of the architecture work.
References: : The TOGAF Standard, Version 9.2 - Architecture Development Method : The TOGAF Standard, Version 9.2 - Architecture Vision : The TOGAF Standard, Version 9.2 - Requirements Management : [The TOGAF Standard, Version 9.2 - Architecture Governance]

質問 # 43
Please read this scenario prior to answering the question
Your role is that of a senior architect, reporting to the Chief Enterprise Architect, at a medium-sized company with 400 employees. The nature of the business is such that the data and the information stored on the company systems is their major asset and is highly confidential.
The company employees travel extensively for work and must communicate over public infrastructure using message encryption, VPNs, and other standard safeguards. The company has invested in cybersecurity awareness training for all its staff. However, it is recognized that even with good education as well as system security, there is a dependency on third-parly suppliers of infrastructure and software.
The company uses the TOGAF standard as the method and guiding framework for its Enterprise Architecture (EA) practice. The CTO is the sponsor of the activity.
The Chief Security Officer (CSO) has noted an increase in ransomware (malicious software used in ransom demands) attacks on companies with a similar profile. The CSO recognizes that no matter how much is spent on education, and support, it is likely just a matter of time before the company suffers a significant attack that could completely lock them out of their information assets.
A risk assessment has been done and the company has sought cyber insurance that includes ransomware coverage. The quotation for this insurance is hugely expensive. The CTO has recently read a survey that stated that one in four organizations paying ransoms were still unable to recover their data, while nearly as many were able to recover the data without paying a ransom. The CTO has concluded that taking out cyber insurance in case they need to pay a ransom is not an option.
Refer to the scenario
You have been asked to describe the steps you would take to improve the resilience of the current architecture?
Based on the TOGAF standard which of the following is the best answer?

A. You would monitor for technology changes from your existing suppliers that could improve resilience.
You would prepare and run a disaster recovery planning exercise for a ransomware attack and analyze the performance of the current Enterprise Architecture. Using the findings, you would prepare a gap analysis of the current Enterprise Architecture. You would prepare change requests to address identified gaps. You would add the changes implemented to the Architecture Repository.
B. You would request an Architecture Compliance Review with the scope to examine the company's resilience to ransomware attacks. You would identify the departments involved and have them nominate representatives. You would then tailor checklists to address the requirement for increased resilience.
You would circulate to the nominated representatives for them to complete. You would then review the completed checklists, identifying and resolving issues. You would then determine and present your recommendations.
C. You would determine business continuity requirements, and undertake a gap analysis of the current Enterprise Architecture. You would make recommendations for change requirements to address the situation and create a change request. You would manage a meeting of the Architecture Board to assess and approve the change request. Once approved you would produce a new Request for Architecture Work to activate an ADM cycle to carry out a project to define the change.
D. You would ensure that the company has in place up-to-date processes for managing change to the current Enterprise Architecture. Based on the scope of the concerns raised you recommend that this be managed at the infrastructure level. Changes should be made to the baseline description of the Technology Architecture. The changes should be approved by the Architecture Board and implemented by change management techniques.

正解：C

解説：
Business continuity is the ability of an organization to maintain essential functions during and after a disaster or disruption. Business continuity requirements are the specifications and criteria that define the acceptable level of performance and availability of the business processes and services in the event of a disaster or disruption. A gap analysis is a technique that compares the current state of the architecture with the desired state, and identifies the gaps or differences that need to be addressed. A change request is a formal proposal for an amendment to some product or system, such as the architecture. A Request for Architecture Work is a document that describes the scope, approach, and expected outcomes of an architecture project123 The best answer is A, because it describes the steps that would improve the resilience of the current architecture, which is the ability to withstand and recover from a ransomware attack or any other disruption.
The steps are:
Determine the business continuity requirements, which specify the minimum acceptable level of performance and availability of the business processes and services in case of a ransomware attack. This would involve identifying the critical business functions, the recovery time objectives, the recovery point objectives, and the dependencies and resources needed for recovery.
Undertake a gap analysis of the current Enterprise Architecture, which compares the current state of the architecture with the desired state based on the business continuity requirements. This would involve assessing the strengths and weaknesses of the current architecture, the risks and opportunities for improvement, and the gaps or differences that need to be addressed.
Make recommendations for change requirements to address the situation and create a change request.
This would involve proposing solutions and alternatives to close the gaps, enhance the resilience, and mitigate the risks of the current architecture. The change request would document the rationale, scope, impact, and benefits of the proposed changes, and seek approval from the relevant stakeholders.
Manage a meeting of the Architecture Board to assess and approve the change request. The Architecture Board is a governance body that oversees the architecture work and ensures compliance with the architecture principles, standards, and goals. The meeting would involve presenting the change request, discussing the pros and cons, resolving any issues or conflicts, and obtaining the approval or rejection of the change request.
Once approved, produce a new Request for Architecture Work to activate an ADM cycle to carry out a project to define the change. The Request for Architecture Work would describe the scope, approach, and expected outcomes of the architecture project that would implement the approved change request.
The Request for Architecture Work would initiate a new cycle of the Architecture Development Method (ADM), which is the core process of the TOGAF standard that guides the development and management of the enterprise architecture.
References: 1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 33:
Business Scenarios 2: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter
30: Gap Analysis 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 7: Request for Architecture Work : The TOGAF Standard, Version 9.2, Part III:
ADM Guidelines and Techniques, Chapter 34: Business Transformation Readiness Assessment : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 30: Gap Analysis : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 31: Architecture Change Management : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50:
Architecture Governance : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 7: Request for Architecture Work

質問 # 44
When considering the scope of an architecture, what dimension considers to what level of detail the architecting effort should go?

A. Breadth
B. Architecture Domains
C. Depth
D. Project

正解：C

解説：
The scope of an architecture is the extent and level of detail of the architecture work. The scope of an architecture can be defined along four dimensions: project, breadth, depth, and architecture domains. The project dimension considers the boundaries and objectives of the architecture project, such as the time frame, budget, resources, and deliverables. The breadth dimension considers the coverage and completeness of the architecture across the enterprise, such as the organizational units, business functions, processes, and locations.
The depth dimension considers the level of detail and specificity of the architecture, such as the granularity, abstraction, and precision of the architectural elements and relationships. The architecture domains dimension considers the aspects or segments of the architecture, such as the business, data, application, and technology domains.
Therefore, the depth dimension is the one that considers to what level of detail the architecting effort should go.
References: : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 25:
Architecture Scope : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter
25.2: Scope Dimensions : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 25.2.1: Project, Breadth, Depth, and Architecture Domains

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

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

正解：C

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

質問 # 46
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 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.
B. 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.
C. 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.
D. 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

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

質問 # 47
What are the following activities part of?
. Risk classification
. Risk identification
. Initial risk assessment

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

正解：C

解説：
Risk management is a generic technique that can be applied across all phases of the Architecture Development Method (ADM), as well as in the Preliminary Phase and the Requirements Management Phase2. Risk management involves the following steps1:
*Risk identification: This step involves identifying the potential risks that may affect the architecture project, such as technical, business, organizational, environmental, or legal risks. The risks can be identified through various sources, such as stakeholder interviews, workshops, surveys, checklists, historical data, or expert judgment.
*Risk classification: This step involves categorizing the risks based on their nature, source, impact, and priority. The risks can be classified according to different criteria, such as time, cost, scope, quality, security, or compliance. The classification helps in prioritizing the risks and allocating resources and efforts to address them effectively.
*Initial risk assessment: This step involves assessing the likelihood and impact of each risk, and determining the initial level of risk. The likelihood is the probability of the risk occurring, and the impact is the severity of the consequences if the risk occurs. The initial level of risk is the product of the likelihood and impact, and it indicates the urgency and importance of the risk. The initial risk assessment helps in identifying the most critical risks that need immediate attention and mitigation.
References: 1: The TOGAF Standard, Version 9.2 - Risk Management 2: TOGAF ADM: Top 10 techniques - Part 9: Risk Management

質問 # 48
Which of the following statements about architecture partitioning are correct*?
1 Partitions are used to simplify the management of the Enterprise Architecture
2 Partitions are equivalent to architecture levels
3 Partitions enable different teams to work on different element of the architecture at the same time.
4 Partitions reflect the organization's structure

A. 2 & 4
B. 1 & 3
C. 1 & 4
D. 2 & 3

正解：B

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

質問 # 49
Which of the following best describes purpose of the Business Scenarios?

A. To catch errors in a project architecture early
B. To identify risk when implementing an architecture project
C. To guide decision making throughout the enterprise
D. To identify and understand requirements

正解：D

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

質問 # 50
Which of the following does the TOGAF standard describe as a package of functionality defined to meet business needs across an organization?

A. A deliverable
B. A solution architecture
C. A building block
D. An application

正解：C

質問 # 51
Complete the sentence. The key purpose of Gap Analysis is to _____

A. establish quality parameters for the architecture
B. determine the required service levels for the architecture
C. validate nonfunctional requirements
D. identify commercial building blocks to be purchased
E. identify potential missing or overlapping functions

正解：E

解説：
Gap Analysis is a technique that compares the Baseline Architecture and the Target Architecture to identify the differences and gaps between them. The purpose of this technique is to determine the changes and additions that are required to achieve the desired future state of the architecture. One of the main aspects of Gap Analysis is to identify the functions that are missing or overlapping in the current and future architectures, and to plan how to address them. This helps to ensure that the architecture is complete, consistent, and aligned with the business objectives and requirements3

質問 # 52
What does the TOGAF ADM recommend for use in developing an Architecture Vision document?

A. Architecture Principles
B. Gap Analysis
C. Business Scenarios
D. Requirements Management

正解：C

解説：
Business scenarios are a technique recommended by the TOGAF ADM for use in developing an Architecture Vision document12. Business scenarios are a means of capturing the business requirements and drivers, the processes and actors involved, and the desired outcomes and measures of success34. Business scenarios help to create a common vision and understanding among the stakeholders, and to identify and validate the architecture requirements . Business scenarios also provide a basis for analyzing the impact and value of the proposed architecture. References:
*The TOGAF Standard, Version 9.2 - Phase A: Architecture Vision - The Open Group
*TOGAF Standard - Introduction - Phase A: Architecture Vision
*The TOGAF Standard, Version 9.2 - Definitions - The Open Group
*Business Scenarios - The Open Group
*[The TOGAF Standard, Version 9.2 - Architecture Requirements Specification - The Open Group]
*[The TOGAF Standard, Version 9.2 - Architecture Vision - The Open Group]
*[The TOGAF Standard, Version 9.2 - Business Transformation Readiness Assessment - The Open Group]

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

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

正解：D

解説：
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 . References: 1: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 6: Preliminary Phase. 2: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 18: Phase G: Implementation Governance. 3: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 12: Phase A: Architecture Vision. : TOGAF Standard, 10th Edition, Part II:
Architecture Development Method, Chapter 13: Phase B: Business Architecture.

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

A. To develop a vision of the business value to be delivered by the proposed enterprise architecture
B. To obtain approval for the Statement of Architecture Work
C. To select and implement tools to support the Architecture Capability
D. To create the initial version of the Architecture Roadmap

正解：C

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

質問 # 55
Which of the following describes how the Enterprise Continuum is used when developing an enterprise architecture?

A. To classify architecture and solution assets
B. To identify and understand business requirements
C. To describe how an architecture addresses stakeholder concerns
D. To coordinate with the other management frameworks in use

正解：A

解説：
The Enterprise Continuum consists of two complementary concepts: the Architecture Continuum and the Solutions Continuum1. The Architecture Continuum provides a consistent way to describe and understand the generic and reusable architecture building blocks, such as models, patterns, and standards, that can be applied and tailored to specific situations2. The Solutions Continuum provides a consistent way to describe and understand the specific and implemented solution building blocks, such as products, services, and components, that realize the architecture building blocks3. The Enterprise Continuum enables the reuse and integration of architecture and solution assets across different levels of abstraction, scope, and detail, ranging from foundation architectures to organization-specific architectures1.
The Enterprise Continuum is used when developing an enterprise architecture to support the following activities1:
*Selecting relevant architecture and solution assets from the Architecture Repository or other sources, based on the business drivers, goals, and requirements
*Adapting and customizing the architecture and solution assets to suit the specific needs and context of the enterprise
*Defining and developing the target architecture and the architecture roadmap, based on the gaps and opportunities identified between the baseline and the target states
*Defining and developing the implementation and migration plan, based on the architecture roadmap and the solution building blocks
*Governing and managing the architecture and solution assets throughout the architecture lifecycle, ensuring their quality, consistency, and compliance References: 1: The TOGAF Standard, Version 9.2 - Enterprise Continuum 2: The TOGAF Standard, Version
9.2 - Architecture Continuum 3: The TOGAF Standard, Version 9.2 - Solutions Continuum

質問 # 56
......

試験準備には欠かさない！トップクラスのThe Open Group OGEA-10B試験アプリ学習ガイド練習問題最新版：https://www.jpntest.com/shiken/OGEA-10B-mondaishu

無料The Open Group OGEA-10Bテスト練習問題試験問題集：https://drive.google.com/open?id=14jiuEmS-wnb2H5DU09anyth6Fgpy9ynI