Master and Reference Data

Management
Contents

• Key Points and Master Data Management (MDM)

• MDM Capabilities
• Characteristics, Alignment, and Considerations
• Reference and Master Data Management in NDMO
• Discussion & Questions
• Homework

1
Key Points and Master
Data Management (MDM)
Reference and Master Data
Management
Data Management 2%
Big Data 2%
Data Architecture 6%
Document & Content Management 6%
Data Ethics 2%
Data Governance 11%
Data Integration & Interoperability 6%
Master & Reference Data Management 10%
Data Modelling & Design 11%
Data Quality 11%
Data Security 6%
Data Storage & Operations 6%
Data Warehousing & Business Intelligence 10%
Metadata Management 11%
3
Reference and Master Data
Management

 Where do Reference and Master

Data Management sit on the DAMA
DMBoK Wheel?

4
 Reference and Master Data

Reference and Definition: Managing shared data to meet organizational goals, reduce risks associated with
data redundancy, ensure higher quality, and reduce the costs of data integration.

Master Data Goals:

1. Enable sharing of information assets across business domains and applications within an organization.

Management
2. Provide authoritative source of reconciled and quality-assessed master and reference data.
3. Lower cost and complexity through use of standards, common data models, and integration patterns.

Business
Drivers

Inputs: Activities: Deliverables:

• Business Drivers 1. Identify Drivers and Requirements • Master and
• Cross Functional (P) Reference D ata
1. Validate Data Definitions (C)
Requirements Requirements
2. Evaluate and Assess Data Sources
• Industry (P) • Data Models and
Standards 3. Define Architectural Approach (D) Integration Patterns
• Data Glossary 4. Model Data (D) • Reliable Reference
• Purchased Data 5. Define Stewardship and and Master Data
Maintenance Processes (C)
and/or O pen • Reusable Data
6. Establish Governance Policies (C)
Data and Code 7. Implement Data Sharing/Integration Services
Sets Services (D,O)
• Business Rules 1. Acquire Data Sources for Sharing
2. Publish Reference and Master Data Consumers:
Suppliers: • Master Data Analysts
• Subject Matter P articipants: • Data Integrators
Experts • Data Analysts • D ata Architects
• Data Stewards • Data Modelers • Application Users
• Application • Data Stewards • Application
D evelopers • Data Integrators D evelopers
• D ata Providers • D ata Architects • Solution Architects
• Business Analysts
• Infrastructure
• Data Q uality Analysts
Systems Analysts Technical
Drivers

T echniques: Tools: Metrics:

• Conditions-of-use • Data Modeling Tools • D ata Quality and
agreements • Metadata Repositories Compliance
• Business key cross • Data Profiling and Q uality • D ata C hange Activity
• D ata C onsumption and
references Tools
Services
• Processing Log analysis • Data Integration Tools • D ata Sharing Availability
• MD M Application Platforms • D ata Steward C overage
• Data Sharing/Integration • D ata Sharing Volume
Architecture and Utilization
(P) Planning, (C) Control, (D) Development, (O) Operations
5
 KEY POINTS

• Shared reference and master data belongs to the organization, not to a particular
application or department
• Reference and Master Data Management is an ongoing Data Quality improvement
program; its goals cannot be achieved by one project alone
• Business data stewards are the authorities accountable for controlling reference data
values. Business data stewards work with data professionals to improve the quality of
reference and master data
• Golden data values represent the organization’s best efforts at determining the most accurate,
current, and relevant data values for contextual use. New data may prove earlier assumptions
to be false. Therefore, apply matching rules with caution, and ensure that any changes that
are made are reversible
• Replicate master data values only from the database of record
• Request, communicate, and, in some cases, approve of changes to reference data values
before implementation

6
WHAT IS EVENT/TRANSACTION DATA?

E V E N T D ATA E X A M P L E :
“Bob bought a Twix bar from Morrison's on Monday, Jan. 3rd at 4 p.m.
and paid using cash.”
WHO WHAT WHERE WHEN HOW QUANTITY AMOUNT
Bob Smith Twix bar Morrison's, Bath 16:00 Monday Cash 1 £0.60
January 3rd, 2011

CUSTOMER PRODUCT VENDOR DATE PAYMENT QUANTITY AMOUNT

CODE CODE CODE METHOD
BS005 CONF101 WMBATH 2011-01-03 16:00 CASH 1 £0.60

7
7
 About EVENT DATA

Includes information: Does not include

AKA Transaction data
Identifying the nouns that information:
Describes an action (a verb) were involved in the event Describing the nouns:
E.g. “buy” (the
who/what/where/when/how • Bob is female, aged 25, and
May include and maybe even the why): works for British Airways
measurements about the
action: • Bob Smith • Monday, Jan. 3rd, 2011 is a
bank holiday
• Twix bar
• Quantity bought • The address of Morrisons
• Morrisons, Bath Bath is: York Place, London
• Amount paid
• 16:00 Monday, Jan. 3rd, 2011 Road, Bath, BA1 6AE.

• Cash • That Twix is a special offer

200g jumbo bar

8
WHAT IS …

MASTER DATA? MASTER DATA MANAGEMENT (MDM)?

• Defines and describes the nouns (things) of the • The ongoing reconciliation and
business. maintenance of master data.
e.g., Customer, Risk, Branch, Loan, Field, Well,
Rig, Product, Store, Therapeutic Area, Adverse • Control over master data values to enable
Event, etc.
consistent, shared, contextual use across
• Data about the “things” that will participate in systems, of the most accurate, timely,
events. and relevant version of truth about
• Provides contextual information about events/ essential business entities.
transactions. (DAMA)
• Stored in many systems • Comprises a set of processes and tools
• Packaged Systems that consistently defines and manages
the non-transactional data entities of an
• Line-of-Business Systems
organization.
• Spreadsheets (Wikipedia)
• SharePoint Lists, etc.

9
9
MDM BUSINESS DRIVERS
Meeting
Managing the
Organizational Managing Data
Costs of Data Reducing Risk
Data Quality
Requirements Integration

Multiple business Data The cost of

areas in an inconsistencies, integrating new Master data can
organization need quality issues, and data sources into enable
access to the same gaps lead to simplification of
an already
data sets, with
incorrect complex data sharing,
confidence that the
data sets are decisions, lost environment is interoperability,
complete, current, opportunities, and higher without and integration.
and consistent. inefficiencies. master data.

“Master” data often

forms the basis of Master Data
these data sets Management Master Data
A master data
(e.g., determining reduces these Management
reduces variation architecture can
whether an analysis risks by enabling a reduce costs and
includes all consistent in how critical
customers risk associated
representation of entities are
depends on having with a complex
the core, shared defined and
a consistently environment.
entities critical to identified.
applied definition of the organization.
a customer ).
10
MDM Architectures

1. REPOSITORY

2. REGISTRY
A key difference is the
Standard number of fields that
“Hub” are stored centrally
3. HYBRID
architectures
4. VIRTUALIZED

11
EXAMPLE: CUSTOMER

Customer First name Last Date of birth Preferred Preferred Credit rating Occupation Car
code name delivery delivery
address line 1 address post
code

JBS005 Bob Smith 1985-12-25 Royal Crescent BA1 7LA A Information Audi
Architect R8

IDENTIFIERS

CORE FIELDS

ALL FIELDS

12
EXAMPLE: CUSTOMER

Customer First Last Date of birth Preferred Preferred Credit Occupation Car
code name name delivery address delivery address rating .…
line 1 post code
BS005 Bob Smith 1985-12-25 Royal Crescent BA1 7LA A Information Audi R8
Architect

ALL FIELDS
IDENTIFIERS
Repository

CORE
FIELDS
CORE FIELDS Hybrid

IDENTIFIERS
Registry
ALL FIELDS

NONE
Virtualised

13
 System(s) of Origin

DATA OWNERS

To store data models and

SYSTEMS OF ENTRY MASTER DATA ENVIRONMENT metadata
CONSUMING SYSTEMS

SYSTEM METADATA SYSTEM

CATALOG
DATA DATA
SOURCING DISTRIBUTION
SYSTEM SYSTEM
SYSTEM OF
RECORD
“Best version”
SYSTEM SYSTEM
DATA QUALITY USER INTERFACE

Standardize, De-duplicate, To highlight issues and

Merge, Enrich, etc. enable them to be fixed

DATA STEWARDS

Golden Record

MASTER DATA ENVIRONMENT System of Record

(Database of Record)

14
 DATA OWNERS

SYSTEMS OF ENTRY CONSUMING SYSTEMS

MASTER DATA ENVIRONMENT

SYSTEM ACTIVE PUSH METADATA ACTIVE PUSH SYSTEM

Webservices Webservices
CATALOG
BATCH SCHEDULE BATCH SCHEDULE
D ATjob
ETL A D
ETL ATjobA
ES/IODVUcaRchCeIrNefrGesh
DISTREIIIB/DUVTION
SYSTEM SYSTEM
PULL ON DEMAND SYSTEM OF PULL ON DEMAND
Webservices Webservices
SQL queries RECORD SQL queries

SYSTEM SYSTEM
DATA QUALITY USER INTERFACE

DATA STEWARDS

MASTER DATA ENVIRONMENT: METHODS OF MOVING DATA

15
TYPICAL MDM COMPONENTS

System X CONFLICT System 1

GOVERNANCE
RESOLUTION

TRANSFOR- CACHING &

MATION SYNCHRO-
NIZATION

SUPER-
DATA
SESSION MASTER MODELING
CHAINING DATA
(e.g. Customer)

DATA
DISTRIBUTION
QUALITY

ACCESS SOURCING
System 3 System 2

16
MDM Capabilities
 DATA SYNCHRONIZATION
DATA INTEGRATION MASTER DATA “HUB” DATA DELIVERY
& ACQUISITION

MDM ARCHITECTURE

INTEGRATION
APPLICATION
MASTER DATA SERVICES
DATA DISCOVERY & INTAKE
MASTER DATA MODELS

REFERENCE DATA

DATA QUALITY

INTERFAC
CONSOLIDATIO

CONTROL
METADATA MANAGEMENT

ACCESS

E
BUSINESS RULES

USE

SERVICES
N

BUSINES
R
HIERARCHY MANAGEMENT

S
MASTER DATA “REPOSITORY”

OPERATIONAL MANAGEMENT/DATA GOVERNANCE & STEWARDSHIP

TYPICAL MDM CAPABILITIES

18
1. MASTER DATA “HUB”

• The Master Data Hub* infrastructure supports:

• Master data models, for all deployed concepts

• Metadata Management, supports syntax variety across source data

sets

• May also include Reference Data Management (e.g., Currency

codes, ISO Country codes, Project Status codes)

• Business Rules Management, associated with consistency and

completeness

• The MDM Architecture implements the target core repository

model for each master data concept that will be deployed

• Some vendor products come packaged with data models that

can be extended

• Some vendors expect implementers to integrate their own

models within the architecture

* Does NOT always have to be a physical/centralized “hub” 19

2. DATA INTEGRATION AND ACQUISITION

• Data integration and data acquisition capabilities including:

• Data discovery including connectors to different data sources, together with

extract, transform, and load and other DI capabilities

• Consolidation, identity resolution, and matching as a built-in component or as

an add-on from another vendor

• Data Quality components capable of:

• Data transformation

• Data Quality validation

• Parsing and standardization

• Data cleansing and loading

• Data discovery to assess quality and metadata discovery (some MDM tool
vendors either bundle it or offer it as a separate product)

• Some vendors bundle their MDM platforms with data integration and
Data Quality/cleansing capabilities, while other vendors have
partnerships to provide these functions.

20
3. MASTER DATA SERVICES

• Data delivery services to obtain master data out of the “hub”

• Standard data object lifecycle services such as:

• “create a customer record”

• “update product price”

• For each modeled master object, basic master data services should be
configured to:

• create

• read

• update and delete

• either the object itself or its associated attributes

• MDM products may provide either a service library or the means for
creating master data services as master object models are integrated
or enhanced

21
4. DATA DELIVERY

• Delivery to consuming applications of the information built on the

Master Data Services

• Added-value data delivery reducing replication of

common functions implemented multiple times across different
applications such as:

• “create a new customer account” or

• “look up product”

• Basic business services can provide more complex business services,

implemented once and used multiple times

• A standardized interface will help in transitioning existing applications

to use the master data system by facilitating application
interoperability

22
5. ACCESS CONTROL

• Typical IDAM capabilities frequently leveraging LDAP (e.g., Active

Directory) or other O/S capabilities.

• This component is not typically seen as a

“value-added” component of an MDM product.

• Access control is required as the unified master data objects are

exposed to a wider variety of applications and corresponding users.

23
6. SYNCHRONIZATION

• Across the range of core MDM repository

implementations (from Registry to Transaction
hub), there are different requirements for
synchronizing data from the numerous source data systems.

• For reporting purposes, a daily synchronization may be sufficient, while

certain operational activities may demand immediate coherence across
all views of master data.

• Vendors should be able to describe how their product synchronizes

data across the enterprise and show how to adjust the frequency and
monitor the guarantees of consistency.

24
7. DATA QUALITY, GOVERNANCE, AND OPERATIONS

• Data Quality must be continuously monitored to verify acceptability.

Also, there must be operational governance and stewardship services
to support:

• Inspection

• Root Cause Analysis

• Data Correction

• Propagation of corrections across the master data environment

• Data Quality Reporting

• Data Governance Reporting

• Inspection of Data Quality issues is closely tied to the Data Quality

capabilities of the data integration layers and to the business rules
managed within the master data hub.

• When issues are identified due to a false positive merge or a false

negative non-merge, interfaces should allow for manual remediation.

25
 MASTER DATA MATCH RULES

Three primary scenarios:

1. Duplicate identification match rules

Focus on a specific set of fields that uniquely identify an entity and identify merge
opportunities without taking automatic action. Business data stewards can review
these occurrences and decide to take action on a case-by-case basis.

2. Match-merge rules
Match records and merge the data from these records into a single, unified,
reconciled, and comprehensive record. If the rules apply across data sources, create
a single unique and comprehensive record in each database.

3. Match-link rules
Identify and cross-reference records that appear to relate to a master record
without updating the content of the cross-referenced record. Match-link rules are
easier to implement and much easier to reverse.
Rules around the matching, merging and linking of data from multiple systems about
the same person, group, place or thing.

26
MDM … A HUB IS NOT THE ONLY WAY
MIDDLEWARE SYNCHRONISATION LAYER SYNCHRONISATION LAYER

LEGAC LEGAC
ERP CRM ERP CRM
Y Y

SINGLE DATA
MASTER DATA CONTRIBUTORS SOURCE

Synchronized Master Application Specific Master

• Multiple operational systems acting • One operational system as

as master data contributors master data provider
• Well suited to enterprises where
• Real-time information availability
data is primarily stored in a
• Well suited to enterprises where data single source system
is stored across multiple source • Support from many enterprise
systems vendors
• Well suited to low data velocity
operations

27
MDM … A HUB IS NOT THE ONLY WAY
INDUSTRY
OPERATIONAL SPECIFIC
DATA-STORE MASTER
E.G., CUSTOMER
MASTER

SYNCHRONIZATION LAYER
EXTRACT-TRANSFORM-LOAD
SYNCHRONIZATION LAYER

ERP CRM LEGACY

ERP CRM LEGACY

Master Overlay
Hub-Based Master

• Operational Hub structure that overlaps • Stand-alone, application-neutral master

operational and analytical environments data
• Supports concept of an enterprise data • Industry-specific data model
warehouse
• Well suited to vertical industries in
• Multiple systems acting as data providers
aligning front-office and back-office
• Appropriate for low data latency and velocity systems in real time
operations
• Requires careful Data Quality Management • Now most often seen for reference data

28
MDM … A HUB IS NOT THE ONLY WAY
MASTER
DATA
SAP 1 DSL LEGACY

Non DV (FEDERATED) MASTER DATA

SAP 2 MESSAGING
SAP

ORACLE …..
SAP ….. …..
SAP 3 DW CRM ….. …..
SIEBEL …..

PACKAGES DATABASES FILES XML

REPORTS
Data Virtualization (Federated) Master Data
Real-Time Data Movement
• Virtual MDM hub created via DV layer
• Data is moved between the various
systems using a messaging • DV layer informed from Logical Data Model
integration hub or ESB • Powerful data integration to access multiple
• Data movement is done in real time disparate systems
• Movement of data can be one or two • Rapid time to solution
ways as required
• Outstanding prototyping, proof of value
approach
• Compliments other data integration
approaches
29
MASTER
MASTER DATA
DATA
SHARING
SHARING
ARCHITECTURE
ARCHITECTURE
(EXAMPLE)
(EXAMPLE)

30
MASTER DATA SHARING ARCHITECTURE (EXAMPLE)

Each master data subject area typically has its own Transaction Hub, applications interface with the hub to access and
update master data.
system of record. + Master data exists within the Transaction Hub and not within any other
applications.
Example shown hub-and-spoke architecture for master data.
+ Transaction Hub is the system of record for master data.
The master data hub handles interactions with spoke items such as source + Transaction Hubs enable better governance and provide a consistent
systems, business applications, and data stores while minimizing the source of master data.
number of integration points. -However, it is costly to remove the functionality to update master data
from existing systems of record.
A local data hub can extend and scale the master data hub. -Business rules are implemented in a single system … the Hub.

Registry is an index that points to master data in the various systems of Consolidated approach is a hybrid of Registry and Transaction Hub.
record. + Systems of record manage master data local to their applications.
+ Systems of record manage master data local to their applications. + Master data is consolidated within a common repository and made
+ Access to master data comes from the master index. available from a data-sharing hub, the system of reference for master
+ A registry is relatively easy to implement because it requires few data.
changes in the systems of record. + Eliminates the need to access directly from the systems of record.
-Often, complex queries are required to assemble master data from + Consolidated approach provides an enterprise view with limited impact
multiple systems. on systems of record.
-Moreover, multiple business rules need to be implemented to address -However, it entails replication of data.
semantic differences across systems in multiple places. -Latency between the hub and the systems of record.

31
KEY PROCESSING STEPS FOR MDM

Data Model Data Acquisition Data Validation, Data Sharing and

Entity Resolution
Management Standardization, and Stewardship
Enrichment

32
 SINGLE-Domain and Multi-Domain MDM

SINGLE-DOMAIN MULTI-DOMAIN
• E.g., Product (PIM), Customer (UCM), Vendor, • Highly configurable MDM solutions
Laboratory (LIM) • Informed by data model
• Incorporate specific “domain” features …
• Fewer specific data domain features
• House holding
• Address chaining
• Interfaces to mainstream apps
• Company hierarchies
• Results in fewer MDM solutions throughout the
enterprise
• Tailored data matching (deterministic or probabilistic)

• Engineered to exploit third-party data sources

• GB PAF, USPS Zip+4, Electoral Roll, CCJ …
• D&B, Liquidations, Companies House …
• CAS, COSHH …

• Interfaces to domain LoB apps

33
 IMPLEMENTATION: OPERATIONAL VS. ANALYTICAL MDM

OPERATIONAL ANALYTICAL
• MDM (usually a hub) created for use in data warehouse/
Business Intelligence solutions
• MDM (whatever is most appropriate architecture) created for
• Data integration (e.g., ETL) from source systems still required
use in LIVE operational Business solutions
• Data cleanse, consolidate, merge, de-duplicate, enrich, etc. still
• Data integration (e.g., ETL) from source systems essential required
• Data cleanse, consolidate, merge, de-duplicate, enrich, etc. • Master data used for analytical purposes to ensure consistency of
essential analyses, findings, etc.

• Master data is used by the live operational line-of-business • Master data NOT used by live operational line-of-business
solutions, therefore operational systems do not see any
solutions
benefits of MDM approach
• Essential to address business rules (such as survivorship, • NOT essential to address business rules (such as survivorship,
channels, attribute federation, Data Governance) for channels, governance) for operational MDM
operational MDM
• Easier (organizationally) to implement
• More difficult (technically and organizationally) to implement • Impact of failure only on BI activities
• Impact of failure severe
• Benefits extensive across the organization

34
Characteristics
 MASTER VS. REFERENCE DATA FOCUS

Master Data Management (MDM) involves control

over master data values and identifiers to enable
Reference Data Management (RDM)
consistent use, across systems, of the most accurate entails control over defined domain values
and timely data about essential business entities. and their definitions.

MDM goals include: The goal of RDM is:

1. ensuring availability of accurate, current values 1. Ensuring the organization has access to a
2. reducing risks associated with ambiguous complete set of accurate and current values
identifiers (more than one instance of an entity) for each concept represented.
and
3. reducing risks associated with ambiguity of more
than one entity.

36
 REFERENCE VS MASTER DATA
Characteristic Reference Data Master Data
Number of Values Low, fixed/known Medium-high, variable/unknown

Volatility Stable, low rate of change Medium-frequent rate of change

External (mostly); standards

Source Internal (mostly)
bodies

Ease of Governance Easy Harder, higher number of stakeholders

Number of Attributes per Very low; typically code

High
data area type/value/description

Federation/ownership of Much federation: e.g., Business Area A

attributes per business None (all attributes) masters Attribute 1/Attribute 2, Business
area Area B masters Attributes 3/4/5

High (MDM tools often have ref-data

Tool Cost Low (ref data only)
management also)
37
IMPORTANCE OF REFERENCE DATA

38
 IT’S NOT “THE FIELD OF DREAMS”

• Projects cannot afford to wait for master data to be delivered

• Subsets of the master data must be delivered “just in time” as the business projects need to
use them

• This is NOT “The Field Of Dreams”

• This means aligning the MDM initiatives with the business projects

39
Aligning MDM
ALIGNING MDM WITH BUSINESS INITIATIVES

ALIGN MDM I NI TI ATIVES, PRO CESSES, AND

R E C O M M E N D AT I O N S F O R T E C H N O L O G Y W I T H
CORPORATE AND BUSI NESS UNIT STRATEGY

41
REINVENTING THE WHEEL?

Those who wish to reinvent the

wheel usually end up going
around in circles.

ENGINEER FOR REUSE

42
PORTFOLIO VS. PER PROJECT
Portfolio planning/design for reuse
Design in isolation: Initially no
interaction outside the confines of “the
project” and just a few interfaces will
appear attractive as no wider
considerations need to be made.
Design for reuse: Once a few reusable
artifacts, models, master data objects,
reusable methods, skills, etc. are
established, projects start to reap big
benefits
Benefits $

# projects / reused objects

Seed Money: To not penalize initial projects,
but rather encourage them to do the “right
thing” for the corporation, seed money helps
with provision of resources, budget offset, etc.

Project by project/without reuse

Design in isolation: Costs increase

Design for reuse: First projects hit a dramatically with increasing number of
“cost” as there is nothing in place that point-to-point interfaces, undo-redo
can be reused/leveraged for benefit. work as clashes about data concepts
Project-based accounting discourages explode.
infrastructure investment.
43 43
MDM CHALLENGES & CONSIDERATIONS

DETERMINING THE “MASTER DATA” MATURITY OF MDM ESTABLISHED IN

TO BE MANAGED DIFFERENT PROCESSES
› Not simply the “usual” suspects: Customer, › Service Management
Product, Location, etc. › HR, Finance, etc.
› MD frequently also covers Agreements,
Patents, Trademarks, Licenses …
› How do you make the case for MDM? DATA GOVERNANCE MATURITY
› Master data for most domains spans the business
› Data Ownership & Stewardship
LACK OF CONSISTENCY › Who has the wisdom of Solomon?
› Definition and meaning (can a Supplier also be
a Customer?) INFORMATION SYSTEMS
› Presence and level of metadata
› Do multiple business systems require update to the
› Silo-oriented/stand-alone applications master data?
› Data Quality › What are the conflict resolution rules? (Did I
› “The key to successful master data mention Data Governance?)
management is management support for › Is a decoupled Master Data Hub sufficient?
relinquishing local control of shared data.”
[DAMA] › Which MDM pattern is appropriate?

44
CONCLUSIONS

Don’t believe you can

“build it and they will come”
An MDM initiative needs to be just ahead of the
business projects and deliver just in time aligned to
the business initiatives.

Data models for MDM programs are

essential
Extended with rich metadata including Ownership,
Source systems, Transformations, etc.

Beware the hype on MDM technologies

A hub is NOT the only way.
Rarely will one MDM technology be appropriate for ALL data subject areas.

Data Governance is vital

MDM initiatives cannot be successful without addressing Data Governance for that data subject
area.

45
Reference and Master
Data Management in
NDMO
NDMO Guiding Principles

47
NDMO Guiding Principles

48
Discussion

3 To 5 Minutes
Questions
Reference and Master Data
Management
Data Management 2%
Big Data 2%
Data Architecture 6%
Document & Content Management 6%
Data Ethics 2%
Data Governance 11%
Data Integration & Interoperability 6%
Master & Reference Data Management 10%
Data Modelling & Design 11%
Data Quality 11%
Data Security 6%
Data Storage & Operations 6%
Data Warehousing & Business Intelligence 10%
Metadata Management 11%
51
Ref Question A B C D E
The need to improve Data Quality and The need to build a data
MDM What is a common motivation for Regulatory acts such as The need to consolidate all data Business Intelligenc e
data integrity across multiple data dictionary of all core data entities
1 Reference & Master Data Management? BCBS239, GDPR, and SOX into one physical database data warehousin &
sources and attributes
g
Data about the business
MDM Which of these is a valid definition of Data that if missing or incorrect will cause Data that is only held in one data Data that other data sits entities that provide
Data that rarely, if ever, changes
2 master data? transactions and processes to fail source hierarchically beneath context for business
transactions
Data used to classify or Data that provides Data that has a common
MDM Which of these is a valid definition of Data that is widely accessed and
Data that is fixed and never changes categorize other data metadata about other data and widely understood
3 reference data? referenced across an organization
entities data definition
Which of the following is NOT a primary Producing read-only Producing clear data
MDM Generating a golden record/best version Providing access to golden data
Master Data Management area of Identifying duplicate records versions of key data items definitions for master
4 of the truth records
focus? data

A strong argument for pursuing a By centralizing the management of

They are essential functions in
MDM Job security for the data reference and master data, the
Reference Data and/or Master Data It will not require a lot of time or effort the Data Management
5 framework
people organization can conform critical
Management initiative is: data needed for analysis

A common driver for initiating a Managing codes and

MDM It will improve Data Quality and facilitate It will consolidate the process of
Reference Data Management program It can be a one-time-only project descriptions requires little
6 analysis across the organization securing third party code sets
is: effort and low cost
Reference Data Management includes
MDM
defining relationships within and across TRUE FALSE
7
domain value lists.
Reference Data
Managing reference data Master Data Management requires
Business data stewards maintain lists of Management involves
MDM Which one of the following statements requires the same activities and techniques for splitting or merging
valid data values for master data identifying the “best” or
8 is true? techniques as does managing
“golden” record for each
an instance of a business entity.
instances.
master data.
domain.

52
Ref Question A B C D E

MDM What is a common motivation for Reference The need to improve Data The need to build a data
Regulatory acts such as The need to consolidate all data into Business Intelligence and data
Quality and data integrity across dictionary of all core data entities
1 & Master Data Management? BCBS239, GDPR, and SOX one physical database warehousing
multiple data sources and attributes

Data about the business entities

Data that if missing or incorrect
MDM Which of these is a valid definition of master Data that is only held in one data Data that other data sits that provide context for business
will cause transactions and Data that rarely, if ever, changes
2 data? source hierarchically beneath transactions
processes to fail

Data used to classify or categorize Data that has a common and

MDM Which of these is a valid definition of Data that is fixed and never Data that provides metadata Data that is widely accessed and
other data widely understood data
3 reference data? changes about other data entities referenced across an organization
definition

Producing read-only versions of

MDM Which of the following is NOT a primary Generating a golden record/ Providing access to golden data Producing clear data definitions
Identifying duplicate records key data items
4 Master Data Management area of focus? best version of the truth records for master data

By centralizing the management of

A strong argument for pursuing a Reference reference and master data, the
MDM It will not require a lot of time They are essential functions in the
Data and/or Master Data management or effort Job security for the data people organization can conform critical
5 Data Management framework
initiative is: data needed for analysis

MDM A common driver for initiating a Reference It will improve Data Quality and Managing codes and
It will consolidate the process of
facilitate analysis across the It can be a one-time-only project descriptions requires little effort
6 Data Management program is: securing third party code sets
organization and low cost

Reference Data Management includes

MDM
defining relationships within and across TRUE FALSE
7
domain value lists.
Business data stewards Reference Data Management Master Data Management requires
Managing reference data requires
MDM Which one of the following statements is maintain lists of valid data involves identifying the “best” techniques for splitting or merging
the same activities and techniques
8 true? values for master data or “golden” record for each an instance of a business entity.
as does managing master data.
instances. domain. 53
Thank You