OGEA-103 The Open Group TOGAF Enterprise Architecture Combined Part 1 and Part 2 Exam exact Exam Questions

TOGAF Enterprise Architecture Combined Part 1 and Part 2 Exam

Last Update 18 hours ago Total Questions : 200

The TOGAF Enterprise Architecture Combined Part 1 and Part 2 Exam content is now fully updated, with all current exam questions added 18 hours ago. Deciding to include OGEA-103 practice exam questions in your study plan goes far beyond basic test preparation.

You'll find that our OGEA-103 exam questions frequently feature detailed scenarios and practical problem-solving exercises that directly mirror industry challenges. Engaging with these OGEA-103 sample sets allows you to effectively manage your time and pace yourself, giving you the ability to finish any TOGAF Enterprise Architecture Combined Part 1 and Part 2 Exam practice test comfortably within the allotted time.

Question # 11

Please read this scenario prior to answering the question

You are employed as an Enterprise Architect within a clinical research and health

technologies company. The company is 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 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. 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.

Many of the company ' s rivals have begun using 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 roles?

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

seamless?

How can Al 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.

Refer to the scenario

You have been assigned to the architecture development and asked how to address

the concerns and manage risk for the project. How do you begin?

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

You recommend that an analysis of the stakeholders is carried out. This willallow the architects to define groups of stakeholders who have commonconcerns and include development of a Stakeholder Map. The concerns andrelevant views should then be defined for each group and recorded in theArchitecture Vision document. To mitigate risk, you include a requirement thatthere be progressive development of the target architecture to ensure there is

You recommend that all the stakeholders be identified, and a CommunicationsPlan created to address the most powerful and influential stakeholders. Thisplan should include a report that summarizes the key features of thearchitecture with respect to each division and reflects the stakeholders ' requirements. You will check with each key stakeholder that their concerns arebeing addressed. Risk mitigation should be explicitly addressed as acomp

You recommend creation of a simple solution concept diagram to show howthe stakeholders will be impacted, and the benefits to the firm. You would alsocreate a benefits diagram showing the various opportunities from adoption ofAl-based solutions. A meeting should be held with the main stakeholders toreview the diagrams. They can then decide the priorities and sequencingdecisions for the architecture development. Risk will be evaluated whende

You recommend that models be created for the Draft Business, Data,Application, and Technology Architectures. These can be used to minimize risk,and make sure that the system meets the local regulations for each division.Together with the problem description, and requirements, these should beincluded in the Architecture Vision document. A formal review should be heldwith the stakeholders to verify that their concerns are included in theArchi

Answer:

Explanation:

In this scenario you are right at the start of an ADM cycle: a Request for Architecture Work has been approved to investigate AI, and there are strong stakeholder concerns and risk questions. According to the TOGAF standard, the correct place to start is Phase A: Architecture Vision, with a strong focus on stakeholder management and capturing their concerns and required views.

Option A is the only answer that correctly reflects this:

Stakeholder analysis & Stakeholder Map (Phase A core task)TOGAF explicitly states that in Phase A you must:

Identify stakeholders

Analyze and group them by common concerns

Use a Stakeholder Map to understand their influence, interest, and required engagement

Determine which views/viewpoints are needed to address their concerns in the architecture description coe.qualiware.com+1

Option A says:

“analysis of the stakeholders … define groups of 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.”

This is exactly how TOGAF describes stakeholder management and views in Phase A:

Stakeholder Map to classify and prioritize stakeholders

Concerns and required views captured and traced

These elements feeding into the Architecture Vision deliverable Visual Paradigm TOGAF+1

Concerns, views, and Architecture VisionTOGAF emphasizes that architecture views are constructed to address specific stakeholder concerns; you do not just build generic models. opengroup.org+1

Option A explicitly links concerns → views → Architecture Vision, which aligns with TOGAF guidance for early phases.

Capturing this in the Architecture Vision provides a high-level, shared understanding of what the AI initiative is trying to achieve and how stakeholder issues (e.g., responsible AI, risk processes, change in way of working) will be addressed.

Risk management and “architecting with agility”In the scenario, the CIO has encouraged architecting with agility. TOGAF is compatible with incremental and iterative development of the target architecture, especially when there is high uncertainty and risk. conexiam.com

Option A includes:

“a requirement that there be progressive development of the target architecture to ensure there is regular feedback.”

This “progressive development” and frequent feedback loop is exactly how you mitigate risk in an AI-heavy, change-sensitive initiative:

Frequent stakeholder feedback

Early validation of assumptions

Ability to adjust scope, constraints, and principles as risk and understanding evolve

This directly addresses management’s worry about the change in the way of working and whether risk management and responsible AI policies are adequate: these become explicit stakeholder concerns and requirements that are iteratively refined.

Why the other options are weaker / not TOGAF-aligned as a starting point

Option B

Focuses mainly on a Communications Plan and powerful stakeholders.

While TOGAF does expect a stakeholder communications plan, it is derived from a proper stakeholder analysis and Stakeholder Map, not a substitute for it.

It also treats risk as a “component of the architecture” rather than something to be addressed early through stakeholder concerns, principles, and iteration.

Option C

Jumps straight to a solution concept diagram and benefits diagram and defers risk evaluation to when the Architecture Roadmap is defined (Phase E).

In TOGAF, risk and stakeholder concerns must be addressed already in Phase A and refined throughout, not postponed to roadmap development.

Option D

Proposes creating draft Business, Data, Application, and Technology models and putting them into the Architecture Vision.

This is too detailed for the starting point: Phase A is about high-level vision, not full draft core architecture models (those belong in Phases B, C, D).

It also doesn’t emphasize Stakeholder Mapping and grouping by concerns, which is central to resolving the worries about way of working, risk, and responsible AI.

In summary, Option A is the best and TOGAF-consistent way to begin:

Start in Phase A: Architecture Vision

Perform stakeholder analysis and create a Stakeholder Map

Define stakeholder concerns and relevant views

Record them in the Architecture Vision

Add an explicit requirement for progressive (iterative) development of the target architecture for continuous feedback and risk mitigation

Question # 12

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?

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.

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.

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.

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.

Answer:

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

Question # 13

Please read this scenario prior to answering the question

You are employed as an Enterprise Architect for a company that supplies products for industrial production automation. You are part of an Enterprise Architecture (EA) team that has responsibilities across the company.

The company has multiple manufacturing plants where it assembles both standard and customized products. Each of these plants operates its own planning and production scheduling systems, as well as applications and control systems that drive the automated production line.

During a recent management meeting, the agenda included discussion of how a competitor company had improved production efficiency by replacing multiple planning and scheduling systems with a single cloud-based system. This had reduced lifecycle costs through reduced duplication, lowered software maintenance costs, and supported incremental replacement. The CIO claimed the company ' s current systems architecture is already optimized. However, as the competitor has reported better financial results, the CEO has requested an investigation of a cloud-based solution.

In response, the Architecture Board approved a Request for Architecture Work to find out if such an architecture transformation would lead to efficiency improvements. You have been asked to help the architecture team with this project.

A concern of the plant managers is the safety and dependability of using a remote centralized system for planning and scheduling production. The system they choose must also be able to work with the local partners in the supply chain at each plant.

The company has an Enterprise Architecture (EA) practice and uses the TOGAF standard as the basis for its work. It has been running for many years and has established governance and development processes for EA. The Chief Information Officer (CIO) sponsors the Enterprise Architecture program.

Refer to the scenario

You have been asked to describe how you will start the architecture project.

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

You would conduct a series of workshops with the local partners to gather requirements from them. Based on the findings from the workshops, 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 the Architecture Vision to build agreement among t

You would gather information from your suppliers and conduct a series of briefings with those of them 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

You would develop baseline and target Architectures for each manufacturing plant, 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 increment

You would run a series of interviews at each manufacturing plant to discover and document business requirements. This would also help you understand the systems and integrations with local partners. You would create a matrix of stakeholders and their primary concerns. You would then determine and record the main stakeholder requirements for the architecture. You would then create clear high-level descriptions of the current and future archi

Answer:

Explanation:

Option A best aligns with TOGAF Phase A: Architecture Vision, which is the starting phase for an architecture development cycle in TOGAF. This phase sets the foundation for the architecture engagement and ensures alignment with stakeholders and their concerns, especially when evaluating a major transformation like moving to a cloud-based planning and scheduling system.

???? Key TOGAF Concepts Supporting Option A:

1. Phase A: Architecture Vision Objectives

Establish the high-level scope, constraints, and expectations.

Identify stakeholders and define their concerns and business requirements.

Create the Architecture Vision, which includes:

Summary-level Baseline and Target Architecture views (business, data, application, and technology).

Initial requirements and key concerns.

Stakeholder buy-in and approval for moving forward.

2. Engagement with Stakeholders

In this case, the plant managers and local supply chain partners have concerns regarding safety and dependability.

TOGAF emphasizes early engagement with business stakeholders to ensure concerns are identified and incorporated into the vision.

3. Creating Architecture Vision Document

A deliverable of Phase A.

Includes high-level descriptions of the baseline and target architectures, initial business goals, and stakeholder viewpoints.

Used to build agreement and obtain formal approval to proceed with detailed architecture work in later phases (B–D).

❌ Why Other Options Are Incorrect:

B: Focuses on suppliers and not the actual stakeholders impacted by the architecture — i.e., plant managers and internal operations. This diverts from TOGAF’s stakeholder-driven approach in Phase A.

C: This reflects Phases B–D of the ADM (Business, Information Systems, and Technology Architecture). It is too detailed and premature for the start of the project. In Phase A, you don’t yet develop full baseline and target architectures or conduct a consolidated gap analysis.

D: While interviewing stakeholders is valid in Phase A, this option lacks a holistic view of the Architecture Vision development, and skips the TOGAF requirement to produce summary views of the baseline and target architectures and to use them to drive stakeholder buy-in. It is tactically correct, but strategically incomplete.

???? TOGAF Source References:

TOGAF 9.2 – Section 6.2 (Phase A: Architecture Vision)

" The Architecture Vision describes how the proposed architecture support the business goals, and the strategic direction. It also provides a high-level description of the baseline and target architectures and identifies key stakeholders and concerns. "

TOGAF 9.2 – Part IV, Architecture Content Framework

" The Architecture Vision includes the scope, constraints, and expectations. It forms the basis for approval to proceed with further architecture development. "

Question # 14

Scenario

Your role is that of an Enterprise Architect, reporting to the Chief Enterprise Architect, at a technology company.

The company uses the TOGAF standard as the method and guiding framework for its Enterprise Architecture (EA) practice. The Chief Technology Officer (CTO) is the sponsor of the activity. The EA practice uses an iterative approach for its architecture development. This has enabled the decision-makers to gain valuable insights into the different aspects of the business.

The nature of the business is such that the data and the information stored on the company systems is the company’s major asset and is highly confidential. The company employees travel a lot for work and need to communicate over public infrastructure. They use message encryption, secure internet connections using Virtual Private Networks (VPNs), and other standard security measures. The company has provided computer security awareness training for all its staff. However, despite good education and system security, there is still a need to rely on third-party suppliers for infrastructure and software.

The Chief Security Officer (CSO) has noted an increase in ransomware (malicious software used in ransom demands) attacks on companies with a similar profile. The CSO recognizes that no matter how much is spent on education and support, the company could be a victim of a significant attack that could completely lock them out of their important data.

A risk assessment has been completed, and the company has looked for cyber insurance that covers ransomware. The price for this insurance is very high. The CTO recently saw a survey that said 1 out of 4 businesses that paid ransoms could not get their data back, and almost thesame number were able to recover the data without paying. The CTO has decided not to get cyber insurance to cover ransom payment.

You have been asked to describe the steps you would take to strengthen the current architecture to improve data protection.

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

You would ensure that the company has in place up-to-date processes for managing change to the current Enterprise Architecture. Based on the scope of the concerns raised, you recommend that this be managed at the infrastructure level. Changes should be made to the baseline description of the Technology Architecture. The changes should be approved by the Architecture Board and implemented by change management techniques.

You would request an Architecture Compliance Review with the scope to examine the company’s ability to respond to ransomware attacks. You would identify the departments involved and have them nominate representatives. You would then tailor checklists to address the requirement for increased resilience. You would circulate to the nominated representatives for them to complete. You would then review the completed checklists, identifying and r

You would monitor for technology updates from your existing suppliers that could enhance the company’s capabilities to detect, react, and recover from an IT security incident. You would prepare and run a disaster recovery planning exercise for a ransomware attack and analyze the performance of the current Enterprise Architecture. Using the findings, you would prepare a gap analysis of the current Enterprise Architecture. You would prepare c

You would assess business continuity requirements and analyze the current Enterprise Architecture for gaps. You would recommend changes to address the situation and create a change request. You would engage the Architecture Board to assess and approve the change request. Once approved, you would create a new Request for Architecture Work to begin an ADM cycle to implement the changes.

Answer:

Explanation:

Comprehensive and Detailed Step-by-Step Explanation

Context of the Scenario

The scenario highlights significant risks due to ransomware attacks and the need to strengthen the company’s Enterprise Architecture to improve data protection and resilience. TOGAF emphasizes the Architecture Compliance Review as a mechanism for ensuring the architecturemeets its objectives and addresses specific concerns such as security, resilience, and compliance with organizational goals.

The organization has already conducted a risk assessment but requires actionable steps to:

Address ransomware attack risks.

Increase the resilience of the Technology Architecture.

Ensure proper alignment with governance and compliance frameworks.

Option Analysis

Option A:

Strengths:

Highlights the need for up-to-date processes for managing changes in the Enterprise Architecture.

Recognizes the importance of governance through the Architecture Board and change management techniques.

Weaknesses:

The approach focuses solely on the Technology Architecture baseline but does not address the need for specific steps such as compliance review, gap analysis, or tailored resilience measures for ransomware risks.

It provides a broad and generic approach rather than a targeted plan for ransomware and data protection issues.

Conclusion: Incorrect. While it adheres to governance processes, it lacks specific actions to improve resilience and address the immediate security concerns.

Option B:

Strengths:

Proposes an Architecture Compliance Review, which is a core TOGAF process used to evaluate architecture implementation against defined objectives, ensuring it is fit for purpose.

Involves identifying stakeholders (departments) and tailoring checklists specific to ransomware resilience.

Emphasizes issue identification and resolution through structured review processes.

Weaknesses:

Does not explicitly address longer-term updates to the Enterprise Architecture, but this can be inferred as a next step following compliance recommendations.

Conclusion: Correct. This is the most suitable approach based on TOGAF principles, as it uses an established process to evaluate and improve the architecture ' s resilience.

Option C:

Strengths:

Includes monitoring for updates from suppliers to enhance detection and recovery capabilities, which is relevant to addressing ransomware risks.

Proposes a gap analysis to identify shortcomings in the current Enterprise Architecture and recommends addressing gaps through change requests.

Incorporates disaster recovery planning exercises, which are useful for testing resilience.

Weaknesses:

While thorough, the approach lacks the Architecture Compliance Review process, which is a more structured way to ensure the architecture meets resilience requirements.

Monitoring suppliers and running disaster recovery exercises are operational steps rather than strategic architectural improvements.

Conclusion: Incorrect. While it includes valid activities, it does not adhere to TOGAF’s structured approach for architecture assessment and compliance.

Option D:

Strengths:

Proposes analyzing business continuity requirements and assessing the architecture for gaps, which is relevant to the scenario.

Suggests initiating an ADM cycle to address gaps, which aligns with TOGAF principles.

Weaknesses:

Focusing on initiating a new ADM cycle may be premature, as the immediate priority is to evaluate the existing architecture and address specific resilience concerns.

Does not mention compliance review or tailored resilience measures for ransomware attacks, which are central to the scenario.

Conclusion: Incorrect. It proposes a broader approach that may not adequately address the immediate concerns highlighted by the CSO.

TOGAF References

Architecture Compliance Review: A structured process used to evaluate whether an architecture meets the stated goals, objectives, and requirements (TOGAF 9.2, Chapter 19). It is particularly useful for identifying and addressing resilience requirements in scenarios involving security risks.

Stakeholder Engagement: Identifying and involving stakeholders (e.g., departments) is a critical part of architecture governance and compliance review (TOGAF 9.2, Section 24.2).

Change Management: The Architecture Compliance Review supports identifying necessary changes, which are then managed through governance and change management processes (TOGAF 9.2, Section 21.6).

By choosing Option B, you align with TOGAF’s structured approach to compliance, resilience, and addressing security concerns.

Question # 15

Please read this scenario prior to answering the question

You are employed as an Enterprise Architect within a multinational company. The

company has been very successful and has been buying companies around the

world. This has led to a growing number of manufacturing divisions in various

locations with a complex supply chain.

The top management recently expressed concerns about the company ' s effectiveness

because of its multiple data centers and duplicate applications. The EA team has

been working on a project to solve this issue. An analysis shows that supply chain

issues have led to not enough products being produced to meet all the customer

demand.

A strategic architecture has been defined to help meet customer demand and manage

the supply chain more effectively. The strategic architecture involves combining

different Enterprise Resource Planning (ERP) applications that are currently used

separately in the company ' s production sites.

Each division has finished the Architecture Definition documentation to address their

own specific manufacturing needs. The Enterprise Architects have agreed an overall

strategy for the migration. They have defined a set of work packages that address the

gaps found. They have defined the intermediate architectural states between the

Baseline and Target architecture to add a new ERP environment into the company.

Because of the risks posed by this change from the current environment, the

architects have recommended that a phased approach should be taken to implement

the target architecture with several stages of change. They have created a draft

roadmap with the implementation process estimated to take over two years.

The company has an established Enterprise Architecture (EA) practice and follows the

TOGAF Architecture Development Method. The company also uses various

management frameworks such as business planning, project/portfolio management,

and operations management. The EA program is sponsored by the Chief Information

Officer (CIO). In your role as an Enterprise Architect within the EA team, you work

closely with the important stakeholders from the various divisions within the company.

Refer to the scenario

You have been assigned to plan the next steps for the migration. Which approach will

you choose?

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

You finalize the Architecture Definition documentation with updates to reflectthe implementation approach. You ensure that Implementation and MigrationPlan is consistent with the chosen approach. You identify the resourcesneeded to undertake the development projects. You would then produce anImplementation Governance Model to manage the lessons learned beforefinishing the plan. You ensure that the lessons learned are applied to theImplement

You estimate the business value for each project by applying the BusinessValue Assessment Technique to prioritize the migration projects and projectsteps. The assessment should focus on return on investment and criteria forevaluating performance to track the progress of the architecturetransformation. You would confirm and plan a series of Transition Architecturephases using a table of Architecture Definition Increments that lists theprojec

You will focus on project selection. You make sure that the Implementation andMigration plan aligns with the other management frameworks in use in thecompany. Next, you assign a value to each work package, taking into accountthe resources available and how they fit into the overall strategy. Using thesework packages, you estimate resource requirements and timings. You thenselect which projects will be included in the Implementation and Migr

You conduct a series of Compliance Assessments to check that thearchitecture is being implemented as required by the contract. This is donenow to confirm that the implementation team is following the correctdevelopment process, and if not, so course correction is viable. This involvesusing monitoring tools and making sure that performance targets are beingachieved. If the targets are not met, you would then need to make adjustmentsto the p

Answer:

Explanation:

At this stage in the scenario:

A strategic architecture has been completed.

All divisions have completed their Architecture Definition Documents.

Work packages have been defined.

Transition Architectures between Baseline and Target are already identified.

A draft roadmap exists for a multi-year phased migration.

You are now asked to plan the next steps for the migration, which aligns exactly with TOGAF ADM Phase F: Implementation and Migration Planning.

In Phase F, TOGAF prescribes the following key activities:

Evaluate and prioritize projects and work packages

Determine business value, cost, risk, dependencies

Confirm Transition Architectures and sequencing

Update and finalize the Implementation & Migration Plan

Option B is the ONLY answer that correctly follows these required TOGAF steps.

✔ Why Option B is correct

Option B states:

“Estimate the business value for each project by applying the Business Value Assessment Technique … to prioritize the migration projects.”✔ This is a TOGAF-recommended technique specifically for Phase F to evaluate and prioritize transformations using value, risk, and ROI.

“Confirm and plan a series of Transition Architecture phases … using a table of Architecture Definition Increments.”✔ Exactly aligned with TOGAF:

Transition Architectures were identified earlier.

In Phase F, they must be confirmed, sequenced, and documented.

“Update the Implementation and Migration Plan.”✔ This is the required output of ADM Phase F.✔ At this point, the plan must be validated and finalized based on value and prioritization.

Thus, Option B directly matches TOGAF’s prescribed migration planning process.

✘ Why the other options are incorrect

A – Incorrect

Suggests finalizing Architecture Definition documentation—this was already completed by each division.

Introduces an “Implementation Governance Model,” which is not a TOGAF artifact at this stage.

Focuses on lessons learned BEFORE execution, which is not appropriate for migration planning.

C – Incorrect

Focuses only on project selection and resource assignment.

Does not use TOGAF techniques for value/risk evaluation.

Does not reference Transition Architectures, which are central in the scenario.

Oversimplifies Implementation & Migration Planning to resource scheduling.

D – Incorrect

Compliance Assessments occur DURING execution, not before migration planning.

At this stage, no implementation has started, so compliance reviews are premature.

Adjusting performance requirements now has no alignment with TOGAF’s ADM sequence.

Question # 16

Please read this scenario prior to answering the question

Your role is that of a senior architect, reporting to the Chief Enterprise Architect, at a medium-sized company with 400 employees. The nature of the business is such that the data and the information stored on the company systems is their major asset and is highly confidential.

The company employees travel extensively for work and must communicate over public infrastructure using message encryption, VPNs, and other standard safeguards. The company has invested in cybersecurity awareness training for all its staff. However, it is recognized that even with good education as well as system security, there is a dependency on third-parly suppliers of infrastructure and software.

The company uses the TOGAF standard as the method and guiding framework for its Enterprise Architecture (EA) practice. The CTO is the sponsor of the activity.

The Chief Security Officer (CSO) has noted an increase in ransomware (malicious software used in ransom demands) attacks on companies with a similar profile. The CSO recognizes that no matter how much is spent on education, and support, it is likely just a matter of time before the company suffers a significant attack that could completely lock them out of their information assets.

A risk assessment has been done and the company has sought cyber insurance that includes ransomware coverage. The quotation for this insurance is hugely expensive. The CTO has recently read a survey that stated that one in four organizations paying ransoms were still unable to recover their data, while nearly as many were able to recover the data without paying a ransom. The CTO has concluded that taking out cyber insurance in case they need to pay a ransom is not an option.

Refer to the scenario

You have been asked to describe the steps you would take to improve the resilience of the current architecture?

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

You would determine business continuity requirements, and undertake a gap analysis of the current Enterprise Architecture. You would make recommendations for change requirements to address the situation and create a change request. You would manage a meeting of the Architecture Board to assess and approve the change request. Once approved you would produce a new Request for Architecture Work to activate an ADM cycle to carry out a project

You would monitor for technology changes from your existing suppliers that could improve resilience. You would prepare and run a disaster recovery planning exercise for a ransomware attack and analyze the performance of the current Enterprise Architecture. Using the findings, you would prepare a gap analysis of the current Enterprise Architecture. You would prepare change requests to address identified gaps. You would add the changes implem

You would ensure that the company has in place up-to-date processes for managing change to the current Enterprise Architecture. Based on the scope of the concerns raised you recommend that this be managed at the infrastructure level. Changes should be made to the baselinedescription of the Technology Architecture. The changes should be approved by the Architecture Board and implemented by change management techniques.

You would request an Architecture Compliance Review with the scope to examine the company ' s resilience to ransomware attacks. You would identify the departments involved and have them nominate representatives. You would then tailor checklists to address the requirement for increased resilience. You would circulate to the nominated representatives for them to complete. You would then review the completed checklists, identifying and resolvi

Answer:

Explanation:

Business continuity is the ability of an organization to maintain essential functions during and after a disaster or disruption. Business continuity requirements are the specifications and criteria that define the acceptable level of performance and availability of the business processes and services in the event of a disaster or disruption. A gap analysis is a technique that compares the current state of the architecture with the desired state, and identifies the gaps or differences that need to be addressed. A change request is a formal proposal for an amendment to some product or system, such as the architecture. A Request for Architecture Work is a document that describes the scope, approach, and expected outcomes of an architecture project123

The best answer is A, because it describes the steps that would improve the resilience of the current architecture, which is the ability to withstand and recover from a ransomware attack or any other disruption. The steps are:

Determine the business continuity requirements, which specify the minimum acceptable level of performance and availability of the business processes and services in case of a ransomware attack. This would involve identifying the critical business functions, the recovery time objectives, the recovery point objectives, and the dependencies and resources needed for recovery.

Undertake a gap analysis of the current Enterprise Architecture, which compares the current state of the architecture with the desired state based on the business continuity requirements. This would involve assessing the strengths and weaknesses of the current architecture, the risks and opportunities for improvement, and the gaps or differences that need to be addressed.

Make recommendations for change requirements to address the situation and create a change request. This would involve proposing solutions and alternatives to close the gaps, enhance the resilience, and mitigate the risks of the current architecture. The change request would document the rationale, scope, impact, and benefits of the proposed changes, and seek approval from the relevant stakeholders.

Manage a meeting of the Architecture Board to assess and approve the change request. The Architecture Board is a governance body that oversees the architecture work and ensures compliance with the architecture principles, standards, and goals. The meeting would involvepresenting the change request, discussing the pros and cons, resolving any issues or conflicts, and obtaining the approval or rejection of the change request.

Once approved, produce a new Request for Architecture Work to activate an ADM cycle to carry out a project to define the change. The Request for Architecture Work would describe the scope, approach, and expected outcomes of the architecture project that would implement the approved change request. The Request for Architecture Work would initiate a new cycle of the Architecture Development Method (ADM), which is the core process of the TOGAF standard that guides the development and management of the enterprise architecture.

1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 33: Business Scenarios 2: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 30: Gap Analysis 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 31: Architecture Change Management : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 7: Request for Architecture Work : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 34: Business Transformation Readiness Assessment : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 30: Gap Analysis : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 31: Architecture Change Management : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50: Architecture Governance : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 7: Request for Architecture Work

Question # 17

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

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

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

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

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

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

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

Answer:

Explanation:

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

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

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

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

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

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

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

Question # 18

Which of the following is a purpose of Phase A of the TOGAF ADM?

Identifying key stakeholders

Defining the Enterprise strategy

Describing the target architecture

Developing an Enterprise Architecture Capability

Question # 19

Please read this scenario prior to answering the question

You are employed as an Enterprise Architect working at a vehicle manufacturing

company. The company specializes in buses and coaches. You are part of an

Enterprise Architecture (EA) team that has responsibilities across multiple divisions of

the company. EA provides the company with a comprehensive framework to develop

and manage their manufacturing infrastructure, processes for component production,

and design and testing systems.

The company has a corporate strategy that focuses on switching to electric power for

its vehicles. It has invested heavily in a new standardized design, production efforts,

and major components to use across all its product range. The company has multiple

manufacturing plants in North America, Europe, and in Asia.

Customer demand has caused a backlog of orders because many customers want to

have more environmentally friendly public transportation. There are not enough

electronic components available, which is making it hard to produce products and

meet customer demand. To address this issue, the company has started making the

battery packs themselves and has hired new suppliers.

The EA team is working on a project to improve the process and systems to design,

produce, and test the battery pack. As part of putting the new battery pack into

production, changes to the assembly processes need to be made. A trial has been

completed at a single location. The Chief Engineer, sponsor of the project, and the

Architecture Board have approved the plan to roll out these changes to all plants.

Preliminary Architecture Contracts are being developed to detail the work needed to

put in place the new processes for each location. The EA team leader has called a

meeting to discuss the contracts. It is emphasized that the Architecture Contract will

serve as the key connection between architecture and implementation organizations.

The company mixes internal teams with a few third-party contractors at the locations.

The Chief Engineer is worried that the implementation and deployment will not be

consistent and of satisfactory quality.

The company has an established EA practice. It uses the TOGAF standard as the

foundation for its work including the internal EA framework. Additionally, the company

uses various management frameworks such as business planning, project

management, and operations management.

Refer to the scenario

The EA team leader asks you how you would address the Chief Engineer ' s concern.

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

The contracts must be checked to ensure they have flexibility. For changesundertaken by internal teams, a memorandum of understanding between theArchitecture Board and the implementation organization is needed. If acontract is issued to a contractor, it must be a fully enforceable legal contract. Ifa deviation from the Architecture Contract is found, the Architecture Boardmust grant a dispensation to allow the implementation organization to

The contracts must be checked to ensure they can be used to direct andcontrol the implementation teams. For contracts issued to third-partycontractors, they must be enforceable legal contracts. For internaldevelopment teams, a memorandum of understanding with the ArchitectureBoard is needed. The Architecture Board must review all deviations from theArchitecture Contract and decide whether to grant a dispensation to allow theimplementation o

The contracts must specify goals, measures, acceptance terms, and risks.Third-party contracts must be legally enforceable. It is advisable to establish aschedule of compliance reviews at key points in the implementation process.The Architecture Board must review all deviations from the ArchitectureContract and consider whether to grant a dispensation to allow the process tobe customized for local needs. Ensure that all dispensations are tim

The contracts must be used to manage the architecture governance processesacross the locations. Monitoring tools must be put in place to assess theperformance of each completed battery pack at each location. If a deviationfrom the contract is needed, the Architecture Board should allow theArchitecture Contract to be modified for the location. In such cases they shouldissue a new Request for Architecture Work to implement a modification to t

Answer:

Explanation:

The Chief Engineer is concerned that implementation across multiple plants and mixed teams (internal + contractors) may be inconsistent and of poor quality.

The question asks: How should Architecture Contracts be used to address this concern according to the TOGAF standard?

TOGAF states that an Architecture Contract must:

Define obligations of both architecture and implementation organizations

Specify metrics, measures, acceptance criteria, and success factors

Identify risks and mitigation

Support Architecture Governance through compliance reviews

Apply to BOTH internal teams and external suppliers (external contracts must be legally enforceable)

Option C is the only one that correctly reflects these TOGAF requirements.

✔ Why Option C is correct

1. Architecture Contracts must specify goals, measures, acceptance terms, and risks

TOGAF explicitly states that Architecture Contracts should include:

Statement of Architecture Work

Performance metrics and measures

Acceptance criteria

Risks and issues

Compliance and conformance requirements

Option C includes all of these.

2. Third-party contracts must be legally enforceable

True — TOGAF states that when external suppliers are involved, Architecture Contracts often take the form of legally binding contracts.

Option C:

“Third-party contracts must be legally enforceable.”

Correct.

3. Compliance reviews must be scheduled

TOGAF’s Architecture Governance Framework prescribes scheduled Architecture Compliance Reviews to ensure that implementation conforms to the Architecture Contract.

Option C:

“establish a schedule of compliance reviews at key points”

Correct — this directly addresses the Chief Engineer’s concern about consistency and quality.

4. Deviations must be reviewed by the Architecture Board and any dispensations should be time-bound

TOGAF allows dispensations but requires:

Formal review

Approval by the Architecture Board

Time-bound accommodations rather than permanent exceptions

Option C includes exactly this guidance.

Question # 20

Scenario

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

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

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

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

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

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

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

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

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

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

Answer:

Explanation:

Comprehensive and Detailed Step-by-Step Explanation

Context of the Scenario

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

Job security for employees.

Skill development for adapting to new technologies.

Cybersecurity and resilience risks due to reliance on digital platforms.

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

Option Analysis

Option A:

Strengths:

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

Suggests holding stakeholder meetings to address concerns.

Includes managing risks as part of Security Architecture development.

Weaknesses:

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

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

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

Option B:

Strengths:

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

Suggests addressing stakeholder concerns through communication and risk management.

Weaknesses:

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

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

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

Option C:

Strengths:

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

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

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

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

Weaknesses:

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

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

Option D:

Strengths:

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

Proposes arranging meetings to verify that concerns have been addressed.

Includes risk management as part of the process.

Weaknesses:

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

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

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

TOGAF References

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

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

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

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

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

Go to page: