A superior star schema strategy

A form of data lake that automates data acquisition and initial data qualityprocessing

A metadata repository

A way of sewing together different data concepts into a single data warehouse

Just another data warehouse with no distinguishing features

By creating a map of where the enterprise data is located in IT systems.

By providing a Business Glossary based look up facility for data definitions.

By ensuring that data is properly categorized, owned, understood, defined, documented and controlled

By highlighting the challenges of multiple data definitions within the enterprise

By performing an as-is data audit

[1] Data Flow Design [2] Data Context Diagram

[1] Enterprise Data Model [2] Architecture Diagram

[1] Enterprise Data Model [2] Data Flow Design

[1] Enterprise Data Model [2] Data Context Diagram

Hierarchical

Data structure

Warped

Business rules for managing data

Content

None of the above

Exercise of authority, formalization of reporting lines, implementation of supporting technology, definition of common glossaries

Alignment of Business and IT strategies, definition of data standards, implementation of Data Governance and metadata software tools

Agreed models for decision making and decision rights, defined authority and escalation paths, structures for assigning accountability and delegating responsibility, alignment with business objectives

Agreed architectures, transparent policies, shared language, effective tools, delegated authority, stewardship

Agreed models for data design and definition, decision rights regarding standards and controls, delegation of accountability

Embedded

Flexible

Measures

Rigid

Independent responsibility

Sustainable

Logical model

Physical model

Conceptual model

Subject Area model

FALSE

TRUE

Managed outside of the repository and only the results of data quality assessments stored as rules metadata

Documented consistently, tied to business impact, backed by data analysis, and accessible to all data consumers

Organized with metrics so the data stewards can review the data and see what rules apply

Focused on rules that can be integrated into application services

Focused on managing relationships that have gone wrong in the past and may go wrong in the future

A dictionary that is active 24 hours a day

Any data dictionary is considered active because it has codes and values used in the enterprise

An integrated dictionary that is managed automatically by the database management system software

A dictionary that allows users to enter data in an 'active' or open manner

A dictionary that can be activated by the metadata team

Align data architecture with enterprise strategy and business architecture

Provide a standard business vocabulary for data and components

Outline high-level integrated designs to meet these requirements.

Integrate with overall enterprise architecture roadmap

Define the current state of data in the organization.

Express strategic data requirements

Size, Speed and Sensitivity

Volume, Variety and Velocity

Direction, Depth and Details

Expansive, Engaged and Enormous

Complexity, Compliance and Completeness

TRUE

FALSE

Create a matching separate code table

Create a master shared code table

None of the above

Program integration by joining tables

Embed rules or valid codes into the appropriate object’s definition.

Roadmap Development

Consistency rules

Duplicate identification match rules

Match-merge rules

Match-split rules

Match-link rules

All of the above