Please read this scenario prior to answering the questionYou are serving as the Lead Architect...

The Open Group OG0-093 Full Course Access

The Open Group OG0-093 View All Questions

The Open Group OG0-093 Question Answer

Please read this scenario prior to answering the question

You are serving as the Lead Architect for an Enterprise Architecture project team

within a multinational energy company. The company is organized into two major

business operations:

· Upstream operations which include exploration for crude oil and natural gas and

operating the infrastructure necessary to deliver oil and gas to the market

· Downstream operations which include the manufacturing, distribution and marketing

activities for oil products and chemicals

The downstream business includes oil refining, a retail filling station network,

lubricants manufacture and marketing, industrial fuel and lubricants sales. The

practice for the downstream business has been to operate locally, managed by local

"operating companies".

There is an established Enterprise Architecture program within the company, and the

TOGAF standard has been adopted as the framework.

Safety is a priority for the company, with the aim to ensure it causes zero harm to

people and the environment. The company has to satisfy the regulatory requirements

of each of the countries it operates in.

The Governing Board is concerned about the risk posed by operating in this complex

global environment with a large part of the downstream business represented by local

operating companies.

The Chief Executive Officer (CEO) has requested to be informed about the status of

downstream operations that could impact regulatory compliance. He also wants the

corporate legal staff and auditors to analyze all proposed new downstream operations

to ensure that they are within the legal guidelines for each country. In addition, the

local operating companies should be able to see that the architecture is appropriate

for their needs.

The architecture project team has completed a detailed Request for Architecture Work

providing the high level project description. As the project commences the next phase,

the necessary approvals from management have been received.

Refer to the Scenario

You have been asked to recommend an approach that would enable the development

of an architecture that addresses the needs of the Chief Compliance Officer, legal

staff, auditors and the local operating companies.

Based on the TOGAF Standard, Version 9.2, which of the following is the best

answer?

You recommend that a Communications Plan be created to address the

powerful and influential stakeholders identified in a stakeholder power grid

matrix. This plan should include a report that summarizes the key features of

the architecture with respect to each location and reflect the stakeholder

requirements. You will check with each stakeholder that their concerns are

being addressed.

You recommend that an Organization Map is created to show the relationships

between the different operations within the company and the local operating

companies. This will be used to identify key stakeholders. A set of models

should then be developed that can be applied uniformly across the project. The

stakeholders can then examine the models to ensure that their needs have

been addressed.

You recommend that a stakeholder analysis is made, so as to identify which

stakeholders are involved, their level of involvement, and their concerns. This

will allow the architects to define groups of stakeholders who have common

concerns. The concerns and relevant viewpoints should then be defined for

each group of stakeholders, and recorded in the Architecture Vision document.

You recommend that an analysis of stakeholders occurs, with 22 types of

stakeholders identified, in five categories - corporate functions, end-user

organization, project organization, systems, and external. Models should then

be created for each stakeholder category to ensure that the system complies

with the local regulations. A formal review should be held with the stakeholders

to verify that their concerns h

Explanation:

Analysis of Scenario and TOGAF Guidance

In this scenario, you are leading an architecture project for a multinational energy company with both upstream and downstream operations. The downstream operations, in particular, are complex due to local regulations in each country where the company operates. The CEO is especially concerned with ensuring regulatory compliance, with the legal and auditing teams tasked with analyzing new downstream operations to ensure adherence to each country’s legal requirements. Additionally, local operating companies should find the architecture appropriate for their needs.

The TOGAF framework recommends identifying and addressing stakeholder concerns early in the ADM process, especially during the Architecture Vision phase (Phase A). Stakeholder analysis is a foundational activity in TOGAF to ensure that diverse concerns are addressed systematically and that all necessary perspectives are considered. This approach helps in aligning the architecture work with organizational needs and in facilitating communication with various stakeholder groups.

Explanation of Option C and Why It is the Best Answer

Stakeholder Analysis:

Stakeholder analysis is essential to identify which stakeholders are involved, their levels of influence and involvement, and their primary concerns. This process allows the architecture team to group stakeholders with common concerns and develop targeted viewpoints for each group.

TOGAF emphasizes stakeholder analysis in Phase A (Architecture Vision) to ensure that the architecture addresses the specific needs of various stakeholder groups, especially in complex, multi-stakeholder environments like the one described in the scenario.

Definition of Concerns and Viewpoints:

After identifying the stakeholders and their concerns, TOGAF recommends defining specific viewpoints that reflect these concerns. This involves documenting these concerns and aligning them with architectural objectives, ensuring each group’s needs are clearly addressed.

Recording these concerns and viewpoints in the Architecture Vision document provides a consolidated, high-level reference that informs future phases and guides architecture work to address stakeholder expectations and regulatory requirements effectively.

Alignment with TOGAF ADM and Stakeholder Management Guidelines:

TOGAF’s Chapter 24 (Stakeholder Management) and Section 24.2 outline the importance of identifying, grouping, and managing stakeholders to ensure the architecture work meets their needs. This is particularly crucial when stakeholders have distinct, potentially conflicting concerns, such as compliance, legal standards, and local operational requirements.

Additionally, by recording this information in the Architecture Vision document (an outcome of Phase A), the team provides a baseline for engaging stakeholders throughout the project, which is critical in high-stakes, regulated environments.

Why Options A, B, and D Are Less Suitable

Option A: While creating a Communications Plan and using a stakeholder power grid matrix are useful actions, they are insufficient for addressing specific stakeholder concerns and viewpoints. This option lacks a structured approach to defining specific viewpoints based on stakeholder concerns, which is a key TOGAF recommendation in managing complex requirements.

Option B: Developing an Organization Map and uniform models could help visualize relationships, but this option misses the critical step of grouping stakeholders by their concerns and defining viewpoints. TOGAF does not recommend a one-size-fits-all model in situations where different groups have distinct needs.

Option D: Identifying stakeholders by category and developing models for each group can help, but identifying 22 specific types of stakeholders and applying a rigid classification misses the nuance required for a more tailored approach. TOGAF instead encourages developing viewpoints based on stakeholder concerns and does not prescribe an exact count or rigid categories of stakeholders, as it may not be suitable for all cases.

TOGAF References Supporting Option C

TOGAF Chapter 24 (Stakeholder Management): Emphasizes the need for identifying and managing stakeholders and their concerns, particularly through defining viewpoints and concerns relevant to each group.

TOGAF Section 7.5.1: Recommends conducting a stakeholder analysis as part of the Architecture Vision phase (Phase A), which includes defining the architecture’s scope, purpose, and high-level requirements aligned with stakeholder needs.

TOGAF Section 7.5.2: Advises on capturing concerns and viewpoints in the Architecture Vision document, which serves as a high-level guide to ensure all stakeholders' requirements are understood and tracked throughout the project.

In conclusion, Option C is the best answer as it aligns with TOGAF’s approach to stakeholder analysis, defining viewpoints based on stakeholder concerns, and documenting these in the Architecture Vision document to address the needs of the Chief Compliance Officer, legal staff, auditors, and local operating companies.

OG0-093 PDF/Engine

Printable Format
Value of Money
100% Pass Assurance
Verified Answers
Researched by Industry Experts
Based on Real Exams Scenarios
100% Real Questions

Get 60% Discount on All Products, Use Coupon: "8w52ceb345"

Which part of the TOGAF standard provides a full description of each architecture phase?

Which of the following best describes the purpose of an Architecture Definition Document?

Summer Special Limited Time 60% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: 8w52ceb345

Please read this scenario prior to answering the questionYou are serving as the Lead Architect...

The Answer Is:

Explanation:

Quick Links