Reference And Master Data Management Exam Questions and Answers
Question 29
The Reference Data Change Request Process does NOT include which of the following subprocesses:
Options:
A.
Decide and Communicate
B.
Identify Stakeholder
C.
Receive Change Request
D.
Identify Impact
E.
Monitor Database Change
Answer:
E
Explanation:
The Reference Data Change Request Process typically involves the following sub-processes:
Receive Change Request:
Initiation: The process begins with the receipt of a change request, formally logged and acknowledged.
Identify Stakeholder:
Stakeholder Identification: Identifying all relevant stakeholders who need to be involved or informed about the change.
Identify Impact:
Impact Analysis: Assessing the potential impact of the requested change on existing systems, processes, and data.
Decide and Communicate:
Decision Making: Reviewing the change request, making a decision, and communicating the outcome to stakeholders.
Excluded Step - Monitor Database Change: While monitoring database changes is important for overall data management, it is not typically part of the specific change request process for reference data. This step pertains more to ongoing operational monitoring rather than the change request workflow.
References:
Data Management Body of Knowledge (DMBOK), Chapter 6: Data Development & Maintenance
DAMA International, "The DAMA Guide to the Data Management Body of Knowledge (DMBOK)"
Question 30
A global identifier is used to:
Options:
A.
Link two or more equivalent references to the same entity
B.
Link two or more equivalent columns to the same report
C.
Link two or more non-equivalent references to the same entity
D.
Link two or more systems by the same identifier
E.
Link two or more equivalent references to the same system or database
Answer:
A
Explanation:
A global identifier is used to link multiple references to the same entity across different systems or datasets. Here’s why:
Purpose of Global Identifier:
Unique Identification: Provides a unique identifier that can be used to recognize the same entity across disparate systems and datasets.
Consistency: Ensures that different references or records pointing to the same entity are consistently identified and managed.
Linking Equivalent References:
Equivalent References: Global identifiers link references that are equivalent, meaning they represent the same real-world entity even if the data is stored differently in various systems.
Entity Resolution: Helps in resolving different records to a single entity, ensuring data consistency and accuracy.
Example:
Customer Records: A customer might be listed in different systems (CRM, billing, support) with slightly different details. A global identifier links these records to recognize them as the same customer.
References:
Data Management Body of Knowledge (DMBOK), Chapter 7: Master Data Management
DAMA International, "The DAMA Guide to the Data Management Body of Knowledge (DMBOK)"
