Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

The Open Group OGEA-103 Exam - Topic 5 Question 50 Discussion

Posted by Terrilyn on Jul 05, 2025 at 04:54 PM

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?

Suggested Answer: A

Key aspects of the scenario:

Objective:

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

Challenges:

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

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

CIO's Perspective:

Encouraging an agile approach to architecture development.

Addressing risks and ensuring stakeholder concerns are managed.

Areas for Evaluation:

AI usage by staff and impact on workflows.

Patient experience enhancement via AI.

New workplace platforms and tools powered by AI.

Option Analysis:

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

Pros:

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

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

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

Cons:

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

Option 2: Creation of a Communications Plan

Pros:

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

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

Cons:

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

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

Pros:

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

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

Cons:

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

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

Pros:

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

Cons:

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

Recommended Answer:

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

Reasoning:

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

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

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

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


Get Premium OGEA-103 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
31 comments · newest first
TR
Tresa 10 months ago
Wait, are we really ready for such a big change?
JA
Jackie 10 months ago
Not sure if we can really manage AI risks effectively...
BI
Billy 10 months ago
I think a Communications Plan is more crucial right now.
SA
Santos 10 months ago
Totally agree, regular feedback is key to success!
GR
Gracia 11 months ago
Sounds like a solid plan to start with stakeholder analysis!
DO
Donte 11 months ago
I wonder if creating a set of business models is too rigid. It might limit flexibility in how we implement AI across different divisions.
NO
Noelia 11 months ago
I practiced a similar question where we had to create models for different architectures. It feels like a good approach to ensure compliance and address stakeholder concerns.
SA
Santos 11 months ago
I'm not entirely sure, but I think a Communications Plan could help address the worries of the top managers. It might clarify how AI will be integrated.
EV
Evan 11 months ago
I remember we discussed the importance of stakeholder analysis in our last study session. It seems like a solid first step to understand everyone's concerns.
AR
Arleen 12 months ago
This is a tough one, but I think option A is the way to go. Stakeholder analysis and an architecture vision document will be crucial to getting everyone on the same page and addressing their concerns upfront. Plus, the progressive development approach should help us manage the risks and get regular feedback. I feel pretty confident about this approach.
LO
Loreta 12 months ago
Okay, I think I've got a handle on this. Based on the TOGAF standard, I'd recommend starting with a stakeholder analysis and architecture vision document. That will help us clearly define the key stakeholders and their concerns, which we can then address in the subsequent architecture development. Mitigating risk should also be a top priority given the company's reservations about AI.
IS
Isabella 1 year ago
Hmm, this is a tricky one. There are a lot of different factors to consider, like the company's existing architecture governance, the CIO's preference for agile approaches, and the concerns around AI implementation. I'm not entirely sure which approach would be best, but I'll need to weigh the pros and cons of each option carefully.
LE
Leota 1 year ago
This seems like a complex scenario with a lot of moving parts. I'll need to carefully read through the details to make sure I understand the key stakeholders, their concerns, and the overall goals of the project. I think starting with a stakeholder analysis and architecture vision would be a good first step.
KI
Kip 1 year ago
I see your point, Joni. Let's see what others think before making a final decision.
DE
Denny 1 year ago
Option D sounds like a recipe for bureaucratic nightmare. Trying to fit everything into a fixed set of business models? No thank you, I'll take the flexibility of option A any day.
BR
Brittni 1 year ago
↳ replying to Denny
I agree, option A allows for progressive development and regular feedback.
NO
Nobuko 1 year ago
↳ replying to Denny
Option D sounds too rigid. I prefer the flexibility of option A.
WI
Willard 1 year ago
Hah, I bet the CIO is just hoping for a magic AI solution to solve all their problems. Option C looks like the most thorough approach, covering all the necessary architecture models and formal reviews.
AN
Annabelle 1 year ago
↳ replying to Willard
C) You recommend that models be created for the Draft Business, Data, Application, and Technology Architectures. These can be used to ensure that the system will be compliant with the local regulations for each division. Together with the problem description, and requirements, this ensures that all the necessary data and detail is addressed. A formal review should be held with the stakeholders to verify that their concerns have been properly addressed by the models.
CA
Candra 1 year ago
↳ replying to Willard
B) You recommend that a Communications Plan be created to address the key stakeholders, that is the most powerful and influential partners. This plan should include a report that summarizes the key features of the architecture with respect to each location and reflects the stakeholders' requirements. You will check with each key stakeholder that their concerns are being addressed. Risk mitigation should be explicitly addressed as a component of the architecture being developed.
TO
Tommy 1 year ago
↳ replying to Willard
A) You recommend that an analysis of the stakeholders is undertaken. This will allow the architects to define groups of partners (the stakeholders) who have common concerns and include development of a Stakeholder Map. The concerns and relevant views should then be defined for each group and recorded in the Architecture Vision document. To mitigate risk, you include a requirement that there be progressive development of the target architecture to ensure there is regular feedback.
JO
Joni 1 year ago
That's a valid point, Tamekia. But I still think option A provides a more comprehensive approach.
TE
Tegan 1 year ago
I'm not sure if option B is the best choice here. Focusing only on the most powerful and influential stakeholders might leave out important voices. I'd lean more towards option A, which takes a broader stakeholder analysis approach.
SE
Selma 1 year ago
↳ replying to Tegan
I agree, Option A's approach of analyzing all stakeholders is more comprehensive and ensures all concerns are addressed.
DE
Deane 1 year ago
↳ replying to Tegan
Option B might be risky as it focuses only on key stakeholders. Option A seems more inclusive with stakeholder analysis.
TA
Tamekia 1 year ago
I'm not sure, I think option C could also be a good choice. Creating models for different architectures could be beneficial.
DA
Dana 1 year ago
This seems like a complex scenario, but I think option B is the best approach. A communication plan that addresses the key stakeholders' concerns and regularly checks in with them is crucial for mitigating risks.
MA
Matthew 1 year ago
↳ replying to Dana
I agree, keeping stakeholders informed and addressing their concerns is key to success.
RO
Rozella 1 year ago
↳ replying to Dana
Option B is a good choice. Communication with key stakeholders is essential.
KI
Kip 1 year ago
I agree with you, Joni. Option A seems to address the stakeholders' concerns effectively.
JO
Joni 1 year ago
I think option A is the best answer.
0/2000 characters

Save Cancel