You are working as an Enterprise Architect at a large company. The company runs many retail stores as well as an online marketplace that allows…

This set of principles provides the most comprehensive guidance for the described transformation. "Maximize Benefit to the Enterprise" directly addresses the CEO's and CIO's goals of growth and cost savings. "Common Use Applications" aligns with the strategy to replace duplicated systems with a single standard retail management system. "Data is an Asset" is crucial given the central, data-driven AI inventory system. "Responsive Change Management" is essential for managing the complexity of a large-scale merger and the rollout of new technology to a diverse workforce. Finally, "Technology Independence" guides the selection of new standardized systems to ensure future flexibility and avoid vendor lock-in.

A. "Compliance with the Law" and "Data Security" are general, ongoing concerns, not the primary drivers specifically mentioned for this business transformation initiative.

B. This option lacks a principle that captures the core business motivation (growth and savings) and fails to address the significant organizational change management challenge of the merger.

C. While "Ease of Use" is relevant to the device rollout, this option omits the overarching business driver ("Maximize Benefit") and the critical change management aspect of the integration.

1. The TOGAF® Standard

Version 9.2

Chapter 23

"Architecture Principles": This chapter provides the template and examples for architecture principles. The principles listed in the correct answer are representative of the different categories needed to guide a major transformation:

Business Principle: "Maximize Benefit to the Enterprise" (Section 23.6.1).

Data Principle: "Data is an Asset" (Section 23.6.2).

Application Principle: "Common Use Applications" (Section 23.6.3).

Technology Principle: "Technology Independence" (Section 23.6.4).

While "Responsive Change Management" is not an explicit example

TOGAF emphasizes that principles must be tailored to the enterprise's specific needs

and this principle directly addresses the merger context described in Phase H (Architecture Change Management).

2. Ross

J. W.

Weill

P.

& Robertson

D. C. (2006). Enterprise architecture as strategy: Creating a foundation for business execution. Harvard Business Press. This foundational text

widely used in university curricula (e.g.

MIT Sloan)

establishes the direct link between architecture principles like application and data standardization ("Common Use Applications"

"Data is an Asset") and achieving key business outcomes such as cost savings and agility

which aligns with the "Maximize Benefit to the Enterprise" principle. (See Chapter 3: "Building the Foundation One Project at a Time").

3. MIT Center for Information Systems Research (CISR)

Working Paper No. 379

"Enterprise Architecture: The Key to Successful Corporate Strategy": This paper discusses how a mature EA practice uses principles to guide technology decisions to meet business objectives. It emphasizes that principles must connect IT decisions to business value

supporting the selection of principles that directly reflect the strategic goals of growth and efficiency mentioned in the scenario.