The Open Group OGEA-102 Online Practice Questions and Exam Preparation

The Open Group OGEA-102 Online Questions & Answers

• Question 11:

  Please read this scenario prior to answering the question

  Your role is that of a consultant to the Lead Enterprise Architect to an international supplier of engineering services and automated manufacturing systems. It has three manufacturing plants where it assembles both standard and customized

  products for industrial production automation. Each of these plants has been operating its own planning and production scheduling systems, as well as applications and control systems that drive the automated production line.

  The Enterprise Architecture department has been operating for several years and has mature, well-developed architecture governance and development processes that are based on the TOGAF Standard. The CIO sponsors the Enterprise

  Architecture.

  During a recent management meeting, a senior Vice-President highlighted an interview where a competitor company's CIO is reported as saying that their production efficiency had been improved by replacing multiple planning and scheduling

  systems with a common Enterprise

  Resource Planning (ERP) system located in a central data center. Some discussion followed, with the CIO responding that the situations are not comparable, and the current architecture is already optimized.

  In response, the Architecture Board approved a Request for Architecture Work covering the investigations to determine if such an architecture transformation would lead to improvements in efficiency. You have been assigned to support the

  architecture team working on this project.

  A well-known concern of the plant managers is about the security and reliability of driving their planning and production scheduling from a remote centralized system. Any chosen system would also need to support the current supply chain

  network consisting of local partners at each of the plants.

  Refer to the scenario

  You have been asked to explain how you will initiate the architecture project.

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

  A. You would research vendor literature and conduct a series of briefings with vendors that are on the current approved supplier list. Based on the findings from the research, you would define a preliminary Architecture Vision including summary views, high-level requirements, and high-level definitions of the baseline and target environments from a business, information systems, and technology perspective. You would then use that to build consensus among the key stakeholders.
  B. You would conduct a pilot project that will enable vendors to demonstrate potential off-the-shelf solutions that address the concerns of the stakeholders. Running a pilot project will save time and money later in the process. Based on the findings of that pilot project, a complete set of requirements can then be developed that will drive the evolution of the architecture. Once the requirements are completed, a formal stakeholder review should be held, and permission sought to proceed to develop the target architecture.
  C. You would hold a series of interviews at each of the manufacturing plants using the business scenarios technique. This will allow you to understand the systems and integrations with local partners. You would use stakeholder analysis to identify key players in the engagement, and to understand their concerns. You will then identify and document the key high-level stakeholder requirements for the architecture. You will then generate high level definitions of the baseline and target architectures.
  D. You would develop baseline and target Architectures for each of the manufacturing plants, ensuring that the views corresponding to selected viewpoints address key concerns of the stakeholders. A business case, together with performance metrics and measures should be defined to ensure the architecture meets the business needs. A consolidated gap analysis between the architectures will then validate the approach and determine the capability increments needed to achieve the target state.
  C. You would hold a series of interviews at each of the manufacturing plants using the business scenarios technique. This will allow you to understand the systems and integrations with local partners. You would use stakeholder analysis to identify key players in the engagement, and to understand their concerns. You will then identify and document the key high-level stakeholder requirements for the architecture. You will then generate high level definitions of the baseline and target architectures.

  ---

  Explanation

  The best answer is

  C. You would hold a series of interviews at each of the manufacturing plants using the business scenarios technique. This will allow you to understand the systems and integrations with local partners. You would use stakeholder analysis to identify key players in the engagement, and to understand theirconcerns. You will then identify and document the key high-level stakeholder requirements for the architecture. You will then generate high level definitions of the baseline and target architectures.

  This answer is based on the TOGAF standard, which recommends the following steps to initiate the architecture project1: Establish the architecture project Identify stakeholders, concerns, and business requirements Confirm and elaborate business goals, business drivers, and constraints Evaluate business capabilities Assess readiness for business transformation Define scope Confirm and elaborate Architecture Principles, including business principles Develop Architecture Vision Define the Target Architecture value propositions and KPIs Identify the business transformation risks and mitigation activities Secure stakeholder and sponsor approval The answer C covers most of these steps, by using the business scenarios technique to elicit and validate the business requirements, goals, drivers, and constraints, as well as the current and future states of the architecture2.The answer C

  also uses stakeholder analysis to identify and engage the key stakeholders, and to address their concerns and expectations3.The answer C also generates high level definitions of the baseline and target architectures, which can be used to

  develop the Architecture Vision and the value propositions4.

  The other answers are not the best approach for architecture development, because:

  Answer A focuses on researching vendor literature and conducting briefings with vendors, which is not the best way to understand the business needs and the current situation of the enterprise. Answer A also defines a preliminary

  Architecture Vision without involving the stakeholders or validating the requirements, which may lead to misalignment and lack of consensus.

  Answer B conducts a pilot project that will enable vendors to demonstrate potential solutions, which is premature and costly at this stage of the architecture project. Answer B also does not address the stakeholder concerns or the current

  systems and integrations, which may result in gaps and risks. Answer B also develops the requirements after the pilot project, which may not reflect the actual business needs and goals.

  Answer D develops baseline and target architectures for each of the manufacturing plants, which may not consider the enterprise-wide perspective and the potential benefits of a common ERP system. Answer D also does not involve the

  stakeholders or address their concerns, which may result in resistance and conflict. Answer D also does not define the business case or the performance metrics, which are essential for demonstrating the value and feasibility of the

  architecture.

  References:1:The TOGAF Standard, Version 9.2 - Architecture Vision2:The TOGAF Standard, Version 9.2 - Business Scenarios3: [The TOGAF Standard, Version 9.2 - Stakeholder Management]4: [The TOGAF Standard, Version 9.2 Architecture Definition Document]

• Question 12:

  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?

  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.
  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.
  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 dispensation to allow the process to be customized for local needs.
  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 to implement a modification to the Architecture Definition.
  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 dispensation to allow the process to be customized for local needs.

  ---

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

  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 either:

  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.

  References:

  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

• Question 13:

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

  ---

  Explanation

  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 thedefinition 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]

• Question 14:

  Please read this scenario prior to answering the question

  You have been appointed as senior architect working for an autonomous driving technology development company. The mission of the company is to build an industry leading unified technology and software platform to support connected cars and autonomous driving.

  The company uses the TOGAF Standard as the basis for its Enterprise Architecture (EA) framework. Architecture development within the company 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 architecture to support strategy has been completed defining a long-range Target Architecture with a roadmap spanning five years. This has identified the need for a portfolio of projects over the next twoyears. The portfolio includes development of travel assistance systems using swarm data from vehicles on the road.

  The current phase of architecture development is focused on the Business Architecture which needs to support the core travel assistance services that the company plans to provide. The core services will manage and process the 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 poses an architecture challenge. The application portfolio needs to interact securely with various third-party cloud services, and V2X (Vehicle-to-Everything) service providers in many countries to be able to manage the data at scale. The security of V2X is a key concern for the stakeholders. Regulators have stated that the user's privacy be always protected, for example, so that the drivers' journey cannot be tracked or reconstructed by compiling data sent or received by the car.

  Refer to the scenario

  You have been asked to describe the risk and security considerations you would include in the current phase of the architecture development?

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

  A. You will focus on the relationship with the third parties required for the travel assistance systems and define a trust framework. This will describe the relationship with each party. Digital certificates are a key part of the framework and will be used to create trust between parties. You will monitor legal and regulatory changes across all the countries to keep the trust framework in compliance.
  B. You will perform a qualitative risk assessment for the data assets exchanged with partners. This will deliver a set of priorities, high to medium to low, based on identified threats, the likelihood of occurrence, and the impact if it did occur. Using the priorities, you would then develop a Business Risk Model which will detail the risk strategy including classifications to determine what mitigation is enough.
  C. You will focus on data quality as it is a key factor in risk management. You will identify the datasets that need to be safeguarded. For each dataset, you will assign ownership and responsibility for the quality of data needs. A security classification will be defined and applied to each dataset. The dataset owner will then be able to authorize processes that are trusted for a certain activity on the dataset under certain circumstances.
  D. You will create a security domain model so that assets with the same level can be managed under one security policy. Since data is being shared across partners, you will establish a security federation to include them. This would include contractual arrangements, and a definition of the responsibility areas for the data exchanged, as well as security implications. You would undertake a risk assessment determining risks relevant to specific data assets.
  D. You will create a security domain model so that assets with the same level can be managed under one security policy. Since data is being shared across partners, you will establish a security federation to include them. This would include contractual arrangements, and a definition of the responsibility areas for the data exchanged, as well as security implications. You would undertake a risk assessment determining risks relevant to specific data assets.

  ---

  Explanation

  A security domain model is a technique that can be used to define the security requirements and policies for the architecture. A security domain is a grouping of assets that share a common level of security and trust. A security policy is a set

  of rules and procedures that govern the access and protection of the assets within a security domain. A security domain model can help to identify the security domains, the assetswithin each domain, the security policies for each domain, and

  the relationships and dependencies between the domains

  Since the data is being shared across partners, a security federation is needed to establish a trust relationship and a common security framework among the different parties. A security federation is a collection of security domains that have

  agreed to interoperate under a set of shared security policies and standards. A security federation can enable secure data exchange and collaboration across organizational boundaries, while preserving the autonomy and privacy of each

  party. A security federation requires contractual arrangements, and a definition of the responsibility areas for the data exchanged, as well as security implications

  A risk assessment is a process that identifies, analyzes, and evaluates the risks that may affect the architecture. A risk assessment can help to determine the likelihood and impact of the threats and vulnerabilities that may compromise the

  security and privacy of the data assets. A risk assessment can also help to prioritize and mitigate the risks, and to monitor and review the risk situation

  Therefore, the best answer is D, because it describes the risk and security considerations that would be included in the current phase of the architecture development, which is focused on the Business Architecture. The answer covers the

  security domain model, the security federation, and the risk assessment techniques that are relevant to the scenario.

  References: 1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 35:

  Security Architecture and the ADM 2: The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 38: Security Architecture 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter

  32: Risk Management

• Question 15:

  You are working as an Enterprise Architect at a large company. The company runs many retail stores as well as an online marketplace that allows hundreds of brands to partner with the company. 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).

  Many of the stores remain open all day and night. Each store uses a standard method to track sales and inventory, which involves sending accurate, timely sales data to a central AI-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 acquired a major rival. The Chief Executive Officer (CEO) believes that the merger will enable growth through combined offerings and cost savings. The decision has been made to fully integrate the two organizations,

  including merging retail operations and systems. Duplicated systems will be replaced with one standard retail management system. The CIO expects significant savings from these changes across the newly merged company.

  The rival company has successfully implemented the use of hand-held devices within stores for both customers and staff, which has increased satisfaction due to time savings. The CIO has approved the rollout of these devices to all stores

  but has stated that training should be brief, as there are many part-time employees.

  You have been asked to confirm the most relevant architecture principles for this transformation. Based on the TOGAF Standard, which of the following is the best answer?

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

  ---

  Explanation

  In this scenario, the enterprise is undergoing significant transformation due to a merger and the adoption of new technology (hand-held devices). Several key principles from TOGAF's ADM Techniques--particularly those focused on promoting enterprise-wide standardization, adaptability, and data utilization--are pertinent here:

  Maximize Benefit to the Enterprise:This principle emphasizes that all architectural decisions should deliver maximum business value. Given that the company is integrating systems to cut costs and improve offerings, maximizing the benefit is crucial. Ensuring that the EA efforts align with enterprise- wide benefits supports the goal of optimizing costs and enhancing offerings, which aligns with the CEO' s vision for the merger.

  Common Use Applications:Standardizing applications across the merged entity will be essential to achieve cost savings and to simplify operations. The goal of reducing the number of applications fits with this principle, ensuring that reusable and widely adopted applications support business functions across the organization. Adopting this principle will also aid in harmonizing the systems from both organizations and avoiding unnecessary diversity.

  Data is an Asset:Data plays a central role in the company's operations, especially with the use of AI- driven inventory management and the integration of systems. Treating data as an asset is essential for reliable and accurate decision-making. This principle ensures that data is viewed as a critical enterprise resource and is managed with care, maintaining integrity, accuracy, and value.

  Responsive Change Management:The organization's ability to adapt quickly and effectively to changes, such as integrating new handheld devices and merging systems, is essential. This principle will facilitate the smooth transition required for integrating the new handheld devices and the merger- related system updates while minimizing disruption to store operations.

  Technology Independence:Since the enterprise will likely encounter varied technologies from the merger, it is crucial to maintain flexibility. This principle advocates for using technology solutions that are adaptable and not bound to a single vendor or specific technology. This ensures that the enterprise can integrate various technological components from both organizations and evolve with minimal constraints.

  These principles align well with TOGAF's broader recommendations for guiding architectural changes, as found in Section 2.6 of the TOGAF ADM Techniques. They ensure that the EA practice is aligned with business objectives while maintaining flexibility, data integrity, and a focus on enterprise-wide benefits. These guiding principles are critical for the successful execution of the integration and adoption of new technologies while achieving cost efficiencies and improving service delivery.

  For reference, TOGAF's ADM Techniques highlight the importance of architectural principles in guiding transformational initiatives, ensuring that decisions are made consistently across the enterprise. Eachprinciple supports organizational agility, system integration, and the efficient use of technology resources, all of which are vital for the enterprise's stated objectives.

• Question 16:

  Please read this scenario prior to answering the question

  You are the Chief Enterprise Architect at a large food service company specializing in sales to trade and wholesale, for example, restaurants and other food retailers.

  One of your company's competitors has launched a revolutionary product range and is running a very aggressive marketing campaign. Your company's resellers are successively announcing that they are not interested in your company's products and will sell your competitor's.

  The CEO has stated there must be significant change to address the situation. He has made it clear that new markets must be found for the company's products, and that the business needs to pivot, and address the retail market as well as the existing wholesale market.

  A consideration is the company's ability and willingness to change its business model, and if it is a temporary or permanent change. An additional risk factor is one of culture. The company has been used to a stable business with a reasonably well known and settled client base - all with its own local understandings and practices.

  The CEO is the sponsor of the EA program within the company. You have been engaged with the sales, logistics, production, and marketing teams, enabling the architecture activity to start. An Architecture Vision, Architecture Principles, and Requirements have all been agreed. As you move forward to develop a possible Target Architecture you have identified that some of the key stakeholders' preferences are incompatible. The incompatibilities are focused primarily on time-tomarket, cost savings, and the need to bring out a fully featured product range, but there are additional factors.

  Refer to the scenario

  You have been asked how you will address the incompatibilities between key stakeholder preferences.

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

  A. You would seek to understand value preferences and priorities of the stakeholders. You would develop alternative Target Architectures, highlighting the gaps between current state and the alternatives. You would consider combining features from one or more alternatives in collaboration with the stakeholders. A formal stakeholder review should then be held to decide which alternative is fit for purpose and should be moved forward with. You will then secure the funding required.
  B. You recommend that since the CEO has stated that the company must pivot, it is better to compromise on a full product range rather than time-to-market. You would develop just enough of the Target Architecture to demonstrate fitness of the proposed approach. You would limit the description to just where there is a gap between the current baseline. You would seek approval by the stakeholders to move forward with developing the Target Architecture in detail.
  C. You would use the Architecture Vision, Principles, and Requirements to define a set of criteria for alternatives and create a set of architecture views to illustrate the impact of the alternative Target Architectures. You would identify the impact on planned projects. You would understand the strengths and weaknesses of the alternatives. You would conduct a formal stakeholder review to decide which alternative to move forward with. You will determine the funding required.
  D. You would review the Stakeholder Map and ensure that you have addressed and represented the concerns of all department heads. You will involve them in resolving the incompatibilities. The Communications Plan should include a report that summarizes the key features of the architecture with and how incompatibilities were resolved to reflects the stakeholders' requirements. You will check with each key stakeholder they are satisfied with how the incompatibilities have been resolved.
  C. You would use the Architecture Vision, Principles, and Requirements to define a set of criteria for alternatives and create a set of architecture views to illustrate the impact of the alternative Target Architectures. You would identify the impact on planned projects. You would understand the strengths and weaknesses of the alternatives. You would conduct a formal stakeholder review to decide which alternative to move forward with. You will determine the funding required.

  ---

  Explanation

  According to the TOGAF standard, the Target Architecture is the description of a future state of the architecture being developed for an organization. It should be aligned with the Architecture Vision, Principles, and Requirements that have

  been agreed with the stakeholders. To address the incompatibilities between key stakeholder preferences, the TOGAF standard recommends creating and evaluating multiple alternative Target Architectures that meet different sets of criteria.

  These criteria should reflect the value preferences and priorities of the stakeholders, as well as the business drivers and objectives. The alternative Target Architectures should be illustrated using a set of architecture views that show the

  impact of each alternative on the business, data, application, and technology domains. The impact on planned projects should also be identified and analyzed. The strengths and weaknesses of each alternative should be understood and

  documented. A formal stakeholder review should then be conducted to decide which alternative is the most fit for purpose and should be moved forward with. The funding required for implementing the chosen alternative should also be

  determined and secured.

  References:

  The TOGAF Standard, Version 9.2 - Phase B: Business Architecture - The Open Group

  The TOGAF Standard, Version 9.2 - Phase C: Information Systems Architectures - The Open Group

  [The TOGAF Standard, Version 9.2 - Phase D: Technology Architecture - The Open Group]

  [The TOGAF Standard, Version 9.2 - Phase E: Opportunities and Solutions - The Open Group]

  [The TOGAF Standard, Version 9.2 - Phase F: Migration Planning - The Open Group]

• Question 17:

  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 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.
  D. You recommend that the set of required Solution Building Blocks be determined by identifying those which need to be developed and which need to be procured. Eliminate any duplicates. Group the remaining Solution Building Blocks together to create the work packages using a CRUD (create, read, update, delete) matrix. Rank the work packages and select the most cost-effective options for inclusion in a series of Transition Architectures. Schedule the roll out of the work packages to be sequential across the geographic regions.
  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.

  ---

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

  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

• Question 18:

  You are working as an Enterprise Architect within the Enterprise Architecture (EA) team at a healthcare and life sciences company. The EA team is developing a secure system for researchers to share clinical trial information easily across the organization and with external partners.

  Due to the highly sensitive nature of the information, each architecture domain must consider privacy and safety concerns. The healthcare division has been directed to minimize disruptions to clinical trials while introducing the new system gradually.

  How would you identify the work packages for introducing the new system? Based on the TOGAF standard, which of the following is the best answer?

  A. Use a Consolidated Gaps, Solutions, and Dependencies Matrix to create work packages and sequence them into Capability Increments. Document in a Transition Architecture State Evolution Table.
  B. Identify Solution Building Blocks for development or procurement, then use a CRUD matrix to rank and select the most cost-effective work packages. Schedule the rollout sequentially across regions.
  C. Use a Consolidated Gaps, Solutions, and Dependencies Matrix to classify each solution, group them into work packages, then regroup into Capability Increments. Document in an Architecture Definition Increments Table.
  D. Draw up an Implementation Factor Catalog to indicate actions and constraints. Use a Consolidated Gaps, Solutions, and Dependencies Matrix, then group similar activities into work packages and identify dependencies.
  C. Use a Consolidated Gaps, Solutions, and Dependencies Matrix to classify each solution, group them into work packages, then regroup into Capability Increments. Document in an Architecture Definition Increments Table.

  ---

  Explanation

  In the TOGAF framework, understanding and addressing stakeholder concerns is crucial, particularly for complex projects with high stakes like the AI-first initiative described in the scenario. This approach aligns well with TOGAF's ADM (Architecture Development Method) and its emphasis on effective stakeholder management and risk assessment. Here's why this is the best course of action:

  Stakeholder Analysis and Documentation:Conducting a stakeholder analysis is foundational in the early stages of any TOGAF project, particularly during the Preliminary and Architecture Vision phases. This process involves identifying the different stakeholders, understanding their positions, documenting their concerns, and considering any cultural factors that might influence their perspective on the AI-first initiative. Given the diverse concerns raised (such as job security, skill requirements, and cybersecurity), it's essential to have a clear understanding of each stakeholder group's priorities and fears.

  Recording Concerns in the Architecture Vision Document:The Architecture Vision phase in TOGAF focuses on defining the high-level scope and objectives of the architecture project. By documenting stakeholder concerns and the corresponding views in the Architecture Vision document, the EA team ensures that these concerns are transparently acknowledged and addressed as part of the strategic direction. This step not only aligns with TOGAF best practices but also helps in building stakeholder buy-in and trust.

  Architecture Requirements Specification and Risk Management:Risk management is a key aspect of TOGAF's ADM, particularly in the Requirements Management and Implementation Governance phases. Documenting the requirements for addressing specific risks in theArchitecture Requirements Specification provides a structured way to ensure that identified risks are acknowledged and managed throughout the transformation. Regular assessments and feedback loops ensure ongoing alignment and adaptability to emerging risks, which is particularly important given the dynamic nature of AI and its associated challenges.

  Alignment with TOGAF ADM Phases:This approach follows the prescribed flow of TOGAF's ADM, starting with stakeholder engagement in the Preliminary and Architecture Vision phases and progressing to risk assessment in the Requirements Management phase. By maintaining a focus on stakeholder needs and formalizing these into architecture requirements, the EA team can ensure that the architecture not only meets business objectives but also mitigates stakeholder concerns.

  TOGAF Reference on Stakeholder Management Techniques:TOGAF places significant emphasis on managing stakeholder concerns through its stakeholder management techniques, which highlight the need to systematically identify, analyze, and address the concerns of all involved parties. This practice helps ensure that the architecture is viable and accepted across the organization.

  By conducting a thorough stakeholder analysis and integrating the findings into both the Architecture Vision and the Architecture Requirements Specification, the EA team can proactively address stakeholder concerns, manage risks, and align the AI-first initiative with the agency's strategic objectives. This approach is consistent with TOGAF's guidance and provides a structured framework for addressing both business and technical challenges in the context of an AI-first transformation.