Difficulty: Easy
Correct Answer: Correct
Explanation:
Introduction / Context:
This question targets core data modeling vocabulary used in database design and normalization. When analysts integrate multiple sources, they often discover attributes that are semantically the same but named differently across systems. Understanding the term “synonym” helps designers consolidate and standardize schemas, reduce redundancy, and improve data quality.
Given Data / Assumptions:
Concept / Approach:
In data modeling, a synonym describes attributes that represent the same business concept while using different labels. For example, CustID and CustomerNumber may both identify a customer; EmpNo and Employee_ID may both identify an employee. Recognizing synonyms is crucial for building conformed, consistent models and for eliminating confusion when merging legacy systems or packaged applications. During logical data modeling and canonical data definition, designers map synonyms to a single standardized attribute name and document the alternatives for ETL and integration.
Step-by-Step Solution:
Verification / Alternative check:
Validate with stakeholders: if different system teams agree that attributes reference the same business object and play the same role, they are synonyms. Data profiling (distinct counts, overlap, join success) gives additional evidence.
Why Other Options Are Wrong:
Common Pitfalls:
Confusing synonyms with homonyms (same name, different meanings). Failing to standardize synonyms can lead to duplicate columns, inconsistent joins, and reporting errors across systems.
Final Answer:
Correct
Discussion & Comments