Enterprise Architecture and Data Governance Chapter 2

Enterprise architecture and data governance are not interrelated.

Effective data governance only ensures data consistency.

Master Data Management (MDM) does not require strong data governance.

Data governance is only concerned with data security.

Cultures of distrust between technology and employees can lead to effective data governance.

Data governance is not important for reducing legal risks and improving financial health.

Adding new apps or data analytics on an as-needed basis is sufficient for ensuring compatibility with existing systems.

A detailed plan for expansion is necessary when building a simple cabin in a remote area.

Enterprise architecture is a one-time process of creating and maintaining IT systems.

Enterprise architecture is primarily focused on solving business strategy execution challenges.

Enterprise Architecture (EA) is not necessary for managing big data, content from mobiles and social networks, and data in the cloud.

The primary purpose of EA is to reduce IT system complexity.

The relationship between complexity and planning is more difficult to see in physical systems such as skyscrapers and transportation systems.

A well-thought-out growth plan is not necessary for building a simple, single-user, non-distributed system.

EA is a roadmap for controlling the direction of IT investments.

Methodologies can solve people problems.

EA is only concerned with IT systems and not with business operations.

The four subarchitectures of EA are not part of the overall IT capabilities.

Technical architecture is the organization and access of enterprise data

EA helps align IT capabilities with business strategy to reduce IT costs

The four components of Enterprise Architecture are Business Architecture, Application Architecture, Data Architecture, and IT Economics

EA provides a short-term view of a company’s processes, systems, and technologies

EA reduces the risk of buying or building systems and enterprise apps that are compatible and inexpensive to maintain and integrate

EA increases IT costs and decreases productivity by limiting access to information

Enterprise Architecture begins by identifying the organization's current state.

Data Governance is only concerned with structured data.

Data is only used in an organization for running the business.

Enterprise Architecture guides and controls physical infrastructure investments only.

Data Governance is optional for data-driven strategies.

Enterprise Architecture sets priorities for changes based on technical feasibility.