OGEA-102 TOGAF Enterprise Architecture Part 2 Exam (English) Questions and Answers

Questions 4

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?

Options:

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. D

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 sched

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

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. Schedu

Buy Now

Answer:

Explanation:

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.

[: 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, ]

Questions 5

Scenario

You are working as an Enterprise Architect within an Enterprise Architecture (EA) team at a large government agency. The agency has multiple divisions.

The agency has a well-established EA practice and follows the TOGAF standard as its method for architecture development. Along with the EA program, the agency also uses various management frameworks, including business planning, project/portfolio management, and operations management. The EA program is sponsored by the Chief Information Officer (CIO), who has actively promoted architecting with agility within the EA department as her preferred approach for projects.

The government has mandated that the agency prepare themselves for an Artificial Intelligence (AI)-first world, which they have called their “AI-first” plan. As a result, the agency is looking to determine the impact and role that AI will play moving forward. The CIO has approved a Request for Architecture Work to look at how AI can be used for services across the agency. She has noted that digital platforms will be a priority for investment in order to scale the AI applications planned. Using AI to automate tasks and make things run smoother is seen as a big advantage. Process automation and improved efficiency from manual, repetitive activities have been identified as the key benefits of applying generative AI to their agency’s business. This will include back-office automation, for example, for help center agents who receive hundreds of email inquiries. This should also improve services for citizens by making them more efficient and personalized, tailored to each individual’s needs.

Many of the agency leaders are worried about relying too much on AI. Some leaders think their employees will need to learn new skills. Some employees are worried they might lose their jobs to AI. Other leaders worry about security and cyber resilience in the digital platforms needed for AI to be successful.

The leader of the Enterprise Architecture team has asked for your suggestions on how to address the concerns, and how to manage the risks of a new architecture for the AI-first project.

Based on the TOGAF standard, which of the following is the best answer?

Options:

You recommend creating an Organization Map to display the links between different parts of the agency. This will help the EA team to find and involve all areas of the agency impacted by this strategic change. Multiple business models should then be created that can be applied to AI-related projects. A meeting will be held with the stakeholders to teach them how to interpret the models and see how their concerns are being addressed. Risk wil

You recommend that the key stakeholders be formally identified. This should include those who will be most helpful for the change to be successful. A Communication Plan should be made to address their needs. This plan should include a report that summarizes the key features of the architecture based on stakeholder requirements and addressing concerns. You communicate with each key stakeholder to make sure their concerns are being addressed.

You recommend conducting an analysis of the stakeholders. This involves documenting the positions, concerns, issues, and cultural factors of each group. This information will shape how the architecture is to be presented and communicated. The concerns and relevant views can then be defined for each group and recorded in the Architecture Vision document. The requirements for addressing risk should be recorded in the Architecture Requirements

You recommend conducting an analysis that separates the different types of stakeholders into groups. They can be divided into categories: corporate functions, end-user organization, project team, external vendors, and external partners. A model will be developed for each stakeholder category to ensure that all the necessary information and actions are taken into account. Meetings will be arranged with stakeholders to verify that their conce

Buy Now

Answer:

Explanation:

Comprehensive and Detailed Step-by-Step Explanation

Context of the Scenario

The agency is initiating a strategic “AI-first” plan to transform processes using AI and improve efficiency while ensuring service improvements for citizens. Several stakeholder concerns have been raised, such as:

Job security for employees.

Skill development for adapting to new technologies.

Cybersecurity and resilience risks due to reliance on digital platforms.

TOGAF emphasizes the importance of stakeholder management, communication, and risk management to ensure successful adoption and implementation of new architecture. These concerns need to be addressed methodically by gathering requirements, analyzing stakeholder positions, and ensuring proper communication of risks and benefits.

Option Analysis

Option A:

Strengths:

Proposes creating an Organization Map to identify the links between different parts of the agency and the impact of the strategic change.

Suggests holding stakeholder meetings to address concerns.

Includes managing risks as part of Security Architecture development.

Weaknesses:

Focusing solely on creating business models and teaching stakeholders how to interpret them does not directly address cultural and positional concerns about job loss, skill development, and security.

Risk management is addressed as part of Security Architecture development but lacks broader integration into stakeholder requirements.

Conclusion: Incorrect, as it fails to systematically document stakeholder concerns and map them into requirements and architecture decisions.

Option B:

Strengths:

Highlights the importance of formal stakeholder identification and creating a Communication Plan.

Suggests addressing stakeholder concerns through communication and risk management.

Weaknesses:

Does not go into detail on analyzing stakeholder concerns, cultural positions, or specific requirements.

Lacks the inclusion of stakeholder feedback in architecture artifacts like the Architecture Vision or Requirements Specification, which are critical TOGAF outputs.

Conclusion: Incorrect, as it does not include a systematic and structured approach for stakeholder analysis and integration into architecture deliverables.

Option C:

Strengths:

Emphasizes conducting a thorough stakeholder analysis to document concerns, positions, and cultural factors, which aligns with TOGAF’s approach in Phase A (Architecture Vision).

Ensures stakeholder views and requirements are recorded in the Architecture Vision document and reflected in the Architecture Requirements Specification.

Includes continuous assessment and feedback, ensuring concerns are addressed and risks managed effectively.

Aligns with TOGAF's principle of involving stakeholders in architecture development to ensure alignment and success.

Weaknesses:

Could further detail how risk management is included across all phases, but this is implied through integration into the Architecture Requirements Specification.

Conclusion: Correct, as it provides a structured and detailed approach for addressing stakeholder concerns and managing risks within TOGAF’s framework.

Option D:

Strengths:

Suggests categorizing stakeholders into groups and creating models for each category.

Proposes arranging meetings to verify that concerns have been addressed.

Includes risk management as part of the process.

Weaknesses:

Dividing stakeholders into generic categories (e.g., corporate functions, project team) may not adequately capture specific cultural factors and concerns raised in the scenario.

Lacks integration of stakeholder feedback into architecture deliverables such as the Architecture Vision and Architecture Requirements Specification.

Conclusion: Incorrect, as it provides a generalized and less targeted approach to stakeholder concerns compared to Option C.

TOGAF References

Stakeholder Management (Phase A): TOGAF emphasizes analyzing stakeholders’ positions, concerns, and issues to shape architecture development and communication (TOGAF 9.2, Section 24.2).

Architecture Vision: Captures high-level requirements and stakeholder views to ensure alignment with business goals (TOGAF 9.2, Section 6.2).

Architecture Requirements Specification: Records detailed requirements, including those related to risk management, to guide the development of target architectures (TOGAF 9.2, Section 35.5).

Iterative Feedback: Regular assessments and feedback loops are critical to ensure stakeholder concerns are addressed effectively throughout the ADM cycle.

By selecting Option C, the approach adheres to TOGAF's principles of stakeholder analysis, communication, and integration of concerns into architecture development.

Questions 6

Please read this scenario prior to answering the question

You are working as an Enterprise Architect within a healthcare and life science company. The company is a

leading player in its industry, dedicated to transforming healthcare with new ideas and advancements. The

company has multiple divisions that cover different aspects of the business.

The company's Enterprise Architecture (EA) department has been operating for several years and has

mature, well-developed architecture governance and development processes following the TOGAF

Standard. In addition to the EA program, the company has a number of management frameworks in use.

The Architecture Board includes representatives from each division of the company.

Many of the company's rivals have begun utilizing Artificial Intelligence (Al) in their operations, and the

indications are that this will be transformative for healthcare delivery. This is something the EA department

has been interested in for a while, and they had recently submitted an architecture Change Request which

was approved. As a result, the CIO has approved a Request for Architecture Work to investigate the

implementation of Al in the company.

Areas for evaluation include:

How can staff use Al daily in their current role?

How Al can enhance access to care for patients, and how to make that experience seamless?

How Al can offer new workplace platforms and tools to increase efficiency?

Some of the top managers are worried about a change in the way of working, and if it will achieve the goals.

Many are not confident that the company's risk management processes are adequate for a company-wide

integration of generative Al. There are also questions from staff about whether enough specific guidelines

and polices have been put in place for responsible use of Al.

The Chief Information Officer (CIO) is the sponsor of the Enterprise Architecture program. The CIO has

actively encouraged architecting with agility within the EA department as her preferred approach for projects.

The CIO wants to know how to address these concerns and reduce risks.

Refer to the scenario

You have been tasked with starting the architecture development. How do you begin?

Based on the TOGAF standard which of the following is the best answer?

Options:

You recommend that an analysis of the stakeholders is undertaken. This will allow the architects to

define groups of partners (the stakeholders) who have common concerns and include development

of a Stakeholder Map. The concerns and relevant views should then be defined for each group and

recorded in the Architecture Vision document. To mitigate risk, you include a requirement that there

be progressive development of

You recommend that a Communications Plan be created to address the key stakeholders, that is the

most powerful and influential partners. This plan should include a report that summarizes the key

features of the architecture with respect to each location and reflects the stakeholders' requirements.

You will check with each key stakeholder that their concerns are being addressed. Risk mitigation

should be explicitly ad

You recommend that models be created for the Draft Business, Data, Application, and Technology

Architectures. These can be used to ensure that the system will be compliant with the local

regulations for each division. Together with the problem description, and requirements, this ensures

that all the necessary data and detail is addressed. A formal review should be held with the

stakeholders to verify that their conce

You recommend creation of a set of business models that can be applied uniformly across all Al-

related architecture projects. These should be developed in the portable format to ensure maximum

portability across the many tools used in the firm. Each architecture should then be defined based on

this fixed set of models. All concerned parties can then examine the models to ensure that their

needs have been addressed.<

Buy Now

Answer:

Explanation:

Key aspects of the scenario:

Objective:

Integrating Artificial Intelligence (AI) into healthcare delivery, with a focus on improving patient care, enhancing workplace efficiency, and enabling seamless experiences.

Challenges:

Stakeholder concerns about risk management, adaptability to change, and ensuring alignment with regulations and policies.

Addressing the concerns of staff and top management about AI integration and achieving the desired goals.

CIO's Perspective:

Encouraging an agile approach to architecture development.

Addressing risks and ensuring stakeholder concerns are managed.

Areas for Evaluation:

AI usage by staff and impact on workflows.

Patient experience enhancement via AI.

New workplace platforms and tools powered by AI.

Option Analysis:

Option 1: Analysis of stakeholders and development of a Stakeholder Map

Pros:

Stakeholder analysis is critical for identifying concerns, viewpoints, and requirements.

TOGAF emphasizes stakeholder engagement early in the process to mitigate risks and align expectations.

Developing a Stakeholder Map ensures clear alignment with their interests and creates a foundation for regular feedback loops.

Cons:

Does not explicitly address the creation of architecture models or policies upfront.

Option 2: Creation of a Communications Plan

Pros:

A communications plan fosters effective stakeholder engagement by addressing their concerns and ensuring transparent reporting.

Risk mitigation as part of communication aligns with TOGAF’s stakeholder management practices.

Cons:

This focuses more on communication mechanics rather than advancing architectural development directly.

Option 3: Models for Draft Business, Data, Application, and Technology Architectures

Pros:

Aligns with the Architecture Development Method (ADM), ensuring compliance with requirements and regulations.

Helps formalize stakeholder feedback by verifying their concerns against tangible models.

Cons:

Developing detailed models early on may delay immediate resolution of stakeholder concerns and risk mitigation.

Option 4: Set of reusable business models for AI-related projects

Pros:

Standardized models ensure consistency and portability across the organization’s AI-related efforts.

Cons:

Too narrow in focus for the initial architecture development phase; does not address risk management or stakeholder concerns adequately.

Recommended Answer:

Option 1: You recommend that an analysis of the stakeholders is undertaken.

Reasoning:

The scenario highlights stakeholder concerns about risks, adaptability, and compliance. Addressing these concerns requires stakeholder analysis as the first step.

A Stakeholder Map aligns with TOGAF’s emphasis on stakeholder engagement, providing a structured way to manage their concerns and expectations.

Identifying concerns early and integrating feedback into the Architecture Vision document ensures alignment with goals and smooth progress.

Option 1 sets the foundation for collaboration and risk management, making it the best fit for the current phase.

Questions 7

Please read this scenario prior to answering the question

You are working as an Enterprise Architect at a large supermarket. The company runs many retail

stores, as well as an online grocery shop. Many of the stores used to remain open 24/7, but the

number has decreased in recent years. Instead, they now focus on fulfilling online orders during

the night.

The company has a mature Enterprise Architecture (EA) practice and uses the TOGAF standard

for its architecture development method. The EA practice is involved in all aspects of the

business, with oversight provided by an Architecture Board with representatives from different

parts of the business. The EA program is sponsored by the Chief Information Officer (CIO).

Each store uses a standard method to track sales and inventory. This involves sending accurate

timely sales data to a central Al-based inventory management system that can predict demand,

adjust stock levels and automate reordering. The central inventory management system is housed

at the company's central data center.

The company has bought a major rival. The Chief Executive Officer believes that a merger will

enable growth through combined offerings and cost savings. The decision has been taken to fully

integrate the two organizations, including merging retail operations and systems. This means that

duplicated systems will be replaced with one standard retail management system. Also, the

company will reduce the number of applications that are used. The CIO expects significant

savings will be achieved by implementing these changes across the newly merged company.

One improvement that the rival has successfully implemented is the use of hand-held devices

within stores, for both customers and staff. This has increased both customer and staff employee

satisfaction due to the time savings this has brought. The CIO has given the go-ahead to roll out

the devices in all stores but has stated that training on how to use the hand-held devices should

be brief because there are a lot of employees, many of whom are part-time.

The Request for Architecture Work to oversee the merger has been approved. The project has

been scoped and you have been assigned to work on it. Your role includes managing the

architecture for the retail stores.

Refer to the scenario

You have been asked to confirm the most relevant architecture principles for the transformation.

Based on the TOGAF Standard, which of the following is the best answer?

[Note: The sequence of the principles listed in each answer does not matter. You should assume

the company follows the set of principles that are provided in the TOGAF Standard, ADM

Techniques, Architecture Principles chapter. You may need to refer to section 2.6 located in ADM

Techniques within the reference text to answer this question.]

Options:

Maximize Benefit to the Enterprise, Common Use Applications, Data is an Asset, Responsive Change Management, Technology Independence

Control Technical Diversity, Interoperability, Data is an Asset, Data is Shared, Business Continuity

Common Vocabulary and Data Definitions, Compliance with the Law, Requirements Based Change, Responsive Change Management, Data Security

Common Use Applications, Data is an Asset, Data is Accessible, Ease of Use, Business Continuity

Buy Now

Answer:

Explanation:

Key aspects of the scenario:

Business Objective:

A merger is happening to combine offerings, reduce costs, and achieve operational efficiency.

The goal includes fully integrating retail operations and systems, replacing duplicated systems, and reducing the number of applications used.

Technological Improvements:

A central AI-based inventory system is in place.

Hand-held devices for stores have improved customer and staff satisfaction and increased efficiency.

Scope of Architecture Work:

Integrating the merged systems.

Managing retail architecture to optimize operations.

TOGAF Alignment:

TOGAF principles aim to ensure the architecture supports business transformation effectively while aligning with governance and best practices.

Best answer analysis:

Option 1:

Maximize Benefit to the Enterprise: Aligns with the merger goals of cost reduction and efficiency.

Common Use Applications: Matches the goal to reduce duplicated systems.

Data is an Asset: Central AI system depends on accurate and reliable data.

Responsive Change Management: Necessary to support the transition and manage organizational impacts.

Technology Independence: Encourages selecting flexible, scalable solutions post-merger.

This option comprehensively aligns with the scenario.

Option 2:

Control Technical Diversity: Important but less emphasized than cost reduction and application unification.

Interoperability: Relevant, but less critical compared to principles addressing business value.

Data is an Asset: Relevant.

Data is Shared: Implied in centralized inventory but not directly stated.

Business Continuity: Important but not the main focus here.

This option partially fits but lacks emphasis on business outcomes.

Option 3:

Common Vocabulary and Data Definitions: Indirectly helpful but not central to the transformation.

Compliance with the Law: Always critical, but no explicit legal issues are mentioned.

Requirements-Based Change: General principle but not transformation-specific.

Responsive Change Management: Relevant.

Data Security: Important but not a central concern in the scenario.

This option focuses more on governance and less on merger goals.

Option 4:

Common Use Applications: Relevant to reducing duplicate systems.

Data is an Asset: Relevant.

Data is Accessible: Fits with AI system and handheld devices but is a subset of "Data is an Asset."

Ease of Use: Relevant to handheld devices but not a core transformation principle.

Business Continuity: Important but secondary to cost and efficiency.

This option focuses more on usability and accessibility rather than transformation objectives.

Questions 8

You are working as an Enterprise Architect within an Enterprise Architecture (EA) team at a large government agency with multiple divisions. The agency has a well-established EA practice and follows the TOGAF standard as its method for architecture development. The government has mandated that the agency prepare for an "AI-first" world.

The agency wants to determine the impact and role of AI in its future services. The CIO has approved a Request for Architecture Work to explore the use of AI in services. Some leaders are concerned about reliance on AI, security, and employees’ need to acquire new skills.

The EA team leader seeks suggestions on managing the risks associated with a new architecture for the AI-first project. Based on the TOGAF standard, which of the following is the best answer?

Options:

Conduct an analysis of stakeholders, documenting their concerns and recording them in the Architecture Vision document. Risks should be recorded in the Architecture Requirements Specification and reviewed regularly.

Identify key stakeholders and develop a Communication Plan that addresses their needs. Ensure the architecture addresses risk management and summarizes features of the architecture.

Separate stakeholders into groups and categorize them. Develop models for each group and verify that their concerns are addressed in Phase G, Implementation Governance.

Create an organization map to show the links between different agency parts. Hold a meeting to teach stakeholders to interpret the models. Manage risks as part of Security Architecture development.

Buy Now

Answer:

Explanation:

In the context of the TOGAF standard, stakeholder management and addressing stakeholder concerns are critical components, especially for high-impact initiatives like adopting an AI-first approach. Here’s why the selected answer aligns best with TOGAF principles and the scenario:

Stakeholder Analysis and Engagement:Conducting a stakeholder analysis is essential as it helps identify and document the concerns, issues, and cultural factors influencing each stakeholder group. This aligns with TOGAF’s emphasis on understanding and managing stakeholder concerns, particularly in the Preliminary and Architecture Vision phases of the ADM (Architecture Development Method). Since the scenario highlights diverse concerns about AI, understanding each group's unique perspective will help the EA team tailor the architecture to address these effectively.

Architecture Vision Document:By documenting these concerns in the Architecture Vision document, the EA team can provide a clear, high-level representation of how AI will be adopted, its benefits, and how it addresses specific stakeholder concerns. This is critical for communicating the intent and value of the AI-first approach in a way that aligns with the agency's strategic goals, including addressing apprehensions about job security, skill development, and cyber resilience.

Risk Management and Architecture Requirements Specification:TOGAF highlights the importance of identifying and managing risks early in the process. By documenting the requirements related to risk in the Architecture Requirements Specification, the EA team ensures that these concerns are formally integrated into the architecture and addressed throughout the ADM phases. Regular assessments and feedback loops will provide a mechanism for continual risk monitoring and adjustment as the AI-first initiative progresses.

Alignment with TOGAF’s ADM Phases:The approach specified aligns with TOGAF’s guidance on managing risk and stakeholder concerns during the early ADM phases, specifically Architecture Vision and Requirements Management. In these phases, the framework emphasizes identifying and addressing risks associated with stakeholders' concerns to build a resilient and widely accepted architecture.

Reference to TOGAF Stakeholder Management Techniques:TOGAF’s stakeholder management techniques underscore the importance of understanding and addressing stakeholder needs as a foundational step. This involves assessing the influence and interest of various stakeholders and integrating their views into architectural development, ensuring that the architecture aligns with both business goals and operational realities.

In conclusion, by conducting a thorough stakeholder analysis and documenting concerns in both the Architecture Vision and Architecture Requirements Specification, the EA team can ensure that stakeholder concerns are addressed, that the architecture supports AI adoption effectively, and that potential risks are managed proactively. This approach will foster acceptance among stakeholders and ensure that the architecture aligns with the agency’s strategic goals and risk management requirements as recommended by TOGAF.

Questions 9

Please read this scenario prior to answering the question

Your role is that of a consultant to the Lead Enterprise Architect in a multinational automotive manufacturer.

The company has a corporate strategy that focuses on electrification of its portfolio, and it has invested

heavily in a new shared car platform to use across all its brands. The company has four manufacturing

facilities, one in North America, two in Europe, and one in Asia.

A challenge that the company is facing is to scale up the number of vehicles coming off the production line to meet customer demand, while maintaining quality. There are significant supply chain shortages for electronic components, which are impacting production. In response to this the company has taken on new suppliers and has also taken design and production of the battery pack in-house.

The company has a mature Enterprise Architecture practice. The TOGAF standard is used for developing

the process and systems used to design, manufacture, and test the battery pack. The Chief Information

Officer and the Chief Operating Officer co-sponsor the Enterprise Architecture program.

As part of putting the new battery pack into production, adjustments to the assembly processes need to be made. A pilot project has been completed at a single location. The Chief Engineer, sponsor of the activity, and the Architecture Board have approved the plan for implementation and migration at each plant.

Draft Architecture Contracts have been developed that detail the work needed to implement and deploy the new processes for each location. The company mixes internal teams with a few third-party contractors at the locations. The Chief Engineer has expressed concern that the deployment will not be consistent and of acceptable quality.

Refer to the scenario

The Lead Enterprise Architect has asked you to review the draft Architecture Contracts and recommend the best approach to address the Chief Engineer's concern.

Based on the TOGAF Standard, which of the following is the best answer?

Options:

For changes requested by an internal team, you recommend a memorandum of understanding

between the Architecture Board and the implementation organization. For contracts issued to third-

party contractors, you recommend that it is a fully enforceable legal contract. You recommend that

the Architecture Board reviews all deviations from the Architecture Contract and considers whether to

grant a dispensation to allow the

For changes undertaken by internal teams, you recommend a memorandum of understanding

between the Architecture Board and the implementation organization. If a contract is issued to a

contractor, you recommend that it is a fully enforceable legal contract. If a deviation from the

Architecture Contract is found, you recommend that the Architecture Board grant a dispensation to

allow the implementation organization to c

You review the contracts ensuring that they address project objectives, effectiveness metrics,

acceptance criteria, and risk management. Third-party contracts must be legally enforceable. You

recommend a schedule of compliance reviews at key points in the implementation process. You

recommend that the Architecture Board reviews all deviations from the Architecture Contract and

considers whether to grant a dispensatio

You recommend that the Architecture Contracts be used to manage the architecture governance

processes across the locations. You recommend deployment of monitoring tools to assess the

performance of each completed battery pack at each location and develop change requirements if

necessary. If a deviation from the contract is detected, the Architecture Board should allow the

Architecture Contract to be modified meet the

Buy Now

Answer:

Explanation:

According to the TOGAF Standard, Version 9.2, an Architecture Contract is a joint agreement between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture1. It defines the scope, responsibilities, and governance of the architecture work, and ensures the alignment and compliance of the architecture with the business goals and objectives1.

In the scenario, the Lead Enterprise Architect has asked you to review the draft Architecture Contracts and recommend the best approach to address the Chief Engineer’s concern about the consistency and quality of the deployment of the new processes for the battery pack production at each location.

The best answer is C, because it follows the guidelines and best practices for defining and using Architecture Contracts as described in the TOGAF Standard, Version 9.22. It ensures that the contracts cover the essential aspects of the project objectives, effectiveness metrics, acceptance criteria, and risk management, and that they are legally enforceable for third-party contractors. It also recommends a schedule of compliance reviews at key points in the implementation process, and a mechanism for handling any deviations from the Architecture Contract, involving the Architecture Board and the possibility of granting a dispensation to allow the process to be customized for local needs.

The other options are not correct because they either23:

A. For changes requested by an internal team, you recommend a memorandum of understanding between the Architecture Board and the implementation organization. For contracts issued to third-party contractors, you recommend that it is a fully enforceable legal contract. You recommend that the Architecture Board reviews all deviations from the Architecture Contract and considers whether to grant a dispensation to allow the implementation organization to customize the process to meet their local needs.: This option does not address the need to review the contracts to ensure that they address the project objectives, effectiveness metrics, acceptance criteria, and risk management. It also does not recommend a schedule of compliance reviews at key points in the implementation process. Moreover, it suggests that a memorandum of understanding is sufficient for internal teams, which may not be legally binding or enforceable.

B. For changes undertaken by internal teams, you recommend a memorandum of understanding between the Architecture Board and the implementation organization. If a contract is issued to a contractor, you recommend that it is a fully enforceable legal contract. If a deviation from the Architecture Contract is found, you recommend that the Architecture Board grant a dispensation to allow the implementation organization to customize the process to meet their local needs.: This option has the same problems as option A, and also implies that the Architecture Board should always grant a dispensation for any deviation, which may not be appropriate or desirable in some cases.

D. You recommend that the Architecture Contracts be used to manage the architecture governance processes across the locations. You recommend deployment of monitoring tools to assess the performance of each completed battery pack at each location and develop change requirements if necessary. If a deviation from the contract is detected, the Architecture Board should allow the Architecture Contract to be modified meet the local needs. In such cases they should issue a new Request for Architecture Work.: This option does not address the need to review the contracts to ensure that they address the project objectives, effectiveness metrics, acceptance criteria, and risk management. It also does not recommend a schedule of compliance reviews at key points in the implementation process. Moreover, it suggests that the Architecture Board should always allow the Architecture Contract to be modified for any deviation, which may not be appropriate or desirable in some cases. It also implies that a new Request for Architecture Work should be issued for each deviation, which may not be necessary or feasible.

[:, 1: The TOGAF Standard, Version 9.2, Chapter 3: Definitions and Terminology, Section 3.1: Terms and Definitions, 2: The TOGAF Standard, Version 9.2, Chapter 43: Architecture Contracts, 3: The TOGAF Standard, Version 9.2, Chapter 44: Architecture Governance, , , ]

Exam Code: OGEA-102

Exam Name: TOGAF Enterprise Architecture Part 2 Exam (English)

Last Update: Jan 5, 2026

Questions: 33