The Open Group OGEA-102 TOGAF Enterprise Architecture Part 2 Exam (English) Exam Practice Test

Page: 1 / 3
Total 34 questions

Get OGEA-102 Full Access Download OGEA-102 PDF

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

Question 1

Please read this scenario prior to answering the question

You are employed as an Enterprise Architect in a team at a large company. The

company sells luxury food and drinks in more than 10,000 stores worldwide. The

company is a leader in using technology to connect with its customers. This includes

online ordering, mobile apps, and rewards programs. The company is also famous for

bringing new ideas to the market, like ordering through apps, using Al to suggest

personalized options, self-service pickup stations, and changing prices based on

demand.

The stores are open every day. They send timely sales data to a central system that

manages inventory. This system can predict what products are needed, adjust how

much stock there is, and order more stock automatically. The stores and the main

inventory system work directly with the mobile apps, allowing orders to be made

online. The central inventory system is located at the company ' s main data center.

The company will merge with a major competitor. This competitor has a synergistic

business. Leaders from both companies have told shareholders that the merger will

happen fast. There will be minimal impact for customers. All stores will keep the

current brand names. They will combine their systems, choosing the best ones to use.

This means their store management and back-office systems will become one. They

will stop using duplicate systems and use one main system to manage the stores.

They will also cut down on the number of back-office applications they use.

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

Stakeholders, concerns, and business requirements have been identified. The

stakeholders have made it clear that they expect to continue to be able to innovate

quickly, and that changes should not restrict that capability. The scope of what is

inside and what is outside the architecture efforts has been confirmed. The next step

is to revisit and review the Architecture Principles, as they form part of the constraints

on architecture work.

Business Continuity is essential given that the business depends on real-time

ordering and automated inventory management. During the systems integration,

maintaining service for customers and inventory operations must be prioritized

Refer to the scenario

You have been asked to identify the most relevant Architecture Principles for the

merger besides Business Continuity.

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

[Note: You should assume that the company follows the example set of Architecture

Principles provided in the TOGAF standard, ADM Techniques, Architecture Principles

chapter.]

Options:

Control Technical Diversity will help by standardizing technology platforms aspart of the integration process. This will be vital for standardizing the appintegration for digital orders with the back-office systems, and will reducecomplexity and costs during integration. Data Trustee will establish owners tomanage the shared data across the company, thereby assuring data quality.Ease-of-Use is needed to make sure that new user interfaces fo

Primacy of Principles will make sure that the same principles apply to bothorganizations of the newly merged operation, creating consistency acrosslocations. Data as an Asset is critical. Since you ' re maintaining separate mobileapps but consolidating back-end systems, treating data as an asset becomesessential. This principle helps ensure that customer data, and inventoryinformation from both brands are properly integrated and managed.Tec

Compliance with the Law makes sure that all company activities comply withrelevant laws and regulations. This principle provides the foundation forensuring the merger meets all legal requirements. Requirements-BasedChange will make sure that when combining systems, changes to applicationsand technology are only made if required by business needs. ResponsiveChange Management focuses on the speed needed to achieve the goals setby the leaders

Service orientation will speed up the merger and make it easier to integratesystems while maintaining business operations. Maximize Benefit to theEnterprise will make sure that merger decisions prioritize the overall benefit tothe combined company. Common Use Applications across the mergedcompany is preferred over the use of similar or duplicative applications forcertain parts of the company. This help supports the goal of merging back-offi

Answer:

Explanation:

You are asked to identify the most relevant Architecture Principles, besides Business Continuity, that apply to a rapid merger, where:

Back-office and store management systems will be consolidated

Duplicate applications will be eliminated

Innovation must remain fast

Customer experience must remain uninterrupted

Combined enterprise value is the priority

TOGAF’s example Architecture Principles include four main categories:

Business Principles

Data Principles

Application Principles

Technology Principles

Option D contains the principles that best support the specific needs of the merger as described.

✔ Why Option D is correct

1. Service Orientation (Business Principle)

This principle states that architecture should be organized around services, enabling flexibility, loose coupling, and ease of integration.

For the merger:

Integrating two companies’ store systems, mobile apps, and inventory platforms requires modular, interoperable services.

Service orientation directly supports the requirement that innovation must not slow down.

It allows systems to be merged with minimal disruption.

This principle supports fast integration + ongoing innovation — exactly what stakeholders demand.

2. Maximize Benefit to the Enterprise (Business Principle)

This principle ensures decisions are made from an enterprise-wide (not departmental or local) perspective.

In the scenario:

Two companies are merging.

Decisions must prioritize combined enterprise value, not local optimizations by either company.

System consolidation and elimination of duplicates requires an enterprise-first mindset.

This principle aligns perfectly with a merger that aims to unify operations and reduce redundancy.

3. Common Use Applications (Application Principle)

This is one of the MOST relevant principles in any merger.

TOGAF defines this principle as:

“Applications should be shared across the enterprise and not duplicated.”

In the scenario:

Back-office systems and store management tools must be consolidated.

Duplicate applications are explicitly to be reduced.

One main system will be used across stores.

This principle directly matches the merger ' s objectives.

✔ Summary

Option D contains the three principles that best support:

A major merger

System consolidation

Reduction of duplication

Enterprise-wide benefit

Flexible, service-oriented integration

Continued innovation

Therefore, Option D is the most appropriate selection according to TOGAF’s example Architecture Principles.

Question 2

You are working as an Enterprise Architect within an Enterprise Architecture (EA) team at a multinational energy company. The company is committed to becoming a net-zero emissions energy business by 2050. To achieve this, the company is focusing on shifting to renewable energy production and adopting eco-friendly practices.

The EA team, which reports to the Chief Technical Officer (CTO), has been tasked with overseeing the transformation to make the company more effective through acquisitions. The company plans to fully integrate these acquisitions, including merging operations and systems.

To address the integration challenges, the EA team leader wants to know how to manage risks and ensure that the company succeeds with the proposed changes. Based on the TOGAF Standard, which of the following is the best answer?

Options:

The EA team should create a Business Scenario to fully describe the business problem that is being addressed by the transformation. Once requirements are identified, they should be evaluated in terms of risks. Any residual risks should be escalated to the Architecture Board.

The EA team should develop Business Architecture views that demonstrate how stakeholder concerns are addressed and assess each factor for readiness, urgency, and degree of difficulty.

The EA team should evaluate the company’s readiness for change by identifying factors that will impact the transformation. These factors will be used to determine initial risks associated with the initiative.

The EA team should document the risks associated with the transformation in an Implementation Factor Catalog to inform decisions during implementation and deployment.

Answer:

Explanation:

In TOGAF, creating a Business Scenario is a foundational step in defining and understanding the business problem, especially for complex transformations involving multiple stakeholders and systems, such as in this scenario. This method aligns with Phase A (Architecture Vision) of the TOGAF Architecture Development Method (ADM). Here’s why this approach is the most effective:

Understanding Business Requirements:A Business Scenario provides a structured way to capture and analyze the business requirements, stakeholder concerns, and the contextual elements related to the problem. In this scenario, the company faces challenges in integrating newly acquired companies with existing operations, which includes complex stakeholder concerns across different functional areas. Developing a Business Scenario allows the EA team to break down these complexities into identifiable and manageable parts.

Risk Evaluation and Management:By using the Business Scenario approach, the EA team can not only define the requirements but also assess associated risks systematically. TOGAF emphasizes the importance of risk management through identifying potential risks, evaluating their impact, and defining strategies for handling these risks. The process includes assessing how risks can be avoided, transferred, or reduced—a necessary step in large-scale transformations to ensure that risks are proactively managed.

Residual Risks and Governance:Any risks that cannot be fully resolved should be identified as residual risks and escalated to the Architecture Board, which is aligned with TOGAF’s governance approach. The Architecture Board’s role in TOGAF is to provide oversight and make critical decisions on risks that exceed the control of the EA team. This ensures that unresolved risks are managed at the appropriate level of the organization.

Alignment with TOGAF ADM Phases:The Business Scenario approach directly aligns with the Preliminary and Architecture Vision phases of the TOGAF ADM, which focuses on establishing a baseline understanding of the business context and the strategic transformation required. The detailed understanding of requirements, stakeholder concerns, and risks identified here will guide the subsequent phases of the ADM, including Business Architecture and Information Systems Architecture.

TOGAF Reference (Section 2.6, ADM Techniques):TOGAF provides guidelines on the creation of Business Scenarios as part of ADM Techniques, highlighting the importance of defining a business problem comprehensively to ensure successful transformation. This method includes identification of stakeholders, business requirements, and associated risks, which aligns well with the company ' s need for strategic and systematic integration of new business units.

By utilizing a Business Scenario, the EA team ensures that all aspects of the transformation are well understood, risks are identified early, and residual risks are managed effectively, aligning with the company ' s strategic objectives and the TOGAF framework’s guidance on risk management and stakeholder alignment.

Question 3

Scenario:

You are working as an Enterprise Architect within a company providing legal services. The company operates in many countries and has a complicated structure. Every office must follow the local regulations in their country.

The company’s Enterprise Architecture (EA) department has been operating for several years and has mature, well-developed architecture governance and development processes based on the TOGAF standard. In addition to the EA program, the company has several management frameworks, including business planning, project/portfolio management, and operations management. The Architecture Board includes representatives from all parts of the company.

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 the preferred approach for projects. The CIO has given approval for a Request for Architecture Work to explore the adoption of an AI-powered system for managing legal cases and financial processes.

Senior management has become more concerned about business performance, especially with the advancements in Artificial Intelligence (AI). Many of the company’s competitors have started using AI to assist with legal strategies, streamline processes, and boost productivity. One of the most important benefits AI has for the business is its ability to increase accuracy and minimize mistakes.

Some of the top managers are worried about a change in the way of working, and if it will achieve the business goals. Their staff also fear that management will use the AI system to measure their performance. The CIO wants to know how to address these concerns and reduce risks.

The new system is expected to guide legal professionals and analysts on which tasks to focus on. The main goals are to improve productivity and make better use of staff. In addition, the CIO hopes these changes will lead to higher customer satisfaction.

Refer to the scenario:

You have been asked to respond to the Chief Information Officer (CIO) recommending an approach that would enable the development of an architecture that addresses the concerns of the top managers and the multiple branches in different parts of the company.

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

Options:

You recommend that models be created for each of the Business, Application, and Technology architectures. These can be used to ensure that the system will be compliant with the local regulations for each operating entity. This ensures that all necessary data and detail is addressed. A formal review should be held with the stakeholders to verify that their concerns have been properly addressed by the models.

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 reduce risk, you include a requirement that there be progressive development of the target architecture t

You recommend creation of a set of business models that can be applied uniformly across all AI-related architecture projects. These should be developed in a 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 stakeholders can then examine the models to ensure that their needs have been addressed.

You recommend that a Communications Plan be created to address the key stakeholders, particularly influential partners. This plan should include a report summarizing the key features of the architecture with respect to each location and reflect the stakeholders’ requirements. You will check with each key stakeholder that their concerns have been addressed. Risk mitigation should be explicitly addressed as a component of the architecture be

Answer:

Explanation:

The correct answer is B, as it aligns with TOGAF ' s stakeholder management approach, ensuring that stakeholder concerns are captured and addressed iteratively throughout the architecture development process.

Analysis of the Correct Answer (Option B):

Stakeholder Analysis and Mapping

The scenario highlights that top managers and staff are worried about the changes AI will bring.

TOGAF recommends stakeholder analysis early in the ADM process to ensure that concerns, expectations, and risks are documented.

Creating a Stakeholder Map groups stakeholders by common concerns, allowing architects to develop tailored viewpoints.

Recording Concerns in the Architecture Vision Document

The Architecture Vision (ADM Phase A) serves as a high-level guiding document.

Capturing stakeholder concerns in the Vision document ensures alignment between business goals and technology implementation.

Iterative Development and Regular Feedback

The scenario describes an AI-powered system with major business impacts, so incremental validation is necessary.

TOGAF emphasizes progressive development to manage risk and validate requirements continuously.

Regular feedback loops help mitigate resistance from top managers and staff.

Why Other Options Are Incorrect?

Option A: Creating Models for Business, Application, and Technology Architectures

Incorrect because while compliance is important, it does not address stakeholder concerns directly.

The scenario is about ensuring buy-in from top managers and employees, not just regulatory compliance.

Option C: Using Uniform Business Models Across AI Projects

Incorrect because a one-size-fits-all model does not allow for regional and functional differences within the company.

The scenario emphasizes the need to address specific concerns of top managers and different locations, which requires stakeholder-specific customization.

Option D: Creating a Communications Plan

Incorrect because communication alone does not resolve stakeholder concerns.

While communication is useful, the architecture development process should include stakeholder engagement and progressive validation, not just reporting.

[References:, TOGAF Standard, ADM Phase A – Architecture Vision, TOGAF Standard, Stakeholder Management (ADM Guidelines and Techniques), TOGAF Enterprise Architecture Principles – The Open Group, , , , , , ]

Question 4

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?

Options:

You would research vendor literature and conduct a series of briefings with vendorsthat are on the current approved supplier list. Based on the findings from theresearch, you would define a preliminary Architecture Vision including summaryviews, high-level requirements, and high-level definitions of the baseline and targetenvironments from a business, information systems, and technology perspective. Youwould then use that to build consensus

You would conduct a pilot project that will enable vendors to demonstrate potentialoff-the-shelf solutions that address the concerns of the stakeholders. Running a pilotproject will save time and money later in the process. Based on the findings of thatpilot project, a complete set of requirements can then be developed that will drive theevolution of the architecture. Once the requirements are completed, a formalstakeholder review should be

You would hold a series of interviews at each of the manufacturing plants using thebusiness scenarios technique. This will allow you to understand the systems andintegrations with local partners. You would use stakeholder analysis to identify keyplayers in the engagement, and to understand their concerns. You will then identifyand document the key high-level stakeholder requirements for the architecture. Youwill then generate high level def

You would develop baseline and target Architectures for each of the manufacturingplants, ensuring that the views corresponding to selected viewpoints address keyconcerns of the stakeholders. A business case, together with performance metricsand measures should be defined to ensure the architecture meets the businessneeds. A consolidated gap analysis between the architectures will then validate theapproach and determine the capability increm

Answer:

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

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.

1: The TOGAF Standard, Version 9.2 - Architecture Vision 2: The TOGAF Standard, Version 9.2 - Business Scenarios 3: [The TOGAF Standard, Version 9.2 - Stakeholder Management] 4: [The TOGAF Standard, Version 9.2 - Architecture Definition Document]

Question 5

Please read this scenario prior to answering the question

You have been appointed as Chief Enterprise Architect (CEA). reporting to the Chief Technical Officer (CTO), of a company established as a separate operating entity by a major automotive manufacturer. The mission of the company is to build a new industry leading unified technology and software platform for electric vehicles.

The company uses the TOGAF Standard as the basis for its Enterprise Architecture (EA) framework, and architecture development follows the purpose-based EA Capability model as described in the TOGAF Series Guide: A Practitioners ' Approach to Developing Enterprise Architecture Following the TOGAF® ADM.

An end-to-end Target Architecture has been completed with a roadmap for change over a five-year period. The new platform will be a cross-functional effort between hardware and software teams, with significant changes over the old platform. It is expected to be developed in several stages over three years. The EA team has inherited the architecture for the previous generation hardware and software automotive platform, some of which can be carried over to the new unified platform. The EA team has started to define the new platform, including defining which parts of the architecture to carry forward.

Enough of the Business Architecture has been defined, so that work can commence on the Information Systems and Technology Architectures. Those need to be defined to support the core business services that the company plans to provide. The core services will feature an innovative approach with swarm data generated by vehicles, paving the way for autonomous driving in the future.

The presentation and access to different variations of data that the company plans to offer through its platform pose an architecture challenge. The application portfolio and supporting infrastructure need to interact with various existing cloud services and data-

Refer to the scenario

You have been asked what approach should be taken to determine and organize the work to deliver the requested architectures?

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

Options:

You would look outside the enterprise to research data models and application portfolios of leading big data businesses. You would develop just enough applications, data, and technology architecture to identify options. For each project this should include identification of candidate architecture and solution building blocks. You will identify solution providers, perform a readiness assessment, and assess the viability and fitness of the so

You would refer to the end-to-end Target Architecture for guidance and direction. The first objective should be to identify projects, dependencies and synergies, then prioritize before initiating the projects. You will develop high-level architecture descriptions. For each project you would estimate effort size, identify reference architectures, and candidate building blocks. You will identify the resource needs considering cost and value.

You will revisit ADM Phase A. identifying the stakeholders and creating a new Architecture Vision. You will update the Stakeholder map produced for the strategic architecture so it reflects the stakeholders who are now the most relevant to the projects that are to be developed. You would then ask the CTO to make some decisions about the Architecture Roadmap, and update the Implementation and Migration Plan to reflect the decisions.

You will research leading data businesses, developing high-level Target Data, Application and Technology Architectures. You would review the Architecture Vision in order to estimate the level of detail, time, and breadth of the ADM cycle phases that will be needed to develop the architecture. You will identify and cost major work packages, and then develop an Architecture Roadmap. You would then seek approval by the Architecture Board and i

Answer:

Explanation:

The Target Architecture is a description of the future state of the architecture that addresses the business goals and drivers, and satisfies the stakeholder requirements and concerns. The Target Architecture is developed through the Architecture Development Method (ADM), which is the core process of the TOGAF standard that guides the development and management of the enterprise architecture. The Target Architecture is typically divided into four domains: Business, Data, Application, and Technology. The Target Architecture also includes a roadmap for change, which defines the Transition Architectures, the Capability Increments, and the work packages that enable the transition from the Baseline Architecture to the Target Architecture12

The best answer is B, because it describes the approach that should be taken to determine and organize the work to deliver the requested architectures, which are the Information Systems and Technology Architectures. The answer covers the following steps:

Refer to the end-to-end Target Architecture for guidance and direction. The end-to-end Target Architecture provides the overall vision, scope, and objectives of the architecture work, and the alignment with the business strategy and goals. The end-to-end Target Architecture also provides the high-level definitions and principles for the four architecture domains, and the roadmap for change that outlines the major milestones and deliverables.

Identify projects, dependencies and synergies, then prioritize before initiating the projects. Projects are the units of work that implement the architecture work packages, which are the sets of actions or tasks that are required to implement a specific part of the architecture. Dependencies are the relationships and constraints that affect the order or priority of the projects, such as logical, temporal, or resource dependencies. Synergies are the benefits or advantages that result from the combination or coordination of the projects, such as cost savings, efficiency gains, or innovation opportunities. Prioritization is the process of ranking the projects according to their importance, urgency, or value, and assigning resources and schedules accordingly.

Develop high-level architecture descriptions. High-level architecture descriptions are the outputs of the architecture development phases (B, C, and D) of the ADM cycle, which describe the Business, Data, Application, and Technology Architectures in terms of the Architecture Building Blocks (ABBs) and the Solution Building Blocks (SBBs), which are reusable components of business, IT, or architectural capability. High-level architecture descriptions also include the Architecture Views, which are representations of the system of interest from the perspective of one or more stakeholders and their concerns.

For each project, estimate effort size, identify reference architectures, and candidate building blocks. Effort size is the measure of the amount of work, time, or resources required to complete a project. Effort size can be estimated using various techniques, such as analogy, expert judgment, parametric, or bottom-up. Reference architectures are standardized architectures that provide a common framework and vocabulary for a specific domain or industry. Reference architectures can be used as a source of best practices, patterns, and models for the architecture development. Candidate building blocks are the potential ABBs or SBBs that can be used to implement the architecture. Candidate building blocks can be identified from the Architecture Repository, which is a collection of architecture assets, such as models, patterns, principles, standards, and guidelines.

Identify the resource needs considering cost and value. Resource needs are the specifications and criteria that define the acceptable level and quality of the resources required to complete the project, such as human, financial, physical, or technological resources. Resource needs can be identified by analyzing the scope, complexity, and dependencies of the project, and the availability, capability, and suitability of the resources. Cost and value are the factors that influence the allocation and utilization of the resources, such as the budget, the return on investment, the benefits, or the risks.

Document options, risks, and controls to enable viability analysis and trade-off with the stakeholders. Options are the alternative ways of achieving the project objectives, such as different solutions, technologies, vendors, or approaches. Risks are the effects of uncertainty on the project objectives, such as threats or opportunities. Controls are the measures or actions that are taken to prevent, reduce, or mitigate the risks, such as policies, procedures, or standards. Viability analysis is the process of evaluating and comparing the options, risks, and controls, and determining the feasibility, suitability, and desirability of each option. Trade-off is the decision outcome that balances and reconciles the multiple, often conflicting, requirements and concerns of the stakeholders, and ensures alignment with the Architecture Vision and the Architecture Principles.

1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 5: Introduction to the ADM 2: The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 36: Building Blocks : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 19: Phase B: Business Architecture : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 20: Phase C: Information Systems Architectures : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 21: Phase F: Migration Planning : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 23: Architecture Principles : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 30: Trade-Off Analysis : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 46: Tools for Architecture Development : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 47: Architecture Board : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 48: Architecture Compliance : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 49: Architecture Contract : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50: Architecture Governance : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 51: Architecture Maturity Models : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 52: Architecture Skills Framework

Question 6

Please read this scenario prior to answering the question

You are working as the Chief Enterprise Architect within a law firm specializing in personal injury cases. Many of the firm ' s competitors have improved their litigation strategies, and efficiency by streamlining their processes using Artificial Intelligence {Al).

The CIO has approved a Request for Architecture Work to examine the use of Machine Learning in defining a new Al-driven litigation and finance process for the firm. This process would instruct the lawyers and analysts as to what tasks and portfolio they should work on. The key objectives are to increase task profitability, maximize staff utilization, and increase individual profitability.

The CIO has emphasized that the architecture should enable the fast implementation of continuous Machine Learning. The solution will need to be constantly measured for delivered value and be quickly iterated to success.

Some of the partners have expressed concerns about letting the Al make the decisions, others about the risks associated with use of it for the type of service they deliver. The CIO wants to know if these concerns can be addressed, and how risks will be covered by a new architecture enabling Al and Machine Learning.

Refer to the scenario

You have been asked to respond to the CIO recommending an approach that would enable the development of an architecture that addresses the concerns of the CIO and the concerns of the partners.

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

Options:

You recommend that a Communications Plan be created to address the key stakeholders, the most powerful and influential partners. This plan should include a report that summarizes the key features of the architecture reflecting their requirements. You will check with each key stakeholder that their concerns are being addressed. Risk mitigation and agility will be explicitly addressed as a component of the architecture being developed.

You recommend that an analysis of the stakeholders is undertaken resulting in documenting the stakeholders and their concerns in a Stakeholder Map. The concerns and relevant views should then be defined for each group and recorded in the Architecture Vision document. The requirements will include risk mitigation through regular assessments. This will also allow a supervised agile implementation of the continuous Machine Learning.

You recommend that all possible models be created for each candidate architecture that will enable the Al and Machine Learning solution. This ensures that all the necessary data and detail is addressed. A formal review should be held with the stakeholders to verify that their concerns have been properly addressed by the models. Agility will be considered during Phase G Implementation Governance.

You recommend creation of a set of business models that can be applied uniformly across all architecture projects. The stakeholders will be trained to understand the business models to ensure they can see that their concerns are being addressed. Risk will be addressed once the Security Architecture is developed, which will happen later to avoid slowing down the agility required by the CIO.

Answer:

Explanation:

A Stakeholder Map is a technique that can be used to identify and classify the stakeholders of the architecture work, and to document their key interests, requirements, and concerns. A stakeholder is any person, group, or organization that has a stake in the outcome of the architecture work, such as the sponsor, the client, the users, the suppliers, the regulators, or the competitors. A Stakeholder Map can help to understand the needs and expectations of the stakeholders, and to communicate and engage with them effectively1

The steps for creating a Stakeholder Map are:

Identify the stakeholders of the architecture work, using various sources and methods, such as interviews, surveys, workshops, or existing documents.

Classify the stakeholders according to their roles, responsibilities, and relationships, using various criteria and dimensions, such as power, influence, interest, attitude, or impact.

Define the concerns and relevant views for each stakeholder group, using various techniques, such as business scenarios, use cases, or value propositions. A concern is a key interest or issue that is relevant to the stakeholder, such as a goal, a problem, a need, or a risk. A view is a representation of the system of interest from the perspective of one or more stakeholders and their concerns.

Record the stakeholders and their concerns in a Stakeholder Map, which shows the mapping between the stakeholder groups, the concerns, and the views. The Stakeholder Map also shows the dependencies, assumptions, and issues related to each stakeholder and concern.

Therefore, the best answer is B, because it recommends the approach that would enable the development of an architecture that addresses the concerns of the CIO and the partners, using the Stakeholder Map technique. The answer covers the following aspects:

An analysis of the stakeholders is undertaken, which involves identifying, classifying, and defining the stakeholders and their concerns.

The stakeholders and their concerns are documented in a Stakeholder Map, which provides a clear and comprehensive picture of the stakeholder landscape and their interests.

The concerns and relevant views are recorded in the Architecture Vision document, which is the output of Phase A: Architecture Vision of the Architecture Development Method (ADM), which is the core process of the TOGAF standard that guides the development and management of the enterprise architecture. The Architecture Vision defines the scope and approach of the architecture work, and establishes the business goals and drivers that motivate the architecture work. The Architecture Vision also involves obtaining the approval and commitment of the sponsors and other key stakeholders, and initiating the Architecture Governance process2

The requirements include risk mitigation through regular assessments, which involves identifying, analyzing, and evaluating the risks that may affect the architecture, and determining the appropriate measures or actions to prevent, reduce, or mitigate the risks. Risk mitigation can also involve monitoring and reviewing the risk situation, and communicating and reporting the risk status and actions3

This approach also allows a supervised agile implementation of the continuous Machine Learning, which involves applying agile principles and practices to the architecture development and implementation, such as iterative and incremental delivery, frequent feedback, collaboration, and adaptation. A supervised agile implementation can help to ensure the quality, value, and alignment of the architecture, and to respond to the changing needs and expectations of the stakeholders.

1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 24: Stakeholder Management 2: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 32: Risk Management : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 29: Applying Iteration to the ADM

Question 7

Scenario

You are working as an Enterprise Architect within an Enterprise Architecture (EA) team at a global company that sells consumer products. The company produces many products that buyers use and enjoy.

The company has announced a major change to its products that will occur over a four-year period. This change includes the introduction of digital products and services. An architecture to support this strategy has been finished, along with a roadmap for a set of projects to implement this significant change. This will be a cross-functional effort between the product design and software teams. It is planned to be developed in phases.

The company faces a challenge in presenting and providing access to different services through its products and digital platforms while ensuring compliance with data privacy laws. In some countries and regions, the data residency requirements mean that the company has to store certain data within the region where it is collected. As a result, the company’s application portfolio and infrastructure must connect with various cloud services and data repositories in different countries.

The EA team has inherited the architecture used by the current products, some of which can be carried over to the new products. The EA team has started to define which parts of the architecture to carry forward. Enough of the Business Architecture has been defined so that work can commence on the Information Systems and Technology Architectures. Those architectures need to be defined to support the key digital services that the company plans to provide.

The company uses the TOGAF Standard as the foundation for its Enterprise Architecture framework, and architecture development follows the purpose-based EA Capability model outlined in the TOGAF Series Guide: A Practitioner’s Approach to Developing Enterprise Architecture Following the TOGAF ADM. The EA team reports to the Chief Information Officer (CIO), who oversees the program.

You have been asked how to decide and organize the work to deliver the requested architectures.

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

Options:

You refer to the superior architecture for guidance. You review the projects identified, their dependencies, and synergies, then decide the sequence for starting the projects. You develop high-level architecture descriptions. For each project, you determine how much work is needed, identify reference architectures, and candidate building blocks. You identify the resource needs taking into account cost and value. You document the different o

You look outside the company to study how other companies organize their data models and application portfolios. You create just enough architecture description for the Application, Data, and Technology Architectures to identify the different options. For each project, this includes identification of candidate architecture and solution building blocks. You then identify solution providers, perform a readiness assessment, and assess the viab

You research leading data companies, using your findings to help in developing high-level Target Data, Application, and Technology Architectures. You review the Architecture Vision to determine the level of detail, time, and scope of the ADM cycle phases required for each project. You identify and estimate the cost of the main resources. You then prepare an Architecture Roadmap and request the Architecture Board to review the roadmap. You t

You commence an iteration of ADM Phase A, identifying the stakeholders and revising the Architecture Vision. You perform a Stakeholder Analysis and update the Stakeholder Map. You conduct workshops and interviews to reflect the stakeholders who are now the key drivers for the digital products and services. You coordinate with the CIO to ensure alignment with the overall roadmap and update the Implementation and Migration Plan accordingly.

Answer:

Explanation:

Comprehensive and Detailed Step-by-Step Explanation

Context of the Scenario

The company is in the process of delivering requested architectures to support the introduction of digital products and services. The Business Architecture is sufficiently defined, and the focus is on developing the Information Systems and Technology Architectures.

TOGAF emphasizes breaking down large, complex transformation programs into manageable projects, focusing on dependencies, risks, trade-offs, and sequencing of efforts. Based on the scenario, the company must deal with:

Data privacy and residency compliance across different regions.

Re-use of existing architecture for efficiency.

Alignment of digital services with a global roadmap.

The activity described aligns with ADM Phases B (Business Architecture), C (Information Systems Architecture), and D (Technology Architecture), with a focus on delivering architectures for implementation.

Option Analysis

Option A:

Strengths:

Refers to developing high-level architecture descriptions and identifying reference architectures and candidate building blocks, which align with ADM Phases B, C, and D.

Addresses feasibility analysis, trade-offs, and stakeholder engagement, which are part of architecture development and decision-making in TOGAF.

Ensures that the architecture descriptions are resource-conscious, including cost and value analysis, dependencies, risks, and synergies between projects.

Conclusion: Correct, as it provides a complete approach to organizing the work to deliver architectures while adhering to TOGAF principles.

Option B:

Strengths:

Suggests creating architecture descriptions for the Application, Data, and Technology Architectures, which are necessary for delivering requested architectures.

Addresses readiness assessments and the fitness of solutions.

Weaknesses:

Emphasizes looking outside the company and studying other companies’ models, which is not necessarily aligned with TOGAF unless justified by specific gaps.

Skips essential TOGAF steps like feasibility analysis and detailed stakeholder engagement.

Conclusion: Incorrect, as it places undue emphasis on external research instead of leveraging TOGAF’s structured ADM.

Option C:

Strengths:

Suggests reviewing the Architecture Vision and determining scope, which aligns with TOGAF principles.

Proposes preparing an Architecture Roadmap and involving the Architecture Board for review.

Weaknesses:

Does not cover important elements such as candidate building blocks, feasibility analysis, or stakeholder engagement.

Suggests starting the project prematurely without proper sequencing or risk trade-offs.

Conclusion: Incorrect, as it skips key steps and lacks a structured approach to dependencies and resource management.

Option D:

Strengths:

Suggests revising the Architecture Vision and conducting a Stakeholder Analysis, which aligns with Phase A of the ADM.

Weaknesses:

Returning to Phase A is not required here, as the Architecture Vision has already been defined. Revising the vision at this stage indicates a step backward.

Lacks focus on feasibility analysis, dependencies, and sequencing, which are the immediate needs in this phase.

Conclusion: Incorrect, as it unnecessarily revisits earlier ADM phases instead of progressing.

TOGAF References

ADM Phases B, C, D: Emphasizes developing detailed architectures, identifying candidate building blocks, and addressing dependencies, risks, and resource needs (TOGAF 9.2, Chapters 8-10).

Architecture Roadmap and Feasibility Analysis: Guides sequencing and trade-offs for implementation (TOGAF 9.2, Section 12.4).

Stakeholder Engagement: Critical for ensuring alignment and feasibility (TOGAF 9.2, Section 24.2).

Decision-Making and Trade-offs: TOGAF emphasizes documenting risks and trade-offs as part of feasibility analysis (TOGAF 9.2, Section 6.4.1).

Question 8

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 todefine groups of partners (the stakeholders) who have common concerns and include developmentof a Stakeholder Map. The concerns and relevant views should then be defined for each group andrecorded in the Architecture Vision document. To mitigate risk, you include a requirement that therebe progressive development of the target architecture to

You recommend that a Communications Plan be created to address the key stakeholders, that is themost powerful and influential partners. This plan should include a report that summarizes the keyfeatures 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 mitigationshould be explicitly addressed as a component of

You recommend that models be created for the Draft Business, Data, Application, and TechnologyArchitectures. These can be used to ensure that the system will be compliant with the localregulations for each division. Together with the problem description, and requirements, this ensuresthat all the necessary data and detail is addressed. A formal review should be held with thestakeholders to verify that their concerns have been properly addre

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 maximumportability across the many tools used in the firm. Each architecture should then be defined based onthis fixed set of models. All concerned parties can then examine the models to ensure that theirneeds have been addressed.

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.

Options:

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

Service Orientation, Compliance with the Law, Requirements Based Change, Responsive Change Management, Data Security

Common Use Applications, Data is an Asset, Common Vocabulary and Data Definitions, Maximize Benefit to the Enterprise, Business Continuity

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

Answer:

Explanation:

The correct answer is C, as it aligns with the key TOGAF principles necessary for guiding enterprise architecture in a merger scenario where retail operations and systems are being consolidated.

Analysis of the Principles in Option C:

Common Use Applications

Since the two companies are merging, it is essential to standardize applications across the enterprise.

Using common applications ensures consistency, reduces costs, and improves efficiency.

TOGAF emphasizes this principle to prevent duplicate or redundant systems, which aligns with the CIO’s goal of reducing the number of applications used.

Data is an Asset

In the scenario, a central inventory management system is a core business function.

Treating data as an asset ensures it is managed properly, shared efficiently, and used strategically across the merged organization.

This principle supports the company’s ability to predict demand, adjust stock levels, and automate reordering.

Common Vocabulary and Data Definitions

The merger requires integrating different systems and data structures.

Having a common vocabulary ensures that all stakeholders (stores, fulfillment centers, and digital platforms) use consistent terminology and data definitions.

This minimizes confusion and ensures interoperability across business functions.

Maximize Benefit to the Enterprise

Every architectural decision should focus on the overall benefit to the business.

By consolidating IT systems and reducing redundancies, the company achieves cost savings, which directly supports this principle.

Business Continuity

The stores operate seven days a week, so system changes must ensure uninterrupted service.

Business continuity ensures that customers are not affected during the transition and that critical retail operations (sales, inventory tracking, and fulfillment) remain functional.

Why Other Options Are Incorrect?

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

Control Technical Diversity is not the primary concern here. The focus is on system consolidation, not necessarily on limiting technology diversity.

Interoperability is important but not as critical as defining a common system and data structure.

Option B: Service Orientation, Compliance with the Law, Requirements-Based Change, Responsive Change Management, Data Security

While service orientation and compliance are valuable, they are not the most relevant to this specific business transition.

Change management and data security are important but do not address the primary enterprise-wide architectural concerns of system consolidation.

Option D: Ease of Use, Common Use Applications, Data is an Asset, Technology Independence, Business Continuity

Ease of Use is beneficial but is not a core architecture principle in this case.

Technology Independence is useful but does not align directly with the scenario’s priority, which is consolidating applications and data structures.

[References:, TOGAF Standard, ADM Techniques, Architecture Principles (Section 2.6), TOGAF Standard, Part III: ADM Guidelines and Techniques, TOGAF Enterprise Architecture Principles – The Open Group, , , , , , , ]

Question 10

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 two years. 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?

Options:

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.

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.

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.

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

Answer:

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 assets within each domain, the security policies for each domain, and the relationships and dependencies between the domains1

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 implications2

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 situation3

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.

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

Load More OGEA-102 Questions

Page: 1 / 3
Total 34 questions

Get OGEA-102 Full Access Download OGEA-102 PDF

Spring Sale Limited Time Flat 70% Discount offer - Ends in 0d 00h 00m 00s - Coupon code: 70spcl

Activedumpsnet Logo

Activedumpsnet Navigation

Activedumpsnet Slider

The Open Group OGEA-102 TOGAF Enterprise Architecture Part 2 Exam (English) Exam Practice Test

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

Options:

Answer:

Explanation:

Options:

Answer:

Explanation:

Options:

Answer:

Explanation:

Options:

Answer:

Explanation:

Options:

Answer:

Explanation:

Options:

Answer:

Explanation:

Options:

Answer:

Explanation:

Options:

Answer:

Explanation:

Options:

Answer:

Explanation:

Options:

Answer:

Explanation:

Copyright © 2014-2026 Activedumpsnet. All Rights Reserved