OG0-093 · Question #201
Scenario Please read this scenario prior to answering the question You are serving as the Lead Enterprise Architect at a major supplier in the automotive industry. The company is headquartered in…
The correct answer is C. Technology Independence, Data Trustee, Information Management is Everybody's Business, IT. The scenario describes a company with disparate systems across multiple plants leading to process waste, aiming to replace them for efficiency. The correct principles address technology standardization, data ownership, shared information responsibility, and IT accountability…
Question
Scenario Please read this scenario prior to answering the question You are serving as the Lead Enterprise Architect at a major supplier in the automotive industry. The company is headquartered in Cleveland, Ohio with manufacturing plants across the United States, Brazil, Germany, Japan and South Korea . Each of these plants has been operating its own planning and production scheduling systems, as well as custom developed applications that drive the automated production equipment at each plant. The company is implementing lean manufacturing principles to minimize waste and improve the efficiency of all of its production operations. During a recent exercise held for internal quality improvement, it was determined that a significant reduction in process waste could be achieved by replacing the current planning and scheduling systems with a common Enterprise Resource Planning (ERP) system located in the Cleveland data center. This central system would provide support to each of the plants replacing the functionality in the existing systems. It would also eliminate the need for full data centers at each of the plant facilities. A reduced number of IT staff could support the remaining applications. In some cases, a third-party contractor could provide those staff. The Enterprise Architecture department has been operating for several years and has mature, well-developed architecture governance and development processes that are strongly based on TOGAF 9. At a recent meeting, the Architecture Board approved a Request for Architecture Work sponsored by the Chief Engineer of Global Manufacturing Operations. The request covered the initial architectural investigations and the development of a comprehensive architecture to plan the transformation. The Common ERP Deployment architecture project team has now been formed, and the project team has been asked to develop an Architecture Vision that will achieve the desired outcomes and benefits. Some of the plant managers have expressed concern about the security and reliability of diving their planning and production scheduling from a remote centralized system. The Chief Engineer wants to know how these concerns can be addressed. Refer to the Scenario [Note: You should assume that the company has adopted the example set of principles that are listed and defined in TOGAF 9, Section 23.6.] One of the earliest initiatives in the Enterprise Architecture program was the definition of a set of architecture principles. These now need to be updated to address the concerns raised. You have been asked to select a set of principles most appropriate for guiding the team to define a robust solution. Based on TOGAF 9, which of the following is the best answer?
Options
- ACommon-use Applications, Control Technical Diversity, Ease of Use, Interoperability, Data is
- BBusiness Continuity, Common-use Applications, Maximize Benefit to the Enterprise, Data is
- CTechnology Independence, Data Trustee, Information Management is Everybody's Business, IT
- DService-orientation, Responsive Change Management, Business Continuity, Data is Accessible,
How the community answered
(36 responses)- A14% (5)
- B3% (1)
- C75% (27)
- D8% (3)
Why each option
The scenario describes a company with disparate systems across multiple plants leading to process waste, aiming to replace them for efficiency. The correct principles address technology standardization, data ownership, shared information responsibility, and IT accountability, which are key for successful enterprise-wide system replacement and lean manufacturing implementation.
While Common-use Applications, Control Technical Diversity, and Interoperability are relevant, Ease of Use and Data is Accessible are more specific benefits or characteristics rather than foundational enterprise architecture principles for managing an entire transformation. Ease of Use and Data is Accessible describe outcomes, not the underlying guiding principles for technology and information management. Common-use Applications and Control Technical Diversity are good principles for this scenario, but the set is less comprehensive than C.
Business Continuity is a critical principle but not the primary driver for addressing disparate systems causing process waste, which is the scenario's focus. Maximize Benefit to the Enterprise is a very high-level and generic principle that doesn't provide specific guidance on *how* to achieve benefits in the context of integrating diverse systems. Business Continuity is an important principle, but the scenario's primary emphasis on waste reduction and efficiency points to a need for more direct principles for system replacement and integration.
Technology Independence ensures that new systems can be selected without vendor lock-in, crucial for replacing diverse legacy systems efficiently. Data Trustee and Information Management is Everybody's Business establish clear ownership and shared responsibility for data quality and integrity across the enterprise, which is vital for consolidating information from various plants. IT is Accountable ensures that the IT function has clear responsibility for delivering the integrated and efficient systems required to achieve the company's lean manufacturing goals.
Service-orientation and Responsive Change Management are valuable principles, but they focus on technical design and agility rather than the foundational aspects of data governance, technology management, and enterprise-wide accountability for information that are central to the scenario's problems. Data is Accessible describes an outcome, not a guiding principle for enterprise management.
Concept tested: Enterprise Architecture Principles - Technology and Information Management
Source: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap20.html
Topics
Community Discussion
No community discussion yet for this question.