The Open Group TOGAF Enterprise Architecture Part 2 OGEA-102 Exam Questions

Page: 1 / 14
Total 34 questions

Want more questions? Get Premium Access.
()

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

AControl Technical Diversity will help by standardizing technology platforms as
part of the integration process. This will be vital for standardizing the app
integration for digital orders with the back-office systems, and will reduce
complexity and costs during integration. Data Trustee will establish owners to
manage the shared data across the company, thereby assuring data quality.
Ease-of-Use is needed to make sure that new user interfaces for the apps
continue to be easy to use.

BPrimacy of Principles will make sure that the same principles apply to both
organizations of the newly merged operation, creating consistency across
locations. Data as an Asset is critical. Since you're maintaining separate mobile
apps but consolidating back-end systems, treating data as an asset becomes
essential. This principle helps ensure that customer data, and inventory
information from both brands are properly integrated and managed.
Technology Independence is important when consolidating the back-office
applications and order processing systems.

CCompliance with the Law makes sure that all company activities comply with
relevant laws and regulations. This principle provides the foundation for
ensuring the merger meets all legal requirements. Requirements-Based
Change will make sure that when combining systems, changes to applications
and technology are only made if required by business needs. Responsive
Change Management focuses on the speed needed to achieve the goals set
by the leaders for a quick merger. We are committed to quickly blending the
companies as planned.

DService orientation will speed up the merger and make it easier to integrate
systems while maintaining business operations. Maximize Benefit to the
Enterprise will make sure that merger decisions prioritize the overall benefit to
the combined company. Common Use Applications across the merged
company is preferred over the use of similar or duplicative applications for
certain parts of the company. This help supports the goal of merging back-
office systems to reduce duplication.

Answer : D

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.